yipd.cn - dns.ninja

`yipd.cn`

DNSSEC	⚠️ Not signed
A	2606:4700:3031::6815:46c5^{🇺🇸 Cloudflare2606:4700:3031::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3037::ac43:8aed^{🇺🇸 Cloudflare2606:4700:3037::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.70.197^{Cloudflare104.21.64.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.138.237^{🇺🇸 Cloudflare172.67.128.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`chip.ns.cloudflare.com` ⭐
		A	2606:4700:58::adf5:3b54^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chip.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c154^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`chip.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2154^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`chip.ns.cloudflare.com`
		A	108.162.193.84^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chip.ns.cloudflare.com`
		A	172.64.33.84^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chip.ns.cloudflare.com`
		A	173.245.59.84^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chip.ns.cloudflare.com`
NS	`nelly.ns.cloudflare.com`
		A	2606:4700:50::adf5:3ad1^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`nelly.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c0d1^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`nelly.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:20d1^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`nelly.ns.cloudflare.com`
		A	108.162.192.209^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`nelly.ns.cloudflare.com`
		A	172.64.32.209^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`nelly.ns.cloudflare.com`
		A	173.245.58.209^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`nelly.ns.cloudflare.com`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.70.197, 172.67.138.237
		IPv6 hints	2606:4700:3031::6815:46c5, 2606:4700:3037::ac43:8aed
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=148, name=cloudflare-ech.com
SOA	`chip.ns.cloudflare.com`dns@cloudflare.com serial=2406207844

`cn`

	DNSSEC	🔒 Signed (DS record present)
	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=2035158299

Same first word

yipd.com.cn

yipd.or.id

yipd.cn

yipd.com

Similar names

pidy.com

diyp.jp

ypid.net

dipy.fi

pydi.org

dipy.pl

ipyd.org

ypid.com

diyp.org

dipy.digital

dipy.net

ypdi.com.cn

yidp.com

dipy.de

pydi.de

pdiy.cn

dpiy.com

piyd.net

ipdy.shop

piyd.com

ipdy.net

iypd.org

diyp.at

ypid.org

idpy.org

pidy.be

ipyd.net

pidy.it

pidy.co.uk

pidy.se

ypdi.com

dipy.be

dyip.tk

dipy.cl

ypid.or.id

dyip.com.ph

diyp.net

pidy.shop

ipdy.com

ydpi.com

idyp.org

dipy.com

pidy.net

diyp.com

dypi.com.mx

ydpi.cn

iydp.com

dyip.cn

ipyd.gr

dipy.org

iypd.com

yidp.cn

dyip.ca

pidy.eu

dpyi.com

dypi.com

dpiy.co.jp

dyip.shop

pdiy.net

pdiy.com

ydip.com

pyid.com

ypid.de

dyip.com

dyip.de

pidy.de

yidp.org

pdyi.com

dypi.cn

dipy.ru

idpy.com

DNS History

18 records (6 active, 12 former)

●NSchip.ns.cloudflare.com2026-03-16 → 2026-08-09 · 3 obs

○ 2017-06-26 04:25:56
● 2026-03-16 01:16:06
● 2026-08-09 06:16:10

○NSdns1.iidns.com2016-04-27 → 2017-06-26 · 5 obs

○ 2015-08-13 20:06:46
● 2016-04-27 03:29:52
● 2017-06-26 04:25:56
○ 2026-03-16 01:16:06
○ 2026-08-09 06:16:10

○NSdns10.hichina.com2015-08-13 → 2015-08-13 · 3 obs

● 2015-08-13 20:06:46
○ 2016-04-27 03:29:52
○ 2026-08-09 06:16:10

○NSdns2.iidns.com2016-04-27 → 2016-12-04 · 5 obs

○ 2015-08-13 20:06:46
● 2016-04-27 03:29:52
● 2016-12-04 13:35:10
○ 2017-06-26 04:25:56
○ 2026-08-09 06:16:10

○NSdns3.iidns.com2016-04-27 → 2016-12-04 · 5 obs

○ 2015-08-13 20:06:46
● 2016-04-27 03:29:52
● 2016-12-04 13:35:10
○ 2017-06-26 04:25:56
○ 2026-08-09 06:16:10

○NSdns4.iidns.com2016-04-27 → 2016-12-04 · 5 obs

○ 2015-08-13 20:06:46
● 2016-04-27 03:29:52
● 2016-12-04 13:35:10
○ 2017-06-26 04:25:56
○ 2026-08-09 06:16:10

○NSdns5.iidns.com2016-04-27 → 2016-12-04 · 5 obs

○ 2015-08-13 20:06:46
● 2016-04-27 03:29:52
● 2016-12-04 13:35:10
○ 2017-06-26 04:25:56
○ 2026-08-09 06:16:10

○NSdns6.iidns.com2016-04-27 → 2016-12-04 · 5 obs

○ 2015-08-13 20:06:46
● 2016-04-27 03:29:52
● 2016-12-04 13:35:10
○ 2017-06-26 04:25:56
○ 2026-08-09 06:16:10

○NSdns9.hichina.com2015-08-13 → 2015-08-13 · 3 obs

● 2015-08-13 20:06:46
○ 2016-04-27 03:29:52
○ 2026-08-09 06:16:10

●NSnelly.ns.cloudflare.com2026-03-16 → 2026-08-09 · 3 obs

○ 2017-06-26 04:25:56
● 2026-03-16 01:16:06
● 2026-08-09 06:16:10

●A104.21.70.1972026-03-16 → 2026-08-09 · 3 obs

○ 2016-04-27 03:29:52
● 2026-03-16 01:16:06
● 2026-08-09 06:16:10

○A107.167.19.742016-04-27 → 2016-04-27 · 3 obs

● 2016-04-27 03:29:52
○ 2026-03-16 01:16:06
○ 2026-08-09 06:16:10

○A107.167.19.752016-04-27 → 2016-04-27 · 3 obs

● 2016-04-27 03:29:52
○ 2026-03-16 01:16:06
○ 2026-08-09 06:16:10

●A172.67.138.2372026-03-16 → 2026-08-09 · 3 obs

○ 2016-04-27 03:29:52
● 2026-03-16 01:16:06
● 2026-08-09 06:16:10

●A2606:4700:3031::6815:46c52026-07-08 → 2026-08-09 · 3 obs

○ 2026-06-11 00:20:08
● 2026-07-08 11:18:32
● 2026-08-09 06:16:10

○A2606:4700:3034::6815:46c52026-03-16 → 2026-06-11 · 5 obs

○ 2016-04-27 03:29:52
● 2026-03-16 01:16:06
● 2026-06-11 00:20:08
○ 2026-07-08 11:18:32
○ 2026-08-09 06:16:10

●A2606:4700:3037::ac43:8aed2026-03-16 → 2026-08-09 · 3 obs

○ 2016-04-27 03:29:52
● 2026-03-16 01:16:06
● 2026-08-09 06:16:10

○CNAMEcs.ename.net2016-04-27 → 2017-06-26 · 5 obs

● 2016-04-27 03:29:52
○ 2016-12-04 13:35:10
● 2017-06-26 04:25:56
○ 2026-03-16 01:16:06
○ 2026-08-09 06:16:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
cn	a.dns.cn, b.dns.cn, c.dns.cn, d.dns.cn...	-

✅ Authoritative Response

Server:203.119.25.1

NS records: a.dns.cn, b.dns.cn, c.dns.cn, d.dns.cn, e.dns.cn

🔒 DNSSEC Status

🔐 Secure (DNSSEC validated)

Chain of trust verified from root to domain

⏱️ Timing

Total: 844ms | Queries: -

📄 Records

Type	Count	Sample Data

Analysis

IP Addresses

yipd.cn resolves to four IP addresses: 104.21.70.197, 172.67.138.237, 2606:4700:3031::6815:46c5 and 2606:4700:3037::ac43:8aed.

Two other host names, along with backintheusa.us, www.salemco.org and www.id.advocadoapp.com, also share IP numbers with yipd.cn.

Name Servers

yipd.cn is served by two delegated name servers, chip.ns.cloudflare.com and nelly.ns.cloudflare.com.

yipd.cn shares its NS records with other domains, for example nbroom.cn, zhupifa.com, leadmantra.com and two others.

yipd.cn has at least partial name server overlap with other domains, such as mediazone.online, for4dgaya.live, kokitototaken.com and two others.

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

DNS names with 6 IP addresses:

chip.ns.cloudflare.com carries IP addresses 108.162.193.84, 172.64.33.84 and 173.245.59.84, with 3 other addresses beyond those.

nelly.ns.cloudflare.com carries IP addresses 108.162.192.209, 172.64.32.209 and 173.245.58.209, with 3 other addresses beyond those.