`idiry.cn`

DNSSEC	⚠️ Not signed
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`
NS	`titan.ns.cloudflare.com`
		A	2606:4700:58::a29f:2c5d^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`titan.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c35d^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`titan.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:235d^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`titan.ns.cloudflare.com`
		A	108.162.195.93^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`titan.ns.cloudflare.com`
		A	162.159.44.93^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`titan.ns.cloudflare.com`
		A	172.64.35.93^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`titan.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	`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`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
SOA	`pam.ns.cloudflare.com`dns@cloudflare.com serial=2397244099

`cn`

	DNSSEC	⚠️ Not signed
	NS	`a.dns.cn` ⭐
	NS	`b.dns.cn`
	NS	`c.dns.cn`
	NS	`d.dns.cn`
	NS	`e.dns.cn`
	NS	`ns.cernet.net` ⚠️ Not in parent delegation
	SOA	`a.dns.cn`root@cnnic.cn serial=2034546407

Same first word

idiry.cn

Similar names

diyir.com

DNS History

5 records (5 active, 0 former)

●NSpam.ns.cloudflare.com2026-02-25 → 2026-03-22 · 2 obs

● 2026-02-25 05:35:32
● 2026-03-22 23:15:48

●NStitan.ns.cloudflare.com2026-02-25 → 2026-03-22 · 2 obs

● 2026-02-25 05:35:32
● 2026-03-22 23:15:48

●MXroute1.mx.cloudflare.net2026-02-25 → 2026-03-22 · 2 obs

● 2026-02-25 05:35:32
● 2026-03-22 23:15:48

●MXroute2.mx.cloudflare.net2026-02-25 → 2026-03-22 · 2 obs

● 2026-02-25 05:35:32
● 2026-03-22 23:15:48

●MXroute3.mx.cloudflare.net2026-02-25 → 2026-03-22 · 2 obs

● 2026-02-25 05:35:32
● 2026-03-22 23:15:48

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
cn	e.dns.cn, a.dns.cn, c.dns.cn, d.dns.cn...	-
idiry.cn	pam.ns.cloudflare.com, titan.ns.cloudflare.com	-

✅ Authoritative Response

Server:172.64.32.138

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for idiry.cn (unsigned zone)

⏱️ Timing

Total: 983ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`pam.ns.cloudflare.com, titan.ns.cloudflare.com`
MX	3	`route3.mx.cloudflare.net (pri: 39), route2.mx.cloudflare.net (pri: 87)...`
TXT	1	`v=spf1 include:_spf.mx.cloudflare.net ~a`
SOA	1	`pam.ns.cloudflare.com dns.cloudflare.com`

Analysis

Name Servers

idiry.cn's delegation uses two name servers: pam.ns.cloudflare.com and titan.ns.cloudflare.com.

idiry.cn uses the same name server setup as other domains, such as abinitioen.com, 00000.press, arachnicom.com, soslab.com and parforum.com.

idiry.cn at least partially shares name servers with other domains, including trumtool.net, swaprenova-app.com, www.redriverskiarea.com, kfzumfrage.com and paulmcraeod.com.

These name servers are often used with eric.ns.cloudflare.com and vasilii.ns.cloudflare.com.

Host names with six IP numbers:

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.

titan.ns.cloudflare.com points to 2606:4700:58::a29f:2c5d, 2803:f800:50::6ca2:c35d, 2a06:98c1:50::ac40:235d, 108.162.195.93, 162.159.44.93 and 172.64.35.93.

Mail Servers

Three mail servers handle idiry.cn: route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

idiry.cn shares at least some mail servers with other domains, for example acbusca.com, findyfpay.com, maigelai.com, metrotransport.com.au and blogthea.gr.

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

idiry.cn - robtex.com

idiry.cn

cn

Same first word

Similar names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

Analysis

Name Servers

Mail Servers

`idiry.cn`

`cn`