midpay.com - dns.ninja

`midpay.com`

DNSSEC	🔒 Signed (DS record present)
NS	`ns-cloud-e1.googledomains.com` ⭐
		A	2001:4860:4802:32::6e^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-e1.googledomains.com`
		A	216.239.32.110^{🇺🇸 Google216.239.32.0/24}
			PTR	`ns-cloud-e1.googledomains.com`
NS	`ns-cloud-e2.googledomains.com`
		A	2001:4860:4802:34::6e^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-e2.googledomains.com`
		A	216.239.34.110^{🇺🇸 Google216.239.34.0/24}
			PTR	`ns-cloud-e2.googledomains.com`
NS	`ns-cloud-e3.googledomains.com`
		A	2001:4860:4802:36::6e^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-e3.googledomains.com`
		A	216.239.36.110^{🇺🇸 Google216.239.36.0/24}
			PTR	`ns-cloud-e3.googledomains.com`
NS	`ns-cloud-e4.googledomains.com`
		A	2001:4860:4802:38::6e^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-e4.googledomains.com`
		A	216.239.38.110^{🇺🇸 Google216.239.38.0/24}
			PTR	`ns-cloud-e4.googledomains.com`
SOA	`ns-cloud-e1.googledomains.com`cloud-dns-hostmaster@google.com serial=7

`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=1785690332

Same first word

midpay.net

midpay.me

midpay.com

Similar names

idmpay.com

ipmday.com

mydipa.co.id

yidmap.com

dyapim.com.tr

mapdiy.net

dimpay.io

mypaid.com

ampdiy.com

mayidp.com

mapdiy.com

myipad.ru

myipad.eu

mypaid.net

paymid.org

dmipay.com

pmdiya.cc

myidpa.com

mypadi.com

pmiday.it

diyamp.com

paymid.net

paydim.com

imdpay.com

dimpay.com

impayd.com

paymid.com

myipad.com

myipad.cn

mypaid.de

mypadi.ch

DNS History

16 records (4 active, 12 former)

○NSbuy.internettraffic.com2015-12-02 → 2016-05-10 · 5 obs

○ 2015-08-13 02:47:26
● 2015-12-02 03:00:08
● 2016-05-10 12:58:20
○ 2017-06-20 04:15:58
○ 2026-08-02 17:17:40

○NSdns1.name-services.com2015-08-13 → 2017-06-20 · 6 obs

● 2015-08-13 02:47:26
○ 2015-12-02 03:00:08
○ 2016-05-10 12:58:20
● 2017-06-20 04:15:58
○ 2026-03-26 19:27:38
○ 2026-08-02 17:17:40

○NSdns2.name-services.com2015-08-13 → 2017-06-20 · 6 obs

● 2015-08-13 02:47:26
○ 2015-12-02 03:00:08
○ 2016-05-10 12:58:20
● 2017-06-20 04:15:58
○ 2026-03-26 19:27:38
○ 2026-08-02 17:17:40

○NSdns3.name-services.com2015-08-13 → 2017-06-20 · 6 obs

● 2015-08-13 02:47:26
○ 2015-12-02 03:00:08
○ 2016-05-10 12:58:20
● 2017-06-20 04:15:58
○ 2026-03-26 19:27:38
○ 2026-08-02 17:17:40

○NSdns4.name-services.com2015-08-13 → 2017-06-20 · 6 obs

● 2015-08-13 02:47:26
○ 2015-12-02 03:00:08
○ 2016-05-10 12:58:20
● 2017-06-20 04:15:58
○ 2026-03-26 19:27:38
○ 2026-08-02 17:17:40

○NSdns5.name-services.com2015-08-13 → 2017-06-20 · 6 obs

● 2015-08-13 02:47:26
○ 2015-12-02 03:00:08
○ 2016-05-10 12:58:20
● 2017-06-20 04:15:58
○ 2026-03-26 19:27:38
○ 2026-08-02 17:17:40

●NSns-cloud-e1.googledomains.com2026-03-26 → 2026-08-02 · 3 obs

○ 2017-06-20 04:15:58
● 2026-03-26 19:27:38
● 2026-08-02 17:17:40

●NSns-cloud-e2.googledomains.com2026-03-26 → 2026-08-02 · 3 obs

○ 2017-06-20 04:15:58
● 2026-03-26 19:27:38
● 2026-08-02 17:17:40

●NSns-cloud-e3.googledomains.com2026-03-26 → 2026-08-02 · 3 obs

○ 2017-06-20 04:15:58
● 2026-03-26 19:27:38
● 2026-08-02 17:17:40

●NSns-cloud-e4.googledomains.com2026-03-26 → 2026-08-02 · 3 obs

○ 2017-06-20 04:15:58
● 2026-03-26 19:27:38
● 2026-08-02 17:17:40

○NSsell.internettraffic.com2015-12-02 → 2016-05-10 · 5 obs

○ 2015-08-13 02:47:26
● 2015-12-02 03:00:08
● 2016-05-10 12:58:20
○ 2017-06-20 04:15:58
○ 2026-08-02 17:17:40

○MXp.nsm.ctmail.com2015-08-13 → 2015-08-13 · 3 obs

● 2015-08-13 02:47:26
○ 2015-12-02 03:00:08
○ 2026-08-02 17:17:40

○A208.88.52.2132017-06-20 → 2017-06-20 · 4 obs

○ 2016-05-10 12:58:20
● 2017-06-20 04:15:58
○ 2026-03-26 19:27:38
○ 2026-08-02 17:17:40

○A64.74.223.332015-08-13 → 2015-08-13 · 3 obs

● 2015-08-13 02:47:26
○ 2015-12-02 03:00:08
○ 2026-08-02 17:17:40

○A69.172.201.1532016-05-10 → 2016-05-10 · 4 obs

○ 2016-03-03 05:31:10
● 2016-05-10 12:58:20
○ 2017-06-20 04:15:58
○ 2026-08-02 17:17:40

○A69.172.201.2082015-12-02 → 2016-03-03 · 5 obs

○ 2015-08-13 02:47:26
● 2015-12-02 03:00:08
● 2016-03-03 05:31:10
○ 2016-05-10 12:58:20
○ 2026-08-02 17:17:40

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
midpay.com	ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com	8 records

✅ Authoritative Response

Server:216.239.34.110

NS records: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com

🔒 DNSSEC Status

🔐 Secure (DNSSEC validated)

Chain of trust verified from root to domain

⏱️ Timing

Total: 360ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com...`
SOA	1	`ns-cloud-e1.googledomains.com cloud-dns-`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns-cloud-e1.googledomains.com, ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com...)

Analysis

Name Servers

The domain midpay.com is delegated to these four name servers: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com.

At least some of midpay.com's name servers are shared with other domains, for example martaismyagent.com, abbaandme.com, plastiikkakirurgianpalvelut.fi and two more.

Four hostnames, each resolving to a pair of IP addresses: ns-cloud-e1.googledomains.com directs to 216.239.32.110 and 2001:4860:4802:32::6e; ns-cloud-e2.googledomains.com directs to 216.239.34.110 and 2001:4860:4802:34::6e; ns-cloud-e3.googledomains.com directs to 216.239.36.110 and 2001:4860:4802:36::6e; ns-cloud-e4.googledomains.com directs to 216.239.38.110 and 2001:4860:4802:38::6e.