`fjyp.cn`

DNSSEC	⚠️ Not signed
A	2606:4700:3033::6815:50c3^{🇺🇸 Cloudflare2606:4700:3033::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3036::ac43:994f^{🇺🇸 Cloudflare2606:4700:3036::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.80.195^{Cloudflare104.21.80.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.153.79^{🇺🇸 Cloudflare172.67.144.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`casey.ns.cloudflare.com` ⭐
		A	2606:4700:58::a29f:2c9e^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`casey.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c39e^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`casey.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:239e^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`casey.ns.cloudflare.com`
		A	108.162.195.158^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`casey.ns.cloudflare.com`
		A	162.159.44.158^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`casey.ns.cloudflare.com`
		A	172.64.35.158^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`casey.ns.cloudflare.com`
NS	`kim.ns.cloudflare.com`
		A	2606:4700:50::adf5:3a7e^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kim.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c07e^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`kim.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:207e^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`kim.ns.cloudflare.com`
		A	108.162.192.126^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kim.ns.cloudflare.com`
		A	172.64.32.126^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kim.ns.cloudflare.com`
		A	173.245.58.126^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kim.ns.cloudflare.com`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.80.195, 172.67.153.79
		IPv6 hints	2606:4700:3033::6815:50c3, 2606:4700:3036::ac43:994f
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=230, name=cloudflare-ech.com
SOA	`casey.ns.cloudflare.com`dns@cloudflare.com serial=2400662072

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

Same first word

fjyp.cn

Similar names

pjfy.com

pfyj.cn

pfyj.com

fpyj.com

jyfp.com

pyfj.cn

jpfy.cn

pjyf.com

jpyf.com.cn

fypj.com.cn

jfpy.cn

jfyp.com

jpfy.com

fpyj.cn

pfjy.cn

ypfj.com

ypfj.cn

yjpf.net

jypf.com

pyfj.com

jyfp.cn

jpyf.com

pyjf.cn

yjfp.cn

fpjy.cn

fyjp.com

ypjf.com

ypfj.com.cn

fypj.com

fypj.cn

pyfj.net

pfyj.com.cn

DNS History

22 records (6 active, 16 former)

●NScasey.ns.cloudflare.com2026-03-27 → 2026-04-12 · 3 obs

○ 2017-04-08 07:13:24
● 2026-03-27 10:38:10
● 2026-04-12 15:39:54

○NSdns1.iidns.com2015-08-16 → 2015-08-16 · 3 obs

● 2015-08-16 10:20:52
○ 2016-03-10 13:31:12
○ 2026-04-12 15:39:54

○NSdns2.iidns.com2015-08-16 → 2015-08-16 · 3 obs

● 2015-08-16 10:20:52
○ 2016-03-10 13:31:12
○ 2026-04-12 15:39:54

○NSdns3.iidns.com2015-08-16 → 2015-08-16 · 3 obs

● 2015-08-16 10:20:52
○ 2016-03-10 13:31:12
○ 2026-04-12 15:39:54

○NSdns4.iidns.com2015-08-16 → 2015-08-16 · 3 obs

● 2015-08-16 10:20:52
○ 2016-03-10 13:31:12
○ 2026-04-12 15:39:54

○NSdns5.iidns.com2015-08-16 → 2015-08-16 · 3 obs

● 2015-08-16 10:20:52
○ 2016-03-10 13:31:12
○ 2026-04-12 15:39:54

○NSdns6.iidns.com2015-08-16 → 2015-08-16 · 3 obs

● 2015-08-16 10:20:52
○ 2016-03-10 13:31:12
○ 2026-04-12 15:39:54

●NSkim.ns.cloudflare.com2026-03-27 → 2026-04-12 · 3 obs

○ 2017-04-08 07:13:24
● 2026-03-27 10:38:10
● 2026-04-12 15:39:54

○NSwww.fjyp.cn2016-03-10 → 2017-04-08 · 5 obs

○ 2015-08-16 10:20:52
● 2016-03-10 13:31:12
● 2017-04-08 07:13:24
○ 2026-03-27 10:38:10
○ 2026-04-12 15:39:54

○MXio.bouncemx.com2016-03-10 → 2017-04-08 · 4 obs

● 2016-03-10 13:31:12
● 2017-04-08 07:13:24
○ 2026-03-27 10:38:10
○ 2026-04-12 15:39:54

●A104.21.80.1952026-03-27 → 2026-04-12 · 3 obs

○ 2017-04-08 07:13:24
● 2026-03-27 10:38:10
● 2026-04-12 15:39:54

○A172.64.80.12026-03-27 → 2026-04-12 · 2 obs

○ 2026-03-27 10:38:10
○ 2026-04-12 15:39:54

●A172.67.153.792026-03-27 → 2026-04-12 · 3 obs

○ 2017-04-08 07:13:24
● 2026-03-27 10:38:10
● 2026-04-12 15:39:54

○A198.148.92.872015-08-16 → 2015-08-16 · 3 obs

● 2015-08-16 10:20:52
○ 2026-03-27 10:38:10
○ 2026-04-12 15:39:54

○A198.148.92.882015-08-16 → 2015-08-16 · 3 obs

● 2015-08-16 10:20:52
○ 2026-03-27 10:38:10
○ 2026-04-12 15:39:54

●A2606:4700:3033::6815:50c32026-03-27 → 2026-04-12 · 3 obs

○ 2017-04-08 07:13:24
● 2026-03-27 10:38:10
● 2026-04-12 15:39:54

●A2606:4700:3036::ac43:994f2026-03-27 → 2026-04-12 · 3 obs

○ 2017-04-08 07:13:24
● 2026-03-27 10:38:10
● 2026-04-12 15:39:54

○A59.188.9.432015-12-09 → 2015-12-09 · 4 obs

○ 2015-08-16 10:20:52
● 2015-12-09 05:24:52
○ 2016-03-10 13:31:12
○ 2026-04-12 15:39:54

○A70.39.84.2312016-03-10 → 2016-03-10 · 4 obs

○ 2015-12-09 05:24:52
● 2016-03-10 13:31:12
○ 2017-04-08 07:13:24
○ 2026-04-12 15:39:54

○A70.39.84.2332017-04-08 → 2017-04-08 · 4 obs

○ 2016-03-10 13:31:12
● 2017-04-08 07:13:24
○ 2026-03-27 10:38:10
○ 2026-04-12 15:39:54

○CNAMEcs.ename.net2015-08-16 → 2015-08-16 · 3 obs

● 2015-08-16 10:20:52
○ 2015-12-09 05:24:52
○ 2026-04-12 15:39:54

○CNAMEf.dcoin.co2016-03-10 → 2017-04-08 · 5 obs

○ 2015-12-09 05:24:52
● 2016-03-10 13:31:12
● 2017-04-08 07:13:24
○ 2026-03-27 10:38:10
○ 2026-04-12 15:39:54

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
cn	e.dns.cn, a.dns.cn, c.dns.cn, d.dns.cn...	-
fjyp.cn	kim.ns.cloudflare.com, casey.ns.cloudflare.com	-

✅ Authoritative Response

Server:108.162.195.158

NS records: kim.ns.cloudflare.com, casey.ns.cloudflare.com

🔒 DNSSEC Status

❌ Bogus (DNSSEC validation failed)

Validation error at cn: Error: DNS query timeout: 203.119.29.1 for DNSKEY cn

⏱️ Timing

Total: 3569ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.80.195, 172.67.153.79`
AAAA	2	`2606:4700:3033::6815:50c3, 2606:4700:3036::ac43:994f`
NS	2	`casey.ns.cloudflare.com, kim.ns.cloudflare.com`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`casey.ns.cloudflare.com dns.cloudflare.c`

Analysis

IP Addresses

fjyp.cn resolves to four IPs: 2606:4700:3033::6815:50c3, 2606:4700:3036::ac43:994f, 104.21.80.195 and 172.67.153.79.

Other host names such as velaclub.com, charityrising.com, dxmx.us, halquonethir.com and ourtrendmagazine.com share IP numbers with fjyp.cn.

Name Servers

fjyp.cn is delegated to two name servers: casey.ns.cloudflare.com and kim.ns.cloudflare.com.

fjyp.cn uses the same name server setup as other domains, including shuandashi.com, chakejie.com, yulanchun.cn, kkdgq.com and montie-safetycare.com.

At least part of the name servers for fjyp.cn are shared with other domains, for instance hoteldudomaine.com, l117n-sofort.de, rmapa.cn, maxenceserre.com and ivanaj.org.

These name servers are commonly used alongside leif.ns.cloudflare.com and walt.ns.cloudflare.com.

Host names with six IP numbers:

casey.ns.cloudflare.com points to: 2606:4700:58::a29f:2c9e, 2803:f800:50::6ca2:c39e, 2a06:98c1:50::ac40:239e, 108.162.195.158, 162.159.44.158 and 172.64.35.158.

kim.ns.cloudflare.com points to: 2606:4700:50::adf5:3a7e, 2803:f800:50::6ca2:c07e, 2a06:98c1:50::ac40:207e, 108.162.192.126, 172.64.32.126 and 173.245.58.126.

fjyp.cn - robtex.com

fjyp.cn

cn

Same first word

Similar names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

Analysis

IP Addresses

Name Servers

`fjyp.cn`

`cn`