🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`problemcracker.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3031::6815:371a^{🇺🇸 Cloudflare2606:4700:3031::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3031::ac43:9024^{🇺🇸 Cloudflare2606:4700:3031::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.55.26^{Cloudflare104.21.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.144.36^{🇺🇸 Cloudflare172.67.144.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`kareem.ns.cloudflare.com` ⭐
		A	2606:4700:58::a29f:2c16^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kareem.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c316^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`kareem.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2316^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`kareem.ns.cloudflare.com`
		A	108.162.195.22^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	162.159.44.22^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	172.64.35.22^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`lia.ns.cloudflare.com`
		A	2606:4700:50::adf5:3ab9^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lia.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c0b9^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`lia.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:20b9^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`lia.ns.cloudflare.com`
		A	108.162.192.185^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lia.ns.cloudflare.com`
		A	172.64.32.185^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lia.ns.cloudflare.com`
		A	173.245.58.185^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lia.ns.cloudflare.com`
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	`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	`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`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.55.26, 172.67.144.36
		IPv6 hints	2606:4700:3031::6815:371a, 2606:4700:3031::ac43:9024
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=118, name=cloudflare-ech.com
SOA	`kareem.ns.cloudflare.com`dns@cloudflare.com serial=2416179805

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

Previously MX for

problemcracker.com

Same first word

problemcracker.com

Previous names

Next names

DNS History

23 records (9 active, 14 former)

●NSkareem.ns.cloudflare.com2026-09-30 → 2026-10-02 · 3 obs

○ 2026-09-14 08:47:38
● 2026-09-30 12:19:50
● 2026-10-02 21:25:52

●NSlia.ns.cloudflare.com2026-09-30 → 2026-10-02 · 3 obs

○ 2026-09-14 08:47:38
● 2026-09-30 12:19:50
● 2026-10-02 21:25:52

○NSns0.wixdns.net2017-02-05 → 2017-02-05 · 3 obs

● 2017-02-05 23:25:18
○ 2020-02-19 23:56:10
○ 2026-10-02 21:25:52

○NSns1.guzelhosting.com2026-09-14 → 2026-09-14 · 4 obs

○ 2020-02-19 23:56:10
● 2026-09-14 08:47:38
○ 2026-09-30 12:19:50
○ 2026-10-02 21:25:52

○NSns1.wixdns.net2017-02-05 → 2017-02-05 · 3 obs

● 2017-02-05 23:25:18
○ 2020-02-19 23:56:10
○ 2026-10-02 21:25:52

○NSns11.guzelhosting.com2026-09-14 → 2026-09-14 · 4 obs

○ 2020-02-19 23:56:10
● 2026-09-14 08:47:38
○ 2026-09-30 12:19:50
○ 2026-10-02 21:25:52

○NSns12.guzelhosting.com2026-09-14 → 2026-09-14 · 4 obs

○ 2020-02-19 23:56:10
● 2026-09-14 08:47:38
○ 2026-09-30 12:19:50
○ 2026-10-02 21:25:52

○NSns2.guzelhosting.com2026-09-14 → 2026-09-14 · 4 obs

○ 2020-02-19 23:56:10
● 2026-09-14 08:47:38
○ 2026-09-30 12:19:50
○ 2026-10-02 21:25:52

○MXalt1.aspmx.l.google.com2017-02-05 → 2017-02-05 · 3 obs

● 2017-02-05 23:25:18
○ 2020-02-19 23:56:10
○ 2026-10-02 21:25:52

○MXalt2.aspmx.l.google.com2017-02-05 → 2017-02-05 · 3 obs

● 2017-02-05 23:25:18
○ 2020-02-19 23:56:10
○ 2026-10-02 21:25:52

○MXaspmx.l.google.com2017-02-05 → 2017-02-05 · 3 obs

● 2017-02-05 23:25:18
○ 2020-02-19 23:56:10
○ 2026-10-02 21:25:52

○MXaspmx2.googlemail.com2017-02-05 → 2017-02-05 · 3 obs

● 2017-02-05 23:25:18
○ 2020-02-19 23:56:10
○ 2026-10-02 21:25:52

○MXaspmx3.googlemail.com2017-02-05 → 2017-02-05 · 3 obs

● 2017-02-05 23:25:18
○ 2020-02-19 23:56:10
○ 2026-10-02 21:25:52

○MXproblemcracker.com2026-09-14 → 2026-09-14 · 4 obs

○ 2020-02-19 23:56:10
● 2026-09-14 08:47:38
○ 2026-09-30 12:19:50
○ 2026-10-02 21:25:52

●MXroute1.mx.cloudflare.net2026-09-30 → 2026-10-02 · 3 obs

○ 2026-09-14 08:47:38
● 2026-09-30 12:19:50
● 2026-10-02 21:25:52

●MXroute2.mx.cloudflare.net2026-09-30 → 2026-10-02 · 3 obs

○ 2026-09-14 08:47:38
● 2026-09-30 12:19:50
● 2026-10-02 21:25:52

●MXroute3.mx.cloudflare.net2026-09-30 → 2026-10-02 · 3 obs

○ 2026-09-14 08:47:38
● 2026-09-30 12:19:50
● 2026-10-02 21:25:52

●A104.21.55.262026-09-30 → 2026-10-02 · 3 obs

○ 2026-09-14 08:47:38
● 2026-09-30 12:19:50
● 2026-10-02 21:25:52

●A172.67.144.362026-09-30 → 2026-10-02 · 3 obs

○ 2026-09-14 08:47:38
● 2026-09-30 12:19:50
● 2026-10-02 21:25:52

○A23.236.62.1472017-02-05 → 2017-02-05 · 3 obs

● 2017-02-05 23:25:18
○ 2020-02-19 23:56:10
○ 2026-10-02 21:25:52

●A2606:4700:3031::6815:371a2026-09-30 → 2026-10-02 · 3 obs

○ 2026-09-14 08:47:38
● 2026-09-30 12:19:50
● 2026-10-02 21:25:52

●A2606:4700:3031::ac43:90242026-09-30 → 2026-10-02 · 3 obs

○ 2026-09-14 08:47:38
● 2026-09-30 12:19:50
● 2026-10-02 21:25:52

○A5.135.76.1282026-09-14 → 2026-09-14 · 4 obs

○ 2020-02-19 23:56:10
● 2026-09-14 08:47:38
○ 2026-09-30 12:19:50
○ 2026-10-02 21:25:52

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, g.gtld-servers.net...	-
problemcracker.com	lia.ns.cloudflare.com, kareem.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.192.185

NS records: lia.ns.cloudflare.com, kareem.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for problemcracker.com (unsigned zone)

⏱️ Timing

Total: 678ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.55.26, 172.67.144.36`
AAAA	2	`2606:4700:3031::6815:371a, 2606:4700:3031::ac43:9024`
NS	2	`kareem.ns.cloudflare.com, lia.ns.cloudflare.com`
MX	3	`route2.mx.cloudflare.net (pri: 29), route3.mx.cloudflare.net (pri: 40)...`
TXT	1	`v=spf1 include:_spf.mx.cloudflare.net ~a`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`kareem.ns.cloudflare.com dns.cloudflare.`

📌 Glue Records Collected

Total: 12

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

Analysis

IP Addresses

problemcracker.com points to the four IP addresses 104.21.55.26, 172.67.144.36, 2606:4700:3031::6815:371a and 2606:4700:3031::ac43:9024.

Additional host names — geg777pag.com, dpc.rs, snspmhnp.com and two others — share IP numbers with problemcracker.com.

Name Servers

Two name servers handle the delegation for problemcracker.com: kareem.ns.cloudflare.com and lia.ns.cloudflare.com.

problemcracker.com shares its name server setup with other domains, including mmm-177.pages.dev, potflow.workers.dev, vgiks42381.workers.dev and two others.

There is at least partial name server overlap between problemcracker.com and other domains — nkgworks-learning.pages.dev, ezoteriksanat.com, saranbranda.com and two more among them.

The name servers lady.ns.cloudflare.com, kinsley.ns.cloudflare.com and gabe.ns.cloudflare.com are often found in combination with these name servers.

Host names with 6 IP numbers:

kareem.ns.cloudflare.com resolves to 108.162.195.22, 162.159.44.22 and 172.64.35.22 among others, with 3 other IP addresses in total.

lia.ns.cloudflare.com resolves to 108.162.192.185, 172.64.32.185 and 173.245.58.185 among others, with 3 other IP addresses in total.

Mail Servers

Incoming mail for problemcracker.com is delivered via three mail servers: route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

problemcracker.com shares mail servers — at least in part — with other domains, including allratios.com, bypbw.com, 5280-flooring.com and two others.

Host names with 6 IP numbers:

route1.mx.cloudflare.net resolves to 162.159.205.11, 162.159.205.12 and 162.159.205.13 among others, with 3 other IP addresses in total.

route2.mx.cloudflare.net resolves to 162.159.205.17, 162.159.205.18 and 162.159.205.19 among others, with 3 other IP addresses in total.

route3.mx.cloudflare.net resolves to 162.159.205.23, 162.159.205.24 and 162.159.205.25 among others, with 3 other IP addresses in total.

problemcracker.com - robtex.com