🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`lostcode.io`

DNSSEC	⚠️ Not signed
A	2606:4700:3030::ac43:8b5e^{🇺🇸 Cloudflare2606:4700:3030::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3032::6815:4112^{🇺🇸 Cloudflare2606:4700:3032::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.65.18^{Cloudflare104.21.64.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.139.94^{🇺🇸 Cloudflare172.67.128.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`elma.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3a9a^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`elma.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c09a^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`elma.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:209a^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`elma.ns.cloudflare.com`
		A	108.162.192.154^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`elma.ns.cloudflare.com`
		A	172.64.32.154^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`elma.ns.cloudflare.com`
		A	173.245.58.154^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`elma.ns.cloudflare.com`
NS	`rommy.ns.cloudflare.com`
		A	2606:4700:58::a29f:2c14^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rommy.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c314^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`rommy.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2314^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`rommy.ns.cloudflare.com`
		A	108.162.195.20^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rommy.ns.cloudflare.com`
		A	162.159.44.20^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rommy.ns.cloudflare.com`
		A	172.64.35.20^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rommy.ns.cloudflare.com`
MX	`mx2.zoho.com` ⭐
		A	204.141.33.44^{🇺🇸 ZohoAS204.141.32.0/23 PNAP-DAL CASE00103239}
			PTR	`mx2.zoho.com`
			PTR	`mx3.zoho.com`
			PTR	`mx6.zoho.com`
			PTR	`mx7.zoho.com`
			PTR	`mx8.zoho.com`
			PTR	`mx.zoho.com`
			PTR	`mx2.zohomail.com`
			PTR	`mx3.zohomail.com`
			PTR	`mx.zohomail.com`
		A	204.141.43.44^{🇺🇸 ZohoAS204.141.42.0/23 Zoho Corporation}
			PTR	`mx2.zoho.com`
			PTR	`mx3.zoho.com`
			PTR	`mx6.zoho.com`
			PTR	`mx7.zoho.com`
			PTR	`mx8.zoho.com`
			PTR	`mx.zoho.com`
			PTR	`mx2.zohomail.com`
			PTR	`mx3.zohomail.com`
			PTR	`mx.zohomail.com`
MX	`mx3.zoho.com`⁽²⁰⁾
		A	204.141.43.44^{🇺🇸 ZohoAS204.141.42.0/23 Zoho Corporation}
			PTR	`mx2.zoho.com`
			PTR	`mx3.zoho.com`
			PTR	`mx6.zoho.com`
			PTR	`mx7.zoho.com`
			PTR	`mx8.zoho.com`
			PTR	`mx.zoho.com`
			PTR	`mx2.zohomail.com`
			PTR	`mx3.zohomail.com`
			PTR	`mx.zohomail.com`
MX	`mx.zoho.com`⁽⁵⁰⁾
		A	136.143.183.44^{🇺🇸 ZohoAS136.143.182.0/23 Zoho}
			PTR	`mx2.zoho.com`
			PTR	`mx3.zoho.com`
			PTR	`mx.zoho.com`
			PTR	`mx2.zohomail.com`
			PTR	`mx3.zohomail.com`
			PTR	`mx.zohomail.com`
		A	204.141.43.44^{🇺🇸 ZohoAS204.141.42.0/23 Zoho Corporation}
			PTR	`mx2.zoho.com`
			PTR	`mx3.zoho.com`
			PTR	`mx6.zoho.com`
			PTR	`mx7.zoho.com`
			PTR	`mx8.zoho.com`
			PTR	`mx.zoho.com`
			PTR	`mx2.zohomail.com`
			PTR	`mx3.zohomail.com`
			PTR	`mx.zohomail.com`
TXT	`v=spf1 include:zoho.com ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.65.18, 172.67.139.94
		IPv6 hints	2606:4700:3030::ac43:8b5e, 2606:4700:3032::6815:4112
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=81, name=cloudflare-ech.com
SOA	`elma.ns.cloudflare.com`dns@cloudflare.com serial=2412538610

`io`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a0.nic.io` ⭐
	NS	`a2.nic.io`
	NS	`b0.nic.io`
	NS	`c0.nic.io`
	SOA	`a0.nic.io`hostmaster@donuts.email serial=1788675677

Same first word

lostcode.lv

lostcode.com.mx

lostcode.cyou

lostcode.io

lostcode.altervista.org

lostcode.ru

lostcode.de

Similar names

Previous names

Next names

DNS History

9 records (9 active, 0 former)

●NSelma.ns.cloudflare.com2026-08-28 → 2026-09-06 · 2 obs

● 2026-08-28 14:11:10
● 2026-09-06 06:45:34

●NSrommy.ns.cloudflare.com2026-08-28 → 2026-09-06 · 2 obs

● 2026-08-28 14:11:10
● 2026-09-06 06:45:34

●MXmx.zoho.com2026-08-28 → 2026-09-06 · 2 obs

● 2026-08-28 14:11:10
● 2026-09-06 06:45:34

●MXmx2.zoho.com2026-08-28 → 2026-09-06 · 2 obs

● 2026-08-28 14:11:10
● 2026-09-06 06:45:34

●MXmx3.zoho.com2026-08-28 → 2026-09-06 · 2 obs

● 2026-08-28 14:11:10
● 2026-09-06 06:45:34

●A104.21.65.182026-08-28 → 2026-09-06 · 2 obs

● 2026-08-28 14:11:10
● 2026-09-06 06:45:34

●A172.67.139.942026-08-28 → 2026-09-06 · 2 obs

● 2026-08-28 14:11:10
● 2026-09-06 06:45:34

●A2606:4700:3030::ac43:8b5e2026-08-28 → 2026-09-06 · 2 obs

● 2026-08-28 14:11:10
● 2026-09-06 06:45:34

●A2606:4700:3032::6815:41122026-08-28 → 2026-09-06 · 2 obs

● 2026-08-28 14:11:10
● 2026-09-06 06:45:34

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
io	a0.nic.io, a2.nic.io, b0.nic.io, c0.nic.io	8 records
lostcode.io	elma.ns.cloudflare.com, rommy.ns.cloudflare.com	-

✅ Authoritative Response

Server:108.162.192.154

NS records: elma.ns.cloudflare.com, rommy.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for lostcode.io (unsigned zone)

⏱️ Timing

Total: 1266ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.65.18, 172.67.139.94`
AAAA	2	`2606:4700:3030::ac43:8b5e, 2606:4700:3032::6815:4112`
NS	2	`elma.ns.cloudflare.com, rommy.ns.cloudflare.com`
MX	3	`mx.zoho.com (pri: 10), mx2.zoho.com (pri: 20)...`
TXT	1	`v=spf1 include:zoho.com ~all`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`elma.ns.cloudflare.com dns.cloudflare.co`

📌 Glue Records Collected

Total: 8

In-bailiwick: 8 (a0.nic.io, a0.nic.io, a2.nic.io...)

Analysis

IP Addresses

lostcode.io has four IP addresses: 104.21.65.18, 172.67.139.94, 2606:4700:3030::ac43:8b5e and 2606:4700:3032::6815:4112.

Additional host names — (0x706f726e687562)1.shop, bizsuccessstory.com, fotografieforum.at and two others — share IP numbers with lostcode.io.

Name Servers

DNS delegation for lostcode.io points to two name servers: elma.ns.cloudflare.com and rommy.ns.cloudflare.com.

lostcode.io shares its name server setup with other domains, including megakindo-u0zu.pages.dev, floral-bar-48c5.workers.dev, 1125323804.workers.dev and two others.

lostcode.io partially shares its NS delegation with several other domains, including gutkaufen.com, xjsp26.cc, prayer-trainer.pages.dev and two others.

These name servers are regularly seen alongside west.ns.cloudflare.com and kai.ns.cloudflare.com as name servers.

Host names with 6 IP numbers:

elma.ns.cloudflare.com has IP addresses 108.162.192.154, 172.64.32.154 and 173.245.58.154, plus 3 other.

rommy.ns.cloudflare.com has IP addresses 108.162.195.20, 162.159.44.20 and 172.64.35.20, plus 3 other.

Mail Servers

lostcode.io uses three mail servers — mx2.zoho.com, mx3.zoho.com and mx.zoho.com.

lostcode.io shares mail servers — at least in part — with other domains, including lynxmagnus.com, cloudbooksacademy.com, surprisewithlove.com and two others.

Host names with two IP numbers:

mx2.zoho.com has two IP addresses: 204.141.33.44 and 204.141.43.44.

mx.zoho.com has two IP addresses: 136.143.183.44 and 204.141.43.44.

Host names pointing to a single IP address:

mx3.zoho.com directs to 204.141.43.44.

mx2.zoho.com, mx.zoho.com and mx3.zoho.com are host names that all point to 204.141.43.44.

lostcode.io - robtex.com

lostcode.io

io

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

`lostcode.io`

`io`