fsang.cn - robtex.com

fsang.cn

DNSSEC⚠️ Not signed
A38.14.218.173πŸ‡ΊπŸ‡Έ AS40061938.14.216.0/21 arosscloud
NSns1.julydns.com ⭐ ⚠️ Not in parent delegation
A162.159.48.223Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US
NSns1.judns.com ⚠️ Not in zone NS records
A162.159.27.251Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
NSns2.judns.com ⚠️ Not in zone NS records
A162.159.27.251Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
NSns2.julydns.com ⚠️ Not in parent delegation
A162.159.48.223Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US
SOAns1.julydns.commaster@jmdns.com serial=1756969258

cn

DNSSEC⚠️ Not signed
NSa.dns.cn ⭐
NSb.dns.cn
NSc.dns.cn
NSd.dns.cn
NSe.dns.cn
NSns.cernet.net ⚠️ Not in parent delegation
SOAa.dns.cnroot@cnnic.cn serial=2035048671

Same first word

Similar names

DNS History

9 records (5 active, 4 former)

2017201820192020202120222023202420252026NSns1.judns.comns1.julydns.comns2.judns.comns2.julydns.comf1g1ns1.dnspod.netf1g1ns2.dnspod.netA38.14.218.173104.217.114.178168.235.255.218
β—‹NSf1g1ns1.dnspod.net2016-04-22 β†’ 2017-10-02 Β· 4 obs
● 2016-04-22 00:02:58
● 2017-10-02 19:40:00
β—‹ 2026-06-17 18:13:38
β—‹ 2026-07-16 23:36:50
β—‹NSf1g1ns2.dnspod.net2016-04-22 β†’ 2017-10-02 Β· 4 obs
● 2016-04-22 00:02:58
● 2017-10-02 19:40:00
β—‹ 2026-06-17 18:13:38
β—‹ 2026-07-16 23:36:50
●NSns1.judns.com2026-06-17 β†’ 2026-07-16 Β· 3 obs
β—‹ 2017-10-02 19:40:00
● 2026-06-17 18:13:38
● 2026-07-16 23:36:50
●NSns1.julydns.com2026-06-17 β†’ 2026-07-16 Β· 3 obs
β—‹ 2017-10-02 19:40:00
● 2026-06-17 18:13:38
● 2026-07-16 23:36:50
●NSns2.judns.com2026-06-17 β†’ 2026-07-16 Β· 3 obs
β—‹ 2017-10-02 19:40:00
● 2026-06-17 18:13:38
● 2026-07-16 23:36:50
●NSns2.julydns.com2026-06-17 β†’ 2026-07-16 Β· 3 obs
β—‹ 2017-10-02 19:40:00
● 2026-06-17 18:13:38
● 2026-07-16 23:36:50
β—‹A104.217.114.1782016-04-22 β†’ 2016-04-22 Β· 3 obs
● 2016-04-22 00:02:58
β—‹ 2017-10-02 19:40:00
β—‹ 2026-07-16 23:36:50
β—‹A168.235.255.2182017-10-02 β†’ 2017-10-02 Β· 4 obs
β—‹ 2016-04-22 00:02:58
● 2017-10-02 19:40:00
β—‹ 2026-06-17 18:13:38
β—‹ 2026-07-16 23:36:50
●A38.14.218.1732026-06-17 β†’ 2026-07-16 Β· 3 obs
β—‹ 2017-10-02 19:40:00
● 2026-06-17 18:13:38
● 2026-07-16 23:36:50

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
cne.dns.cn, a.dns.cn, b.dns.cn, c.dns.cn...-
fsang.cnns1.judns.com, ns2.judns.com-

βœ… Authoritative Response

Server:162.159.27.251

NS records: ns1.judns.com, ns2.judns.com

πŸ”’ DNSSEC Status

❌ Bogus (DNSSEC validation failed)

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

⏱️ Timing

Total: 3448ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A138.14.218.173
NS2ns1.julydns.com, ns2.julydns.com
SOA1ns1.julydns.com master.jmdns.com

Analysis

IP Addresses

fsang.cn resolves to just one IP address, 38.14.218.173.

Name Servers

The NS records for fsang.cn point to four name servers: ns1.judns.com, ns2.judns.com, ns1.julydns.com and ns2.julydns.com.

There is at least partial name server overlap between fsang.cn and other domains β€” rsgtzdb.com, scwmcc.com, hbjfu9.cn and two more among them.

These name servers frequently co-occur with the name servers ns1.onclouddns.com and ns2.onclouddns.com.

ns1.judns.com resolves to 162.159.27.251, as does ns2.judns.com. ns1.julydns.com resolves to 162.159.48.223, as does ns2.julydns.com.

ns1.judns.com and ns2.judns.com are host names that each point to 162.159.27.251 IP addresses.

ns1.julydns.com and ns2.julydns.com are host names that each point to 162.159.48.223 IP addresses.