🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`prodigycode.com`

DNSSEC	⚠️ Not signed
A	167.172.250.175^{🇺🇸 DIGITALOCEAN167.172.240.0/20 DigitalOcean}
		PTR	`prodigycode.com`
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`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c29::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadum-in-f26.1e100.net`
		A	172.253.115.26^{🇺🇸 Google172.253.115.0/24}
			PTR	`bg-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
TXT	`google-site-verification=DGOK8UTrkzHbmuNR45cq8PycG7vMABtgGlynNUj88_w`
TXT	`v=spf1 include:dn(0x736578)it.com include:_spf.google.com -all`
SOA	`ns1.digitalocean.com`hostmaster@prodigycode.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=1790796974

PTR for

175.250.172.167.in-addr.arpa

Same first word

prodigycode.com

prodigycode.info

prodigycode.com.pk

Similar names

codeprodigy.io

codeprodigy.de

codeprodigy.top

codeprodigy.dev

codeprodigy.ai

Previous names

Next names

DNS History

14 records (9 active, 5 former)

●NSns1.digitalocean.com2017-02-01 → 2026-09-30 · 3 obs

○ 2016-04-26 02:59:52
● 2017-02-01 00:54:48
● 2026-09-30 19:43:06

●NSns2.digitalocean.com2017-02-01 → 2026-09-30 · 3 obs

○ 2016-04-26 02:59:52
● 2017-02-01 00:54:48
● 2026-09-30 19:43:06

●NSns3.digitalocean.com2017-02-01 → 2026-09-30 · 3 obs

○ 2016-04-26 02:59:52
● 2017-02-01 00:54:48
● 2026-09-30 19:43:06

○NSns65.domaincontrol.com2016-01-23 → 2016-04-26 · 4 obs

● 2016-01-23 15:29:46
● 2016-04-26 02:59:52
○ 2017-02-01 00:54:48
○ 2026-09-30 19:43:06

○NSns66.domaincontrol.com2016-01-23 → 2016-04-26 · 4 obs

● 2016-01-23 15:29:46
● 2016-04-26 02:59:52
○ 2017-02-01 00:54:48
○ 2026-09-30 19:43:06

●MXalt1.aspmx.l.google.com2016-01-23 → 2026-09-30 · 2 obs

● 2016-01-23 15:29:46
● 2026-09-30 19:43:06

●MXalt2.aspmx.l.google.com2016-01-23 → 2026-09-30 · 2 obs

● 2016-01-23 15:29:46
● 2026-09-30 19:43:06

●MXalt3.aspmx.l.google.com2016-01-23 → 2026-09-30 · 2 obs

● 2016-01-23 15:29:46
● 2026-09-30 19:43:06

●MXalt4.aspmx.l.google.com2016-01-23 → 2026-09-30 · 2 obs

● 2016-01-23 15:29:46
● 2026-09-30 19:43:06

●MXaspmx.l.google.com2016-01-23 → 2026-09-30 · 2 obs

● 2016-01-23 15:29:46
● 2026-09-30 19:43:06

○A104.131.89.132017-02-01 → 2017-02-01 · 4 obs

○ 2016-04-26 02:59:52
● 2017-02-01 00:54:48
○ 2018-06-05 23:56:48
○ 2026-09-30 19:43:06

●A167.172.250.1752026-09-04 → 2026-09-30 · 3 obs

○ 2018-06-05 23:56:48
● 2026-09-04 23:30:26
● 2026-09-30 19:43:06

○A184.168.221.532016-01-23 → 2016-04-26 · 4 obs

● 2016-01-23 15:29:46
● 2016-04-26 02:59:52
○ 2017-02-01 00:54:48
○ 2026-09-30 19:43:06

○A45.55.86.1702018-06-05 → 2018-06-05 · 4 obs

○ 2017-02-01 00:54:48
● 2018-06-05 23:56:48
○ 2026-09-04 23:30:26
○ 2026-09-30 19:43:06

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
prodigycode.com	ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com	3 records

✅ Authoritative Response

Server:172.64.49.209

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for prodigycode.com (unsigned zone)

⏱️ Timing

Total: 323ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`167.172.250.175`
NS	3	`ns1.digitalocean.com, ns2.digitalocean.com...`
MX	5	`alt1.aspmx.l.google.com (pri: 5), aspmx.l.google.com (pri: 1)...`
TXT	2	`google-site-verification=DGOK8UTrkzHbmuN, v=spf1 include:dn(0x736578)it.com include:_spf.`
SOA	1	`ns1.digitalocean.com hostmaster.prodigyc`

📌 Glue Records Collected

Total: 3

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

Analysis

IP Addresses

prodigycode.com resolves to just one IP address, 167.172.250.175.

Name Servers

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

prodigycode.com partially shares its NS delegation with several other domains, including 92.184.137.in-addr.arpa, locallypages.com, dontpanic.org.ua 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.

Mail Servers

prodigycode.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

There is at least a partial MX overlap between prodigycode.com and other domains, including gubernick.com, eightpatcher.com, leali-fitness-llc.com and two others.

alt4.aspmx.l.google.com, alt3.aspmx.l.google.com, aspmx3.googlemail.com and aspmx2.googlemail.com are mail servers that frequently appear together with these mail servers.

Host names that have two IP addresses:

aspmx.l.google.com directs traffic to 172.253.115.26 and 2607:f8b0:4004:c29::1a.

alt1.aspmx.l.google.com directs traffic to 192.178.234.27 and 2800:3f0:4003:c14::1b.

alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1a.

alt3.aspmx.l.google.com directs traffic to 192.178.223.27 and 2a00:1450:4009:c0f::1b.

alt4.aspmx.l.google.com directs traffic to 172.253.157.26 and 2a00:1450:400c:c23::1a.

prodigycode.com - robtex.com

prodigycode.com

com

PTR for

Same first word

Similar names

Previous names

Next names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

IP Addresses

Name Servers

Mail Servers

`prodigycode.com`

`com`