🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`code-kracker.com`

DNSSEC	⚠️ Not signed
NS	`jarred.ns.cloudflare.com` ⭐
		A	2606:4700:58::a29f:2c7e^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jarred.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c37e^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`jarred.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:237e^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`jarred.ns.cloudflare.com`
		A	108.162.195.126^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jarred.ns.cloudflare.com`
		A	162.159.44.126^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jarred.ns.cloudflare.com`
		A	172.64.35.126^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jarred.ns.cloudflare.com`
NS	`lindsey.ns.cloudflare.com`
		A	2606:4700:50::a29f:2605^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lindsey.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c205^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`lindsey.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2205^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`lindsey.ns.cloudflare.com`
		A	108.162.194.5^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lindsey.ns.cloudflare.com`
		A	162.159.38.5^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lindsey.ns.cloudflare.com`
		A	172.64.34.5^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lindsey.ns.cloudflare.com`
MX	`route3.mx.cloudflare.net` ⭐
		A	2606:4700:f5::11^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::12^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::13^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.23^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.24^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.25^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
MX	`route2.mx.cloudflare.net`⁽²⁵⁾
		A	2606:4700:f5::e^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::f^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::10^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.17^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.18^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.19^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
MX	`route1.mx.cloudflare.net`⁽⁸⁷⁾
		A	2606:4700:f5::b^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::c^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::d^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.11^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.12^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.13^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
SOA	`jarred.ns.cloudflare.com`dns@cloudflare.com serial=2412365106

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

Previously MX for

code-kracker.com

Same first word

code-kracker.com

Previous names

Next names

DNS History

9 records (5 active, 4 former)

●NSjarred.ns.cloudflare.com2026-08-26 → 2026-08-31 · 3 obs

○ 2017-05-09 01:19:38
● 2026-08-26 03:33:54
● 2026-08-31 01:21:14

●NSlindsey.ns.cloudflare.com2026-08-26 → 2026-08-31 · 3 obs

○ 2017-05-09 01:19:38
● 2026-08-26 03:33:54
● 2026-08-31 01:21:14

○NSns1.md-in-54.webhostbox.net2017-05-09 → 2017-05-09 · 3 obs

● 2017-05-09 01:19:38
○ 2026-08-26 03:33:54
○ 2026-08-31 01:21:14

○NSns2.md-in-54.webhostbox.net2017-05-09 → 2017-05-09 · 3 obs

● 2017-05-09 01:19:38
○ 2026-08-26 03:33:54
○ 2026-08-31 01:21:14

○MXcode-kracker.com2017-05-09 → 2017-05-09 · 3 obs

● 2017-05-09 01:19:38
○ 2026-08-26 03:33:54
○ 2026-08-31 01:21:14

●MXroute1.mx.cloudflare.net2026-08-26 → 2026-08-31 · 3 obs

○ 2017-05-09 01:19:38
● 2026-08-26 03:33:54
● 2026-08-31 01:21:14

●MXroute2.mx.cloudflare.net2026-08-26 → 2026-08-31 · 3 obs

○ 2017-05-09 01:19:38
● 2026-08-26 03:33:54
● 2026-08-31 01:21:14

●MXroute3.mx.cloudflare.net2026-08-26 → 2026-08-31 · 3 obs

○ 2017-05-09 01:19:38
● 2026-08-26 03:33:54
● 2026-08-31 01:21:14

○A103.211.216.1372017-05-09 → 2017-05-09 · 3 obs

● 2017-05-09 01:19:38
○ 2026-08-26 03:33:54
○ 2026-08-31 01:21:14

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
code-kracker.com	lindsey.ns.cloudflare.com, jarred.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.194.5

NS records: lindsey.ns.cloudflare.com, jarred.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for code-kracker.com (unsigned zone)

⏱️ Timing

Total: 272ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`jarred.ns.cloudflare.com, lindsey.ns.cloudflare.com`
MX	3	`route3.mx.cloudflare.net (pri: 12), route2.mx.cloudflare.net (pri: 25)...`
TXT	1	`v=spf1 include:_spf.mx.cloudflare.net ~a`
SOA	1	`jarred.ns.cloudflare.com dns.cloudflare.`

📌 Glue Records Collected

Total: 12

Out-of-bailiwick: 12 (lindsey.ns.cloudflare.com, lindsey.ns.cloudflare.com, lindsey.ns.cloudflare.com...)

Analysis

Name Servers

The NS records for code-kracker.com delegate to jarred.ns.cloudflare.com and lindsey.ns.cloudflare.com.

code-kracker.com has the same name server delegation as a number of other domains, such as tiendaplusinc.com, palletvera.com, area-5.com and two more.

code-kracker.com partially shares its NS delegation with several other domains, including rachan789-main.com, nardeen.pages.dev, sande91ep.workers.dev and two others.

These name servers are regularly seen alongside nancy.ns.cloudflare.com and chloe.ns.cloudflare.com as name servers.

Host names resolving to 6 IP numbers:

jarred.ns.cloudflare.com maps to 108.162.195.126, 162.159.44.126, 172.64.35.126 and 3 additional IP addresses.

lindsey.ns.cloudflare.com maps to 108.162.194.5, 162.159.38.5, 172.64.34.5 and 3 additional IP addresses.

Mail Servers

code-kracker.com uses three mail servers — route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

code-kracker.com shares at least some of its mail servers with other domains — for example alegisrevenue.com, 4bfreightincorporated.com, orad-cam.com and two more.

Host names resolving to 6 IP numbers:

route1.mx.cloudflare.net maps to 162.159.205.11, 162.159.205.12, 162.159.205.13 and 3 additional IP addresses.

route2.mx.cloudflare.net maps to 162.159.205.17, 162.159.205.18, 162.159.205.19 and 3 additional IP addresses.

route3.mx.cloudflare.net maps to 162.159.205.23, 162.159.205.24, 162.159.205.25 and 3 additional IP addresses.

code-kracker.com - robtex.com

code-kracker.com

com

Previously MX for

Same first word

Previous names

Next names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

Name Servers

Mail Servers

`code-kracker.com`

`com`