whatrun.com - dns.ninja

`whatrun.com`

DNSSEC	⚠️ Not signed
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=14

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

Same first word

whatrun.com

Similar names

huntwar.com

warthun.de

wuhanrt.com

DNS History

17 records (4 active, 13 former)

○NSdns.technorail.com2015-06-17 → 2017-02-06 · 4 obs

● 2015-06-17 01:53:00
● 2017-02-06 14:58:18
○ 2026-07-03 22:56:12
○ 2026-08-02 17:39:04

○NSdns2.technorail.com2015-06-17 → 2017-02-06 · 4 obs

● 2015-06-17 01:53:00
● 2017-02-06 14:58:18
○ 2026-07-03 22:56:12
○ 2026-08-02 17:39:04

○NSdns3.arubadns.net2015-06-17 → 2017-02-06 · 4 obs

● 2015-06-17 01:53:00
● 2017-02-06 14:58:18
○ 2026-07-03 22:56:12
○ 2026-08-02 17:39:04

○NSdns4.arubadns.cz2015-06-17 → 2017-02-06 · 4 obs

● 2015-06-17 01:53:00
● 2017-02-06 14:58:18
○ 2026-07-03 22:56:12
○ 2026-08-02 17:39:04

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

○ 2017-02-06 14:58:18
● 2026-07-03 22:56:12
● 2026-08-02 17:39:04

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

○ 2017-02-06 14:58:18
● 2026-07-03 22:56:12
● 2026-08-02 17:39:04

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

○ 2017-02-06 14:58:18
● 2026-07-03 22:56:12
● 2026-08-02 17:39:04

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

○ 2017-02-06 14:58:18
● 2026-07-03 22:56:12
● 2026-08-02 17:39:04

○MXmx.whatrun.com2015-06-17 → 2017-02-06 · 4 obs

● 2015-06-17 01:53:00
● 2017-02-06 14:58:18
○ 2026-07-03 22:56:12
○ 2026-08-02 17:39:04

○A62.149.128.1512015-06-17 → 2017-02-06 · 4 obs

● 2015-06-17 01:53:00
● 2017-02-06 14:58:18
○ 2026-07-03 22:56:12
○ 2026-08-02 17:39:04

○A62.149.128.1542015-06-17 → 2017-02-06 · 4 obs

● 2015-06-17 01:53:00
● 2017-02-06 14:58:18
○ 2026-07-03 22:56:12
○ 2026-08-02 17:39:04

○A62.149.128.1572015-06-17 → 2017-02-06 · 4 obs

● 2015-06-17 01:53:00
● 2017-02-06 14:58:18
○ 2026-07-03 22:56:12
○ 2026-08-02 17:39:04

○A62.149.128.1602015-06-17 → 2017-02-06 · 4 obs

● 2015-06-17 01:53:00
● 2017-02-06 14:58:18
○ 2026-07-03 22:56:12
○ 2026-08-02 17:39:04

○A62.149.128.1632015-06-17 → 2017-02-06 · 4 obs

● 2015-06-17 01:53:00
● 2017-02-06 14:58:18
○ 2026-07-03 22:56:12
○ 2026-08-02 17:39:04

○A62.149.128.1662015-06-17 → 2017-02-06 · 4 obs

● 2015-06-17 01:53:00
● 2017-02-06 14:58:18
○ 2026-07-03 22:56:12
○ 2026-08-02 17:39:04

○A62.149.128.722015-06-17 → 2017-02-06 · 4 obs

● 2015-06-17 01:53:00
● 2017-02-06 14:58:18
○ 2026-07-03 22:56:12
○ 2026-08-02 17:39:04

○A62.149.128.742015-06-17 → 2017-02-06 · 4 obs

● 2015-06-17 01:53:00
● 2017-02-06 14:58:18
○ 2026-07-03 22:56:12
○ 2026-08-02 17:39:04

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
whatrun.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.32.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

⚠️ Insecure (no DNSSEC)

No DS record for whatrun.com (unsigned zone)

⏱️ Timing

Total: 224ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns-cloud-e4.googledomains.com, ns-cloud-e3.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 NS records for whatrun.com point to four name servers: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com.

whatrun.com has at least partial name server overlap with other domains, such as kimphan.com, rxdigital.cl, guide.net and two others.

ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com all point to exactly two IP numbers each: ns-cloud-e1.googledomains.com → 216.239.32.110 and 2001:4860:4802:32::6e; ns-cloud-e2.googledomains.com → 216.239.34.110 and 2001:4860:4802:34::6e; ns-cloud-e3.googledomains.com → 216.239.36.110 and 2001:4860:4802:36::6e; ns-cloud-e4.googledomains.com → 216.239.38.110 and 2001:4860:4802:38::6e.