`ipfsscan.io`

DNSSEC	🔒 Signed (DS record present)
A	2606:4700:3032::6815:d81^{🇺🇸 Cloudflare2606:4700:3032::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3036::ac43:c80e^{🇺🇸 Cloudflare2606:4700:3036::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.13.129^{Cloudflare104.21.0.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.200.14^{🇺🇸 Cloudflare172.67.192.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`jim.ns.cloudflare.com` ⭐
		A	2606:4700:58::adf5:3b7d^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jim.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c17d^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`jim.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:217d^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`jim.ns.cloudflare.com`
		A	108.162.193.125^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jim.ns.cloudflare.com`
		A	172.64.33.125^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jim.ns.cloudflare.com`
		A	173.245.59.125^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jim.ns.cloudflare.com`
NS	`pam.ns.cloudflare.com`
		A	2606:4700:50::adf5:3a8a^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`pam.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c08a^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`pam.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:208a^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`pam.ns.cloudflare.com`
		A	108.162.192.138^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`pam.ns.cloudflare.com`
		A	172.64.32.138^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`pam.ns.cloudflare.com`
		A	173.245.58.138^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`pam.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	`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`
TXT	`google-site-verification=a3s1r1xNzA5sMTjk0huXLcKtintGU2QPT-92h1jFyRo`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4	104.21.13.129, 172.67.200.14
		IPv6	2606:4700:3032::6815:d81, 2606:4700:3036::ac43:c80e
SOA	`jim.ns.cloudflare.com`dns@cloudflare.com serial=2399953010

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

📈 Tranco rank: #95,831

Subdomains

tracker.ipfsscan.io

Same first word

ipfsscan.io

Similar names

fanspics.net

fanspics.com

DNS History

9 records (9 active, 0 former)

●NSjim.ns.cloudflare.com2026-02-26 → 2026-03-27 · 2 obs

● 2026-02-26 20:01:52
● 2026-03-27 19:21:50

●NSpam.ns.cloudflare.com2026-02-26 → 2026-03-27 · 2 obs

● 2026-02-26 20:01:52
● 2026-03-27 19:21:50

●MXroute1.mx.cloudflare.net2026-02-26 → 2026-03-27 · 2 obs

● 2026-02-26 20:01:52
● 2026-03-27 19:21:50

●MXroute2.mx.cloudflare.net2026-02-26 → 2026-03-27 · 2 obs

● 2026-02-26 20:01:52
● 2026-03-27 19:21:50

●MXroute3.mx.cloudflare.net2026-02-26 → 2026-03-27 · 2 obs

● 2026-02-26 20:01:52
● 2026-03-27 19:21:50

●A104.21.13.1292026-02-26 → 2026-03-27 · 2 obs

● 2026-02-26 20:01:52
● 2026-03-27 19:21:50

●A172.67.200.142026-02-26 → 2026-03-27 · 2 obs

● 2026-02-26 20:01:52
● 2026-03-27 19:21:50

●A2606:4700:3032::6815:d812026-02-26 → 2026-03-27 · 2 obs

● 2026-02-26 20:01:52
● 2026-03-27 19:21:50

●A2606:4700:3036::ac43:c80e2026-02-26 → 2026-03-27 · 2 obs

● 2026-02-26 20:01:52
● 2026-03-27 19:21:50

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
io	b0.nic.io, a0.nic.io, a2.nic.io, c0.nic.io	-
ipfsscan.io	pam.ns.cloudflare.com, jim.ns.cloudflare.com	-

✅ Authoritative Response

Server:172.64.32.138

NS records: pam.ns.cloudflare.com, jim.ns.cloudflare.com

🔒 DNSSEC Status

🔐 Secure (DNSSEC validated)

Chain of trust verified from root to domain

⏱️ Timing

Total: 2843ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.200.14, 104.21.13.129`
AAAA	2	`2606:4700:3032::6815:d81, 2606:4700:3036::ac43:c80e`
NS	2	`jim.ns.cloudflare.com, pam.ns.cloudflare.com`
MX	3	`route3.mx.cloudflare.net (pri: 57), route1.mx.cloudflare.net (pri: 63)...`
TXT	2	`google-site-verification=a3s1r1xNzA5sMTj, v=spf1 include:_spf.mx.cloudflare.net ~a`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`jim.ns.cloudflare.com dns.cloudflare.com`

Analysis

Hierarchy

ipfsscan.io is a parent of tracker.ipfsscan.io.

IP Addresses

ipfsscan.io resolves to four IPs: 2606:4700:3032::6815:d81, 2606:4700:3036::ac43:c80e, 104.21.13.129 and 172.67.200.14.

Other host names such as 3sheen.com, galo.com.ar, confezionicavalleri.it, tracker-plus.co.uk and joyotogelubi.xyz share IP numbers with ipfsscan.io.

Name Servers

ipfsscan.io is delegated to two name servers: jim.ns.cloudflare.com and pam.ns.cloudflare.com.

ipfsscan.io uses the same name server setup as other domains, including gilix.com.br, oraapex.com, globalcool.org, newai.vn and xaluan.net.

At least part of the name servers for ipfsscan.io are shared with other domains, for instance ukneqash.org, deankotula.com, appinme.com, imeteo.sk and sportsbackers.com.

These name servers are commonly used alongside vasilii.ns.cloudflare.com and carrera.ns.cloudflare.com.

Host names with six IP numbers:

jim.ns.cloudflare.com points to: 2606:4700:58::adf5:3b7d, 2803:f800:50::6ca2:c17d, 2a06:98c1:50::ac40:217d, 108.162.193.125, 172.64.33.125 and 173.245.59.125.

pam.ns.cloudflare.com points to: 2606:4700:50::adf5:3a8a, 2803:f800:50::6ca2:c08a, 2a06:98c1:50::ac40:208a, 108.162.192.138, 172.64.32.138 and 173.245.58.138.

Mail Servers

Three mail servers handle ipfsscan.io: route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

ipfsscan.io shares at least some mail servers with other domains, for example conectapages.com, silviustroe.com, dbree.nl, hupsa.be and plare.fr.

Host names with six IP numbers: route1.mx.cloudflare.net points to 2606:4700:f5::b, 2606:4700:f5::c, 2606:4700:f5::d, 162.159.205.11, 162.159.205.12 and 162.159.205.13; route2.mx.cloudflare.net points to 2606:4700:f5::e, 2606:4700:f5::f, 2606:4700:f5::10, 162.159.205.17, 162.159.205.18 and 162.159.205.19; route3.mx.cloudflare.net points to 2606:4700:f5::11, 2606:4700:f5::12, 2606:4700:f5::13, 162.159.205.23, 162.159.205.24 and 162.159.205.25.

ipfsscan.io - robtex.com

ipfsscan.io

io

Subdomains

Same first word

Similar names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

Analysis

Hierarchy

IP Addresses

Name Servers

Mail Servers

`ipfsscan.io`

`io`