002cf.com - dns.ninja

002cf.com

DNSSEC⚠️ Not signed
A103.112.187.195🇨🇳 RAINBOWIDC-AS-AP103.112.186.0/23 CMI (Customer Route)
PTRunknown.itsidc.com
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.onclouddns.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
NSns2.onclouddns.com ⚠️ Not in zone NS records
A162.159.27.251Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
SOAns1.julydns.commaster@jmdns.com serial=1781612891

com

DNSSEC🔒 Signed (DS record present)
NSa.gtld-servers.net ⭐
NSb.gtld-servers.net
NSc.gtld-servers.net
NSd.gtld-servers.net
NSe.gtld-servers.net
NSf.gtld-servers.net
NSg.gtld-servers.net
NSh.gtld-servers.net
NSi.gtld-servers.net
NSj.gtld-servers.net
NSk.gtld-servers.net
NSl.gtld-servers.net
NSm.gtld-servers.net
SOAa.gtld-servers.netnstld@verisign-grs.com serial=1782751986

Same first word

002cf.com

Similar names

cf002.com
cf200.com
020cf.com
cf002.vip
020fc.net
200fc.com
fc200.com
fc020.com
020fc.cn
020fc.com

DNS History

18 records (5 active, 13 former)

20162017201820192020202120222023202420252026NSns1.julydns.comns1.onclouddns.comns2.julydns.comns2.onclouddns.comdns10.hichina.comdns9.hichina.comns1.22.cnns1.judns.comns2.22.cnns2.judns.comA103.112.187.195103.242.111.124103.242.111.137103.242.111.150107.164.180.16118.193.245.94156.244.99.14645.125.35.221
○NSdns10.hichina.com2015-08-13 → 2017-02-18 · 4 obs
● 2015-08-13 18:01:24
● 2017-02-18 22:53:32
○ 2019-04-10 10:44:20
○ 2026-06-29 17:22:40
○NSdns9.hichina.com2015-08-13 → 2017-02-18 · 4 obs
● 2015-08-13 18:01:24
● 2017-02-18 22:53:32
○ 2019-04-10 10:44:20
○ 2026-06-29 17:22:40
○NSns1.22.cn2019-04-10 → 2019-04-10 · 4 obs
○ 2017-02-18 22:53:32
● 2019-04-10 10:44:20
○ 2026-03-09 16:42:14
○ 2026-06-29 17:22:40
○NSns1.judns.com2026-03-09 → 2026-05-07 · 4 obs
○ 2019-04-10 10:44:20
● 2026-03-09 16:42:14
● 2026-05-07 15:56:58
○ 2026-06-29 17:22:40
●NSns1.julydns.com2026-03-09 → 2026-06-29 · 3 obs
○ 2019-04-10 10:44:20
● 2026-03-09 16:42:14
● 2026-06-29 17:22:40
●NSns1.onclouddns.com2026-06-29 → 2026-06-29 · 2 obs
○ 2026-05-07 15:56:58
● 2026-06-29 17:22:40
○NSns2.22.cn2019-04-10 → 2019-04-10 · 4 obs
○ 2017-02-18 22:53:32
● 2019-04-10 10:44:20
○ 2026-03-09 16:42:14
○ 2026-06-29 17:22:40
○NSns2.judns.com2026-03-09 → 2026-05-07 · 4 obs
○ 2019-04-10 10:44:20
● 2026-03-09 16:42:14
● 2026-05-07 15:56:58
○ 2026-06-29 17:22:40
●NSns2.julydns.com2026-03-09 → 2026-06-29 · 3 obs
○ 2019-04-10 10:44:20
● 2026-03-09 16:42:14
● 2026-06-29 17:22:40
●NSns2.onclouddns.com2026-06-29 → 2026-06-29 · 2 obs
○ 2026-05-07 15:56:58
● 2026-06-29 17:22:40
●A103.112.187.1952026-06-29 → 2026-06-29 · 2 obs
○ 2026-05-07 15:56:58
● 2026-06-29 17:22:40
○A103.242.111.1242017-02-18 → 2017-02-18 · 4 obs
○ 2016-07-16 10:13:48
● 2017-02-18 22:53:32
○ 2019-04-10 10:44:20
○ 2026-06-29 17:22:40
○A103.242.111.1372017-02-18 → 2017-02-18 · 4 obs
○ 2016-07-16 10:13:48
● 2017-02-18 22:53:32
○ 2019-04-10 10:44:20
○ 2026-06-29 17:22:40
○A103.242.111.1502017-02-18 → 2017-02-18 · 4 obs
○ 2016-07-16 10:13:48
● 2017-02-18 22:53:32
○ 2019-04-10 10:44:20
○ 2026-06-29 17:22:40
○A107.164.180.162019-04-10 → 2019-04-10 · 4 obs
○ 2017-02-18 22:53:32
● 2019-04-10 10:44:20
○ 2026-03-09 16:42:14
○ 2026-06-29 17:22:40
○A118.193.245.942015-08-13 → 2015-08-13 · 3 obs
● 2015-08-13 18:01:24
○ 2015-12-05 02:16:22
○ 2026-06-29 17:22:40
○A156.244.99.1462026-03-09 → 2026-05-07 · 4 obs
○ 2019-04-10 10:44:20
● 2026-03-09 16:42:14
● 2026-05-07 15:56:58
○ 2026-06-29 17:22:40
○A45.125.35.2212015-12-05 → 2016-07-16 · 5 obs
○ 2015-08-13 18:01:24
● 2015-12-05 02:16:22
● 2016-07-16 10:13:48
○ 2017-02-18 22:53:32
○ 2026-06-29 17:22:40

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, m.gtld-servers.net, b.gtld-servers.net, e.gtld-servers.net...-
002cf.comns1.onclouddns.com, ns2.onclouddns.com2 records

✅ Authoritative Response

Server:162.159.27.251

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for 002cf.com (unsigned zone)

⏱️ Timing

Total: 216ms | Queries: -

📄 Records

TypeCountSample Data
A1103.112.187.195
NS2ns1.julydns.com, ns2.julydns.com
SOA1ns1.julydns.com master.jmdns.com

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.onclouddns.com, ns2.onclouddns.com)

Analysis

IP Addresses

002cf.com has exactly one IP address — 103.112.187.195.

Name Servers

Four name servers handle the delegation for 002cf.com: ns1.julydns.com, ns2.julydns.com, ns1.onclouddns.com and ns2.onclouddns.com.

The name servers of 002cf.com overlap at least partially with those of other domains — among them nenming.com, hezehq.cn, sj18.com.cn and two more.

These name servers commonly appear alongside the name servers ns1.judns.com and ns2.judns.com.

ns1.julydns.com and ns2.julydns.com share the IP address 162.159.48.223; ns1.onclouddns.com and ns2.onclouddns.com share the IP address 162.159.27.251.

Both ns1.julydns.com and ns2.julydns.com resolve to 162.159.48.223 IP addresses each.

Both ns1.onclouddns.com and ns2.onclouddns.com resolve to 162.159.27.251 IP addresses each.