🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`algorithmchallenge.org`

DNSSEC	⚠️ Not signed
A	2606:4700:3030::6815:b87^{🇺🇸 Cloudflare2606:4700:3030::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3036::ac43:a621^{🇺🇸 Cloudflare2606:4700:3036::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.11.135^{Cloudflare104.21.0.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.166.33^{🇺🇸 Cloudflare172.67.160.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`annalise.ns.cloudflare.com` ⭐
		A	2606:4700:50::a29f:26ea^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`annalise.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c2ea^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`annalise.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:22ea^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`annalise.ns.cloudflare.com`
		A	108.162.194.234^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`annalise.ns.cloudflare.com`
		A	162.159.38.234^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`annalise.ns.cloudflare.com`
		A	172.64.34.234^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`annalise.ns.cloudflare.com`
NS	`jeremy.ns.cloudflare.com`
		A	2606:4700:58::adf5:3bb4^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jeremy.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c1b4^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`jeremy.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:21b4^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`jeremy.ns.cloudflare.com`
		A	108.162.193.180^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jeremy.ns.cloudflare.com`
		A	172.64.33.180^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jeremy.ns.cloudflare.com`
		A	173.245.59.180^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jeremy.ns.cloudflare.com`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.11.135, 172.67.166.33
		IPv6 hints	2606:4700:3030::6815:b87, 2606:4700:3036::ac43:a621
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=49, name=cloudflare-ech.com
SOA	`annalise.ns.cloudflare.com`dns@cloudflare.com serial=2413185344

`org`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a0.org.afilias-nst.info` ⭐ ⚠️ Not in parent delegation
	NS	`a2.org.afilias-nst.info` ⚠️ Not in parent delegation
	NS	`b0.org.afilias-nst.org`
	NS	`b2.org.afilias-nst.org`
	NS	`c0.org.afilias-nst.info` ⚠️ Not in parent delegation
	NS	`d0.org.afilias-nst.org`
	SOA	`a0.org.afilias-nst.info`hostmaster@donuts.email serial=1788743240

Same first word

algorithmchallenge.org

Previous names

Next names

DNS History

6 records (6 active, 0 former)

●NSannalise.ns.cloudflare.com2026-09-04 → 2026-09-07 · 2 obs

● 2026-09-04 05:28:44
● 2026-09-07 01:37:02

●NSjeremy.ns.cloudflare.com2026-09-04 → 2026-09-07 · 2 obs

● 2026-09-04 05:28:44
● 2026-09-07 01:37:02

●A104.21.11.1352026-09-04 → 2026-09-07 · 2 obs

● 2026-09-04 05:28:44
● 2026-09-07 01:37:02

●A172.67.166.332026-09-04 → 2026-09-07 · 2 obs

● 2026-09-04 05:28:44
● 2026-09-07 01:37:02

●A2606:4700:3030::6815:b872026-09-04 → 2026-09-07 · 2 obs

● 2026-09-04 05:28:44
● 2026-09-07 01:37:02

●A2606:4700:3036::ac43:a6212026-09-04 → 2026-09-07 · 2 obs

● 2026-09-04 05:28:44
● 2026-09-07 01:37:02

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
org	b0.org.afilias-nst.org, b2.org.afilias-nst.org, d0.org.afilias-nst.org	-
algorithmchallenge.org	jeremy.ns.cloudflare.com, annalise.ns.cloudflare.com	-

✅ Authoritative Response

Server:108.162.193.180

NS records: jeremy.ns.cloudflare.com, annalise.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for algorithmchallenge.org (unsigned zone)

⏱️ Timing

Total: 1166ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.166.33, 104.21.11.135`
AAAA	2	`2606:4700:3036::ac43:a621, 2606:4700:3030::6815:b87`
NS	2	`annalise.ns.cloudflare.com, jeremy.ns.cloudflare.com`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`annalise.ns.cloudflare.com dns.cloudflar`

Analysis

IP Addresses

algorithmchallenge.org has four IP addresses: 104.21.11.135, 172.67.166.33, 2606:4700:3030::6815:b87 and 2606:4700:3036::ac43:a621.

Additional host names — beidougames.com, acluvamerica.com, moonwin-online-casinos.com and two others — share IP numbers with algorithmchallenge.org.

Name Servers

The NS records for algorithmchallenge.org delegate to annalise.ns.cloudflare.com and jeremy.ns.cloudflare.com.

algorithmchallenge.org shares its name server setup with other domains, including alonegaming9416.workers.dev, polihuh.workers.dev, orchilira.store and two others.

algorithmchallenge.org has at least partial name server overlap with other domains, such as expandriumq.co, 67660050.com, iallowyoutoseewhatihavefornow.com and two others.

It is common to see these name servers used together with name servers dina.ns.cloudflare.com and noah.ns.cloudflare.com.

Host names with 6 IP numbers:

annalise.ns.cloudflare.com maps to 108.162.194.234, 162.159.38.234, 172.64.34.234 and 3 additional IP addresses.

jeremy.ns.cloudflare.com maps to 108.162.193.180, 172.64.33.180, 173.245.59.180 and 3 additional IP addresses.

algorithmchallenge.org - robtex.com