🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`fixchallenge.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3030::6815:174f^{🇺🇸 Cloudflare2606:4700:3030::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3032::ac43:d1cd^{🇺🇸 Cloudflare2606:4700:3032::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.23.79^{Cloudflare104.21.16.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.209.205^{🇺🇸 Cloudflare172.67.208.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`aspen.ns.cloudflare.com` ⭐
		A	2606:4700:50::a29f:266d^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`aspen.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c26d^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`aspen.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:226d^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`aspen.ns.cloudflare.com`
		A	108.162.194.109^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`aspen.ns.cloudflare.com`
		A	162.159.38.109^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`aspen.ns.cloudflare.com`
		A	172.64.34.109^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`aspen.ns.cloudflare.com`
NS	`gordon.ns.cloudflare.com`
		A	2606:4700:58::adf5:3baa^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`gordon.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c1aa^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`gordon.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:21aa^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`gordon.ns.cloudflare.com`
		A	108.162.193.170^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`gordon.ns.cloudflare.com`
		A	172.64.33.170^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`gordon.ns.cloudflare.com`
		A	173.245.59.170^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`gordon.ns.cloudflare.com`
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`
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`
TXT	`google-site-verification=RMKmSFDjkVBaDb7ZpLDY2KZYL5sD1o20jcSIlfRfbb0`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.23.79, 172.67.209.205
		IPv6 hints	2606:4700:3030::6815:174f, 2606:4700:3032::ac43:d1cd
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=162, name=cloudflare-ech.com
SOA	`aspen.ns.cloudflare.com`dns@cloudflare.com serial=2411048672

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

Previously MX for

fixchallenge.com

Same first word

fixchallenge.com

Similar names

fillexchange.com

Previous names

Next names

DNS History

17 records (9 active, 8 former)

●NSaspen.ns.cloudflare.com2026-08-18 → 2026-08-19 · 3 obs

○ 2017-05-15 10:10:24
● 2026-08-18 03:51:56
● 2026-08-19 20:42:36

●NSgordon.ns.cloudflare.com2026-08-18 → 2026-08-19 · 3 obs

○ 2017-05-15 10:10:24
● 2026-08-18 03:51:56
● 2026-08-19 20:42:36

○NSns1.dnslink.com2017-05-15 → 2017-05-15 · 4 obs

○ 2016-09-12 04:37:50
● 2017-05-15 10:10:24
○ 2026-08-18 03:51:56
○ 2026-08-19 20:42:36

○NSns1.icontent.com2015-05-14 → 2016-09-12 · 4 obs

● 2015-05-14 05:01:38
● 2016-09-12 04:37:50
○ 2017-05-15 10:10:24
○ 2026-08-19 20:42:36

○NSns2.dnslink.com2017-05-15 → 2017-05-15 · 4 obs

○ 2016-09-12 04:37:50
● 2017-05-15 10:10:24
○ 2026-08-18 03:51:56
○ 2026-08-19 20:42:36

○NSns2.icontent.com2015-05-14 → 2016-09-12 · 4 obs

● 2015-05-14 05:01:38
● 2016-09-12 04:37:50
○ 2017-05-15 10:10:24
○ 2026-08-19 20:42:36

○MXfixchallenge.com2015-05-14 → 2016-09-12 · 4 obs

● 2015-05-14 05:01:38
● 2016-09-12 04:37:50
○ 2017-05-15 10:10:24
○ 2026-08-19 20:42:36

○MXmail.b-io.co2017-05-15 → 2017-05-15 · 4 obs

○ 2016-09-12 04:37:50
● 2017-05-15 10:10:24
○ 2026-08-18 03:51:56
○ 2026-08-19 20:42:36

●MXroute1.mx.cloudflare.net2026-08-18 → 2026-08-19 · 3 obs

○ 2017-05-15 10:10:24
● 2026-08-18 03:51:56
● 2026-08-19 20:42:36

●MXroute2.mx.cloudflare.net2026-08-18 → 2026-08-19 · 3 obs

○ 2017-05-15 10:10:24
● 2026-08-18 03:51:56
● 2026-08-19 20:42:36

●MXroute3.mx.cloudflare.net2026-08-18 → 2026-08-19 · 3 obs

○ 2017-05-15 10:10:24
● 2026-08-18 03:51:56
● 2026-08-19 20:42:36

○A104.130.196.2532015-05-14 → 2016-09-12 · 4 obs

● 2015-05-14 05:01:38
● 2016-09-12 04:37:50
○ 2017-05-15 10:10:24
○ 2026-08-19 20:42:36

●A104.21.23.792026-08-18 → 2026-08-19 · 3 obs

○ 2017-05-15 10:10:24
● 2026-08-18 03:51:56
● 2026-08-19 20:42:36

●A172.67.209.2052026-08-18 → 2026-08-19 · 3 obs

○ 2017-05-15 10:10:24
● 2026-08-18 03:51:56
● 2026-08-19 20:42:36

○A209.15.13.1342017-05-15 → 2017-05-15 · 4 obs

○ 2016-09-12 04:37:50
● 2017-05-15 10:10:24
○ 2026-08-18 03:51:56
○ 2026-08-19 20:42:36

●A2606:4700:3030::6815:174f2026-08-18 → 2026-08-19 · 3 obs

○ 2017-05-15 10:10:24
● 2026-08-18 03:51:56
● 2026-08-19 20:42:36

●A2606:4700:3032::ac43:d1cd2026-08-18 → 2026-08-19 · 3 obs

○ 2017-05-15 10:10:24
● 2026-08-18 03:51:56
● 2026-08-19 20:42:36

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
fixchallenge.com	gordon.ns.cloudflare.com, aspen.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:162.159.38.109

NS records: gordon.ns.cloudflare.com, aspen.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for fixchallenge.com (unsigned zone)

⏱️ Timing

Total: 302ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.23.79, 172.67.209.205`
AAAA	2	`2606:4700:3030::6815:174f, 2606:4700:3032::ac43:d1cd`
NS	2	`aspen.ns.cloudflare.com, gordon.ns.cloudflare.com`
MX	3	`route1.mx.cloudflare.net (pri: 17), route2.mx.cloudflare.net (pri: 54)...`
TXT	2	`google-site-verification=RMKmSFDjkVBaDb7, v=spf1 include:_spf.mx.cloudflare.net ~a`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`aspen.ns.cloudflare.com dns.cloudflare.c`

📌 Glue Records Collected

Total: 12

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

Analysis

IP Addresses

fixchallenge.com has four IP addresses: 104.21.23.79, 172.67.209.205, 2606:4700:3030::6815:174f and 2606:4700:3032::ac43:d1cd.

Additional host names — wdbuff.com, optera2026analytics.click, suriya-bet.vip and two others — share IP numbers with fixchallenge.com.

Name Servers

fixchallenge.com uses two name servers for its delegation: aspen.ns.cloudflare.com and gordon.ns.cloudflare.com.

fixchallenge.com shares its name server setup with other domains, including itradeonline.com, contentsolution.com, mycart.com and two others.

fixchallenge.com shares at least some of its name servers with other domains, including 00739c4810924ae5.com, tryatlantabridge.info, kingvim.com and two others.

These name servers are frequently seen alongside the name servers nash.ns.cloudflare.com.

Host names with 6 IP numbers:

Hostname aspen.ns.cloudflare.com directs to 108.162.194.109, 162.159.38.109 and 172.64.34.109 along with 3 other IP addresses.

Hostname gordon.ns.cloudflare.com directs to 108.162.193.170, 172.64.33.170 and 173.245.59.170 along with 3 other IP addresses.

Mail Servers

fixchallenge.com is handled by three mail servers: route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

fixchallenge.com shares mail servers — at least in part — with other domains, including liehendr.com, vfitness.us, multikosoft.com and two others.

Host names with 6 IP numbers:

Hostname route1.mx.cloudflare.net directs to 162.159.205.11, 162.159.205.12 and 162.159.205.13 along with 3 other IP addresses.

Hostname route2.mx.cloudflare.net directs to 162.159.205.17, 162.159.205.18 and 162.159.205.19 along with 3 other IP addresses.

Hostname route3.mx.cloudflare.net directs to 162.159.205.23, 162.159.205.24 and 162.159.205.25 along with 3 other IP addresses.

fixchallenge.com - robtex.com