d002.com - dns.ninja

`d002.com`

DNSSEC	⚠️ Not signed
NS	`ns1.julydns.com`
		A	162.159.48.223^{Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns2.julydns.com`
		A	162.159.48.223^{Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}

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

Same first word

d002.com

d002.top

Similar names

d020.com

d200.ru

002d.com

d200.com

d200.ca

2d00.com

0d20.com

200d.com

DNS History

10 records (2 active, 8 former)

○NSbrianna.ns.cloudflare.com2016-12-06 → 2017-12-29 · 5 obs

○ 2016-05-25 21:49:08
● 2016-12-06 13:22:24
● 2017-12-29 22:40:56
○ 2026-04-29 07:35:40
○ 2026-07-29 00:36:30

○NSglen.ns.cloudflare.com2016-12-06 → 2017-12-29 · 5 obs

○ 2016-05-25 21:49:08
● 2016-12-06 13:22:24
● 2017-12-29 22:40:56
○ 2026-04-29 07:35:40
○ 2026-07-29 00:36:30

●NSns1.julydns.com2026-04-29 → 2026-07-29 · 3 obs

○ 2017-12-29 22:40:56
● 2026-04-29 07:35:40
● 2026-07-29 00:36:30

○NSns1cnb.domain-resolution.net2015-09-01 → 2016-05-25 · 4 obs

● 2015-09-01 03:09:30
● 2016-05-25 21:49:08
○ 2016-12-06 13:22:24
○ 2026-07-29 00:36:30

●NSns2.julydns.com2026-04-29 → 2026-07-29 · 3 obs

○ 2017-12-29 22:40:56
● 2026-04-29 07:35:40
● 2026-07-29 00:36:30

○NSns2bls.domain-resolution.net2015-09-01 → 2016-05-25 · 4 obs

● 2015-09-01 03:09:30
● 2016-05-25 21:49:08
○ 2016-12-06 13:22:24
○ 2026-07-29 00:36:30

○NSns3cna.domain-resolution.net2015-09-01 → 2016-05-25 · 4 obs

● 2015-09-01 03:09:30
● 2016-05-25 21:49:08
○ 2016-12-06 13:22:24
○ 2026-07-29 00:36:30

○NSns4kpx.domain-resolution.net2015-09-01 → 2016-05-25 · 4 obs

● 2015-09-01 03:09:30
● 2016-05-25 21:49:08
○ 2016-12-06 13:22:24
○ 2026-07-29 00:36:30

○A108.62.45.952015-09-01 → 2016-05-25 · 4 obs

● 2015-09-01 03:09:30
● 2016-05-25 21:49:08
○ 2016-12-06 13:22:24
○ 2026-07-29 00:36:30

○A123.125.114.1442016-12-06 → 2016-12-06 · 4 obs

○ 2016-05-25 21:49:08
● 2016-12-06 13:22:24
○ 2017-12-29 22:40:56
○ 2026-07-29 00:36:30

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	b.gtld-servers.net, a.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net...	-
d002.com	ns1.julydns.com, ns2.julydns.com	2 records

✅ Authoritative Response

Server:162.159.48.223

NS records: ns1.julydns.com, ns2.julydns.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for d002.com (unsigned zone)

⏱️ Timing

Total: 602ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`ns1.julydns.com, ns2.julydns.com`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.julydns.com, ns2.julydns.com)

Analysis

Name Servers

d002.com is served by two delegated name servers, ns1.julydns.com and ns2.julydns.com.

d002.com shares its NS records with other domains, for example danchequan.com, qiyeclub.com, sz-dmr.com and two others.

The name servers of d002.com overlap at least partially with those of other domains — among them 66fsd.com, syu-katu.com, zhetg.com and two more.

These name servers commonly co-occur with the name servers ns1.judns.com, ns2.judns.com, ns1.onclouddns.com and ns2.onclouddns.com.

ns1.julydns.com and ns2.julydns.com share one IP address between them — 162.159.48.223.

These two host names — ns1.julydns.com and ns2.julydns.com — each point to 162.159.48.223 IP addresses.