payarray.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`payarray.com`

DNSSEC	⚠️ Not signed
A	93.171.200.30^{🇭🇰 IQWEB93.171.200.0/24}
		PTR	`http-gw-ext-ddos.miracloud.tech`
NS	`ns-1115.awsdns-11.org` ⭐
		A	2600:9000:5304:5b00::1^{🇺🇸 Amazon2600:9000:5304::/48 - CloudFront}
			PTR	`ns-1115.awsdns-11.org`
		A	205.251.196.91^{🇺🇸 Amazon205.251.196.0/24 prefix}
			PTR	`ns-1115.awsdns-11.org`
NS	`ns-1021.awsdns-63.net`
		A	2600:9000:5303:fd00::1^{🇺🇸 Amazon2600:9000:5303::/48 - CloudFront}
			PTR	`ns-1021.awsdns-63.net`
		A	205.251.195.253^{🇺🇸 Amazon205.251.195.0/24 prefix}
			PTR	`ns-1021.awsdns-63.net`
NS	`ns-1758.awsdns-27.co.uk`
		A	2600:9000:5306:de00::1^{🇺🇸 Amazon2600:9000:5306::/48 - CloudFront}
			PTR	`ns-1758.awsdns-27.co.uk`
		A	205.251.198.222^{🇺🇸 Amazon205.251.198.0/24 prefix}
			PTR	`ns-1758.awsdns-27.co.uk`
NS	`ns-177.awsdns-22.com`
		A	2600:9000:5300:b100::1^{🇺🇸 Amazon2600:9000:5300::/48 - CloudFront}
			PTR	`ns-177.awsdns-22.com`
		A	205.251.192.177^{🇺🇸 Amazon205.251.192.0/24 prefix}
			PTR	`ns-177.awsdns-22.com`
MX	`mx0.miracloud.tech` ⭐
		A	93.171.200.4^{🇭🇰 IQWEB93.171.200.0/24}
MX	`mx1.miracloud.tech`⁽¹⁰⁾
		A	93.171.201.6^{🇭🇰 SERVEREL-AS93.171.200.0/22}
			PTR	`mx1.miracloud.tech`
TXT	`v=spf1 a mx include:_spf.miracloud.tech ~all`
SOA	`ns-1115.awsdns-11.org`awsdns-hostmaster@amazon.com serial=1

`com`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.gtld-servers.net` ⭐
	NS	`b.gtld-servers.net`
	NS	`c.gtld-servers.net`
	NS	`d.gtld-servers.net`
	NS	`e.gtld-servers.net`
	NS	`f.gtld-servers.net`
	NS	`g.gtld-servers.net`
	NS	`h.gtld-servers.net`
	NS	`i.gtld-servers.net`
	NS	`j.gtld-servers.net`
	NS	`k.gtld-servers.net`
	NS	`l.gtld-servers.net`
	NS	`m.gtld-servers.net`
	SOA	`a.gtld-servers.net`nstld@verisign-grs.com serial=1788677238

Same first word

payarray.com

payarray.xyz

Similar names

ayaparry.com

arraypay.xyz

yarrapay.com

arraypay.pages.dev

arraypay.com

Previous names

Next names

DNS History

22 records (7 active, 15 former)

●NSns-1021.awsdns-63.net2026-08-30 → 2026-09-06 · 3 obs

○ 2018-01-23 05:34:50
● 2026-08-30 02:31:52
● 2026-09-06 06:55:06

●NSns-1115.awsdns-11.org2026-08-30 → 2026-09-06 · 3 obs

○ 2018-01-23 05:34:50
● 2026-08-30 02:31:52
● 2026-09-06 06:55:06

●NSns-1758.awsdns-27.co.uk2026-08-30 → 2026-09-06 · 3 obs

○ 2018-01-23 05:34:50
● 2026-08-30 02:31:52
● 2026-09-06 06:55:06

●NSns-177.awsdns-22.com2026-08-30 → 2026-09-06 · 3 obs

○ 2018-01-23 05:34:50
● 2026-08-30 02:31:52
● 2026-09-06 06:55:06

○NSns29.domaincontrol.com2018-01-23 → 2018-01-23 · 4 obs

○ 2016-08-07 20:27:04
● 2018-01-23 05:34:50
○ 2026-08-30 02:31:52
○ 2026-09-06 06:55:06

○NSns30.domaincontrol.com2018-01-23 → 2018-01-23 · 4 obs

○ 2016-08-07 20:27:04
● 2018-01-23 05:34:50
○ 2026-08-30 02:31:52
○ 2026-09-06 06:55:06

○NSns33.domaincontrol.com2015-05-24 → 2016-08-07 · 4 obs

● 2015-05-24 03:18:58
● 2016-08-07 20:27:04
○ 2018-01-23 05:34:50
○ 2026-09-06 06:55:06

○NSns34.domaincontrol.com2015-05-24 → 2016-08-07 · 4 obs

● 2015-05-24 03:18:58
● 2016-08-07 20:27:04
○ 2018-01-23 05:34:50
○ 2026-09-06 06:55:06

○MXmailstore1.secureserver.net2015-05-24 → 2016-08-07 · 4 obs

● 2015-05-24 03:18:58
● 2016-08-07 20:27:04
○ 2018-01-23 05:34:50
○ 2026-09-06 06:55:06

●MXmx0.miracloud.tech2026-08-30 → 2026-09-06 · 3 obs

○ 2018-01-23 05:34:50
● 2026-08-30 02:31:52
● 2026-09-06 06:55:06

●MXmx1.miracloud.tech2026-08-30 → 2026-09-06 · 3 obs

○ 2018-01-23 05:34:50
● 2026-08-30 02:31:52
● 2026-09-06 06:55:06

○MXsmtp.secureserver.net2015-05-24 → 2016-08-07 · 4 obs

● 2015-05-24 03:18:58
● 2016-08-07 20:27:04
○ 2018-01-23 05:34:50
○ 2026-09-06 06:55:06

○A184.168.221.352018-01-23 → 2018-01-23 · 4 obs

○ 2016-08-07 20:27:04
● 2018-01-23 05:34:50
○ 2026-08-30 02:31:52
○ 2026-09-06 06:55:06

○A184.168.221.392018-01-23 → 2018-01-23 · 4 obs

○ 2016-08-07 20:27:04
● 2018-01-23 05:34:50
○ 2026-08-30 02:31:52
○ 2026-09-06 06:55:06

○A184.168.221.432018-01-23 → 2018-01-23 · 4 obs

○ 2016-08-07 20:27:04
● 2018-01-23 05:34:50
○ 2026-08-30 02:31:52
○ 2026-09-06 06:55:06

○A184.168.221.442018-01-23 → 2018-01-23 · 4 obs

○ 2016-08-07 20:27:04
● 2018-01-23 05:34:50
○ 2026-08-30 02:31:52
○ 2026-09-06 06:55:06

○A184.168.221.482018-01-23 → 2018-01-23 · 4 obs

○ 2016-08-07 20:27:04
● 2018-01-23 05:34:50
○ 2026-08-30 02:31:52
○ 2026-09-06 06:55:06

○A184.168.221.602018-01-23 → 2018-01-23 · 4 obs

○ 2016-08-07 20:27:04
● 2018-01-23 05:34:50
○ 2026-08-30 02:31:52
○ 2026-09-06 06:55:06

○A184.168.221.612018-01-23 → 2018-01-23 · 4 obs

○ 2016-08-07 20:27:04
● 2018-01-23 05:34:50
○ 2026-08-30 02:31:52
○ 2026-09-06 06:55:06

○A184.168.221.632015-05-24 → 2016-08-07 · 4 obs

● 2015-05-24 03:18:58
● 2016-08-07 20:27:04
○ 2018-01-23 05:34:50
○ 2026-09-06 06:55:06

○A50.63.202.612018-01-23 → 2018-01-23 · 4 obs

○ 2016-08-07 20:27:04
● 2018-01-23 05:34:50
○ 2026-08-30 02:31:52
○ 2026-09-06 06:55:06

●A93.171.200.302026-08-30 → 2026-09-06 · 3 obs

○ 2018-01-23 05:34:50
● 2026-08-30 02:31:52
● 2026-09-06 06:55:06

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
payarray.com	ns-177.awsdns-22.com, ns-1021.awsdns-63.net, ns-1115.awsdns-11.org, ns-1758.awsdns-27.co.uk	2 records

✅ Authoritative Response

Server:205.251.198.222

NS records: ns-177.awsdns-22.com, ns-1021.awsdns-63.net, ns-1115.awsdns-11.org, ns-1758.awsdns-27.co.uk

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for payarray.com (unsigned zone)

⏱️ Timing

Total: 1937ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`93.171.200.30`
NS	4	`ns-1021.awsdns-63.net, ns-1115.awsdns-11.org...`
MX	2	`mx1.miracloud.tech (pri: 10), mx0.miracloud.tech (pri: 5)`
TXT	1	`v=spf1 a mx include:_spf.miracloud.tech`
SOA	1	`ns-1115.awsdns-11.org awsdns-hostmaster.`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns-177.awsdns-22.com, ns-177.awsdns-22.com)

Analysis

IP Addresses

payarray.com resolves to just one IP address, 93.171.200.30.

Two other host names, along with mirafox.ru, miracorp.ru and mirafox.com, also share IP numbers with payarray.com.

Name Servers

The NS records for payarray.com point to four name servers: ns-177.awsdns-22.com, ns-1021.awsdns-63.net, ns-1115.awsdns-11.org and ns-1758.awsdns-27.co.uk.

payarray.com has at least partial name server overlap with other domains, such as nanairo.coop, connectqa.connectedcomms.click, kewpieusa.com and two others.

ns-177.awsdns-22.com, ns-1021.awsdns-63.net, ns-1115.awsdns-11.org and ns-1758.awsdns-27.co.uk all point to exactly two IP numbers each: ns-177.awsdns-22.com → 205.251.192.177 and 2600:9000:5300:b100::1; ns-1021.awsdns-63.net → 205.251.195.253 and 2600:9000:5303:fd00::1; ns-1115.awsdns-11.org → 205.251.196.91 and 2600:9000:5304:5b00::1; ns-1758.awsdns-27.co.uk → 205.251.198.222 and 2600:9000:5306:de00::1.

Mail Servers

payarray.com is served by two mail servers, mx0.miracloud.tech and mx1.miracloud.tech.

Among the domains sharing a mail server setup with payarray.com are mirahost.ru, gogettop.ru, miracloud.ru and two others.

mx0.miracloud.tech directs to 93.171.200.4 and mx1.miracloud.tech directs to 93.171.201.6; each host name points to exactly one IP number.