🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`exploringcode.com`

DNSSEC	⚠️ Not signed
A	194.67.193.138^{🇷🇺 MFI-AS194.67.193.0/24}
NS	`ns1.digitalocean.com` ⭐
		A	2606:4700:52::ac40:34d2^{🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.digitalocean.com`
		A	172.64.52.210^{🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.digitalocean.com`
NS	`ns2.digitalocean.com`
		A	2606:4700:5a::ac40:3515^{🇺🇸 Cloudflare2606:4700:5a::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.digitalocean.com`
		A	172.64.53.21^{🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.digitalocean.com`
NS	`ns3.digitalocean.com`
		A	2606:4700:52::ac40:31d1^{🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns3.digitalocean.com`
		A	172.64.49.209^{🇺🇸 Cloudflare172.64.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns3.digitalocean.com`
SOA	`ns1.digitalocean.com`hostmaster@exploringcode.com serial=0

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

Same first word

exploringcode.org

exploringcode.com

Previous names

Next names

DNS History

5 records (4 active, 1 former)

●NSns1.digitalocean.com2015-08-20 → 2026-09-19 · 2 obs

● 2015-08-20 08:25:04
● 2026-09-19 07:54:10

●NSns2.digitalocean.com2015-08-20 → 2026-09-19 · 2 obs

● 2015-08-20 08:25:04
● 2026-09-19 07:54:10

●NSns3.digitalocean.com2015-08-20 → 2026-09-19 · 2 obs

● 2015-08-20 08:25:04
● 2026-09-19 07:54:10

○A162.243.3.1882015-08-20 → 2016-12-16 · 4 obs

● 2015-08-20 08:25:04
● 2016-12-16 12:47:28
○ 2026-04-11 18:37:36
○ 2026-09-19 07:54:10

●A194.67.193.1382026-04-11 → 2026-09-19 · 3 obs

○ 2016-12-16 12:47:28
● 2026-04-11 18:37:36
● 2026-09-19 07:54:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	m.gtld-servers.net, c.gtld-servers.net, k.gtld-servers.net, e.gtld-servers.net...	-
exploringcode.com	ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com	3 records

✅ Authoritative Response

Server:172.64.52.210

NS records: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for exploringcode.com (unsigned zone)

⏱️ Timing

Total: 781ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`194.67.193.138`
NS	3	`ns1.digitalocean.com, ns3.digitalocean.com...`
SOA	1	`ns1.digitalocean.com hostmaster.explorin`

📌 Glue Records Collected

Total: 3

Out-of-bailiwick: 3 (ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com)

Analysis

IP Addresses

exploringcode.com has exactly one IP address — 194.67.193.138.

crypton00b.com, bundleofsavings.com, beclassie.com plus two other host names have IP numbers in common with exploringcode.com.

Name Servers

The authoritative name servers for exploringcode.com are ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com — three in total.

exploringcode.com partially shares its NS delegation with several other domains, including thetrinetwork.com, guests.ca, guardianbrasil.com and two others.

ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com all resolve to exactly two IP numbers apiece: ns1.digitalocean.com → 172.64.52.210 and 2606:4700:52::ac40:34d2; ns2.digitalocean.com → 172.64.53.21 and 2606:4700:5a::ac40:3515; ns3.digitalocean.com → 172.64.49.209 and 2606:4700:52::ac40:31d1.

exploringcode.com - robtex.com