`nanofancy.com`

DNSSEC	⚠️ Not signed
NS	`yoxall.ns.cloudflare.com` ⭐
		A	2606:4700:58::a29f:2c2f^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`yoxall.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c32f^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`yoxall.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:232f^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`yoxall.ns.cloudflare.com`
		A	108.162.195.47^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`yoxall.ns.cloudflare.com`
		A	162.159.44.47^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`yoxall.ns.cloudflare.com`
		A	172.64.35.47^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`yoxall.ns.cloudflare.com`
NS	`ziggy.ns.cloudflare.com`
		A	2606:4700:50::a29f:26ed^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ziggy.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c2ed^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`ziggy.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:22ed^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`ziggy.ns.cloudflare.com`
		A	108.162.194.237^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ziggy.ns.cloudflare.com`
		A	162.159.38.237^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ziggy.ns.cloudflare.com`
		A	172.64.34.237^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ziggy.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	`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	`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	`v=spf1 include:_spf.mx.cloudflare.net ~all`
SOA	`yoxall.ns.cloudflare.com`dns@cloudflare.com serial=2398684008

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

Same first word

nanofancy.com

DNS History

13 records (5 active, 8 former)

○NSdns1.registrar-servers.com2017-03-14 → 2017-03-14 · 3 obs

● 2017-03-14 05:46:54
○ 2026-03-24 02:44:42
○ 2026-04-24 13:20:24

○NSdns2.registrar-servers.com2017-03-14 → 2017-03-14 · 3 obs

● 2017-03-14 05:46:54
○ 2026-03-24 02:44:42
○ 2026-04-24 13:20:24

●NSyoxall.ns.cloudflare.com2026-03-24 → 2026-04-24 · 3 obs

○ 2017-03-14 05:46:54
● 2026-03-24 02:44:42
● 2026-04-24 13:20:24

●NSziggy.ns.cloudflare.com2026-03-24 → 2026-04-24 · 3 obs

○ 2017-03-14 05:46:54
● 2026-03-24 02:44:42
● 2026-04-24 13:20:24

○MXeforward1.registrar-servers.com2017-03-14 → 2017-03-14 · 3 obs

● 2017-03-14 05:46:54
○ 2026-03-24 02:44:42
○ 2026-04-24 13:20:24

○MXeforward2.registrar-servers.com2017-03-14 → 2017-03-14 · 3 obs

● 2017-03-14 05:46:54
○ 2026-03-24 02:44:42
○ 2026-04-24 13:20:24

○MXeforward3.registrar-servers.com2017-03-14 → 2017-03-14 · 3 obs

● 2017-03-14 05:46:54
○ 2026-03-24 02:44:42
○ 2026-04-24 13:20:24

○MXeforward4.registrar-servers.com2017-03-14 → 2017-03-14 · 3 obs

● 2017-03-14 05:46:54
○ 2026-03-24 02:44:42
○ 2026-04-24 13:20:24

○MXeforward5.registrar-servers.com2017-03-14 → 2017-03-14 · 3 obs

● 2017-03-14 05:46:54
○ 2026-03-24 02:44:42
○ 2026-04-24 13:20:24

●MXroute1.mx.cloudflare.net2026-03-24 → 2026-04-24 · 3 obs

○ 2017-03-14 05:46:54
● 2026-03-24 02:44:42
● 2026-04-24 13:20:24

●MXroute2.mx.cloudflare.net2026-03-24 → 2026-04-24 · 3 obs

○ 2017-03-14 05:46:54
● 2026-03-24 02:44:42
● 2026-04-24 13:20:24

●MXroute3.mx.cloudflare.net2026-03-24 → 2026-04-24 · 3 obs

○ 2017-03-14 05:46:54
● 2026-03-24 02:44:42
● 2026-04-24 13:20:24

○A162.255.119.2482017-03-14 → 2017-03-14 · 3 obs

● 2017-03-14 05:46:54
○ 2026-03-24 02:44:42
○ 2026-04-24 13:20:24

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
nanofancy.com	ziggy.ns.cloudflare.com, yoxall.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.194.237

NS records: ziggy.ns.cloudflare.com, yoxall.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for nanofancy.com (unsigned zone)

⏱️ Timing

Total: 166ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`yoxall.ns.cloudflare.com, ziggy.ns.cloudflare.com`
MX	3	`route2.mx.cloudflare.net (pri: 29), route1.mx.cloudflare.net (pri: 41)...`
TXT	1	`v=spf1 include:_spf.mx.cloudflare.net ~a`
SOA	1	`yoxall.ns.cloudflare.com dns.cloudflare.`

📌 Glue Records Collected

Total: 12

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

Analysis

Name Servers

nanofancy.com has two name servers: yoxall.ns.cloudflare.com and ziggy.ns.cloudflare.com.

nanofancy.com shares the same name server setup as other domains, for example nobletap.com, huittistenelainlaakaripalvelu.fi, fussymail.com, animelosangeles.org and flapcode.com.

nanofancy.com shares some name servers with other domains, for example jerue.org, rr-google-cost.pages.dev, 136578.cn, larslaj.com.ua and kitsappropane.com.

These name servers are often used together with ignat.ns.cloudflare.com, brenda.ns.cloudflare.com and sandy.ns.cloudflare.com.

Host names with six IP numbers: yoxall.ns.cloudflare.com points to: 2606:4700:58::a29f:2c2f, 2803:f800:50::6ca2:c32f, 2a06:98c1:50::ac40:232f, 108.162.195.47, 162.159.44.47 and 172.64.35.47; ziggy.ns.cloudflare.com points to: 2606:4700:50::a29f:26ed, 2803:f800:50::6ca2:c2ed, 2a06:98c1:50::ac40:22ed, 108.162.194.237, 162.159.38.237 and 172.64.34.237.

Mail Servers

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

nanofancy.com shares some mail servers with other domains, at least partially; for instance it-f.jp, ktour.ro, over.so, ccnn.com and muverity.net.

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

nanofancy.com - robtex.com

nanofancy.com

com

Same first word

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

Name Servers

Mail Servers

`nanofancy.com`

`com`