`scanmysystem.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=3

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

Same first word

scanmysystem.com

DNS History

6 records (4 active, 2 former)

●NSns-cloud-e1.googledomains.com2026-03-26 → 2026-03-26 · 2 obs

○ 2017-05-26 10:26:36
● 2026-03-26 15:30:10

●NSns-cloud-e2.googledomains.com2026-03-26 → 2026-03-26 · 2 obs

○ 2017-05-26 10:26:36
● 2026-03-26 15:30:10

●NSns-cloud-e3.googledomains.com2026-03-26 → 2026-03-26 · 2 obs

○ 2017-05-26 10:26:36
● 2026-03-26 15:30:10

●NSns-cloud-e4.googledomains.com2026-03-26 → 2026-03-26 · 2 obs

○ 2017-05-26 10:26:36
● 2026-03-26 15:30:10

○NSns1.afternic.com2015-08-23 → 2017-05-26 · 3 obs

● 2015-08-23 02:49:32
● 2017-05-26 10:26:36
○ 2026-03-26 15:30:10

○A184.168.221.1042015-08-23 → 2017-05-26 · 3 obs

● 2015-08-23 02:49:32
● 2017-05-26 10:26:36
○ 2026-03-26 15:30:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	h.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net...	-
scanmysystem.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.36.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: 310ms | 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

scanmysystem.com is delegated 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.

scanmysystem.com at least partially shares name servers with other domains, for instance inputhealth.dev, glassinnovationsinc.com, ayurvedaking.com, turbahn.net and 4z-onlinetech.com.

Host names with two IP numbers:

ns-cloud-e1.googledomains.com points to: 2001:4860:4802:32::6e and 216.239.32.110.

ns-cloud-e2.googledomains.com points to: 2001:4860:4802:34::6e and 216.239.34.110.

ns-cloud-e3.googledomains.com points to: 2001:4860:4802:36::6e and 216.239.36.110.

ns-cloud-e4.googledomains.com points to: 2001:4860:4802:38::6e and 216.239.38.110.

scanmysystem.com - robtex.com