metadust.com - dns.ninja

`metadust.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=1786357114

Same first word

metadust.com

Similar names

dustteam.com

mustdate.com

dustmate.com

studmate.ru

dustmeta.com

studmate.com

stadtmue.de

DNS History

19 records (4 active, 15 former)

○NSdns1.name-services.com2017-09-15 → 2017-09-15 · 4 obs

○ 2016-11-28 07:50:44
● 2017-09-15 05:19:00
○ 2026-04-08 02:17:40
○ 2026-08-10 10:41:18

○NSdns1.registrar-servers.com2015-05-29 → 2016-11-28 · 7 obs

● 2015-05-29 11:04:38
● 2015-10-27 01:54:22
○ 2016-01-05 16:23:46
○ 2016-04-16 22:12:12
● 2016-11-28 07:50:44
○ 2017-09-15 05:19:00
○ 2026-08-10 10:41:18

○NSdns1.registrar-servers.com,2016-01-05 → 2016-04-16 · 5 obs

○ 2015-10-27 01:54:22
● 2016-01-05 16:23:46
● 2016-04-16 22:12:12
○ 2016-11-28 07:50:44
○ 2026-08-10 10:41:18

○NSdns2.name-services.com2017-09-15 → 2017-09-15 · 4 obs

○ 2016-11-28 07:50:44
● 2017-09-15 05:19:00
○ 2026-04-08 02:17:40
○ 2026-08-10 10:41:18

○NSdns2.registrar-servers.com2015-05-29 → 2016-11-28 · 4 obs

● 2015-05-29 11:04:38
● 2016-11-28 07:50:44
○ 2017-09-15 05:19:00
○ 2026-08-10 10:41:18

○NSdns3.name-services.com2017-09-15 → 2017-09-15 · 4 obs

○ 2016-11-28 07:50:44
● 2017-09-15 05:19:00
○ 2026-04-08 02:17:40
○ 2026-08-10 10:41:18

○NSdns3.registrar-servers.com2015-05-29 → 2016-04-16 · 4 obs

● 2015-05-29 11:04:38
● 2016-04-16 22:12:12
○ 2016-11-28 07:50:44
○ 2026-08-10 10:41:18

○NSdns4.name-services.com2017-09-15 → 2017-09-15 · 4 obs

○ 2016-11-28 07:50:44
● 2017-09-15 05:19:00
○ 2026-04-08 02:17:40
○ 2026-08-10 10:41:18

○NSdns4.registrar-servers.com2015-05-29 → 2016-04-16 · 4 obs

● 2015-05-29 11:04:38
● 2016-04-16 22:12:12
○ 2016-11-28 07:50:44
○ 2026-08-10 10:41:18

○NSdns5.name-services.com2017-09-15 → 2017-09-15 · 4 obs

○ 2016-11-28 07:50:44
● 2017-09-15 05:19:00
○ 2026-04-08 02:17:40
○ 2026-08-10 10:41:18

○NSdns5.registrar-servers.com2015-05-29 → 2016-04-16 · 4 obs

● 2015-05-29 11:04:38
● 2016-04-16 22:12:12
○ 2016-11-28 07:50:44
○ 2026-08-10 10:41:18

●NSns-cloud-e1.googledomains.com2026-04-08 → 2026-08-10 · 3 obs

○ 2017-09-15 05:19:00
● 2026-04-08 02:17:40
● 2026-08-10 10:41:18

●NSns-cloud-e2.googledomains.com2026-04-08 → 2026-08-10 · 3 obs

○ 2017-09-15 05:19:00
● 2026-04-08 02:17:40
● 2026-08-10 10:41:18

●NSns-cloud-e3.googledomains.com2026-04-08 → 2026-08-10 · 3 obs

○ 2017-09-15 05:19:00
● 2026-04-08 02:17:40
● 2026-08-10 10:41:18

●NSns-cloud-e4.googledomains.com2026-04-08 → 2026-08-10 · 3 obs

○ 2017-09-15 05:19:00
● 2026-04-08 02:17:40
● 2026-08-10 10:41:18

○A162.255.119.2492016-11-28 → 2016-11-28 · 4 obs

○ 2016-04-16 22:12:12
● 2016-11-28 07:50:44
○ 2017-09-15 05:19:00
○ 2026-08-10 10:41:18

○A192.64.119.1592016-01-05 → 2016-04-16 · 5 obs

○ 2015-10-27 01:54:22
● 2016-01-05 16:23:46
● 2016-04-16 22:12:12
○ 2016-11-28 07:50:44
○ 2026-08-10 10:41:18

○A68.65.123.1912015-05-29 → 2015-10-27 · 4 obs

● 2015-05-29 11:04:38
● 2015-10-27 01:54:22
○ 2016-01-05 16:23:46
○ 2026-08-10 10:41:18

○A69.64.147.102017-09-15 → 2017-09-15 · 4 obs

○ 2016-11-28 07:50:44
● 2017-09-15 05:19:00
○ 2026-04-08 02:17:40
○ 2026-08-10 10:41:18

🔍 DNS Trace

📋 Delegation Chain

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

⚠️ Insecure (no DNSSEC)

No DS record for metadust.com (unsigned zone)

⏱️ Timing

Total: 261ms | 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 authoritative name servers for metadust.com are ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com.

metadust.com shares at least some of its name servers with other domains, including in4bit.com, cybermap.org, familyharris.ca and two others.

The host names ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com each resolve to two IP addresses: ns-cloud-e1.googledomains.com resolves to 216.239.32.110 and 2001:4860:4802:32::6e; ns-cloud-e2.googledomains.com resolves to 216.239.34.110 and 2001:4860:4802:34::6e; ns-cloud-e3.googledomains.com resolves to 216.239.36.110 and 2001:4860:4802:36::6e; ns-cloud-e4.googledomains.com resolves to 216.239.38.110 and 2001:4860:4802:38::6e.