`cdlcf.com`

DNSSEC	⚠️ Not signed
A	156.235.204.106^{🇭🇰 DXTL-1156.235.204.0/24 Proxy-registered route object}
NS	`ns1.julydns.com` ⭐ ⚠️ Not in parent delegation
		A	162.159.48.223^{Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns1.judns.com` ⚠️ Not in zone NS records
		A	162.159.27.251^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns2.judns.com` ⚠️ Not in zone NS records
		A	162.159.27.251^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns2.julydns.com` ⚠️ Not in parent delegation
		A	162.159.48.223^{Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
SOA	`ns1.julydns.com`master@jmdns.com serial=1766917525

`com`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.gtld-servers.net` ⭐
	NS	`b.gtld-servers.net`
	NS	`c.gtld-servers.net`
	NS	`d.gtld-servers.net`
	NS	`e.gtld-servers.net`
	NS	`f.gtld-servers.net`
	NS	`g.gtld-servers.net`
	NS	`h.gtld-servers.net`
	NS	`i.gtld-servers.net`
	NS	`j.gtld-servers.net`
	NS	`k.gtld-servers.net`
	NS	`l.gtld-servers.net`
	NS	`m.gtld-servers.net`
	SOA	`a.gtld-servers.net`nstld@verisign-grs.com serial=1784094037

Same first word

cdlcf.com

Similar names

fccdl.in

flcdc.net

fccdl.co

dlcfc.com

ccfdl.cn

cfcdl.org

cfcdl.com.br

fccdl.us

clfcd.com

cfdlc.org

ccdfl.org

cdlfc.com

flcdc.com

clcfd.com

lfcdc.net

cfldc.com

fldcc.com

lcfdc.net

dflcc.cn

fcdcl.com

ldfcc.com

cdcfl.com

fccdl.com

ccfdl.com

dfclc.com

lfcdc.com

lfdcc.com

flcdc.org

DNS History

23 records (5 active, 18 former)

○NSdns1.iidns.com2016-04-04 → 2017-04-03 · 5 obs

○ 2015-10-19 19:15:00
● 2016-04-04 05:50:24
● 2017-04-03 18:06:48
○ 2026-04-27 12:22:54
○ 2026-07-15 05:58:04

○NSdns2.iidns.com2016-04-04 → 2016-04-04 · 4 obs

○ 2015-10-19 19:15:00
● 2016-04-04 05:50:24
○ 2017-04-03 18:06:48
○ 2026-07-15 05:58:04

○NSdns3.iidns.com2016-04-04 → 2016-04-04 · 4 obs

○ 2015-10-19 19:15:00
● 2016-04-04 05:50:24
○ 2017-04-03 18:06:48
○ 2026-07-15 05:58:04

○NSdns4.iidns.com2016-04-04 → 2016-04-04 · 4 obs

○ 2015-10-19 19:15:00
● 2016-04-04 05:50:24
○ 2017-04-03 18:06:48
○ 2026-07-15 05:58:04

○NSdns5.iidns.com2016-04-04 → 2016-04-04 · 4 obs

○ 2015-10-19 19:15:00
● 2016-04-04 05:50:24
○ 2017-04-03 18:06:48
○ 2026-07-15 05:58:04

○NSdns6.iidns.com2016-04-04 → 2016-04-04 · 4 obs

○ 2015-10-19 19:15:00
● 2016-04-04 05:50:24
○ 2017-04-03 18:06:48
○ 2026-07-15 05:58:04

○NSns1.51dns.com2015-05-22 → 2015-05-22 · 3 obs

● 2015-05-22 00:46:12
○ 2015-10-19 19:15:00
○ 2026-07-15 05:58:04

●NSns1.judns.com2026-04-27 → 2026-07-15 · 3 obs

○ 2017-04-03 18:06:48
● 2026-04-27 12:22:54
● 2026-07-15 05:58:04

●NSns1.julydns.com2026-04-27 → 2026-07-15 · 3 obs

○ 2017-04-03 18:06:48
● 2026-04-27 12:22:54
● 2026-07-15 05:58:04

○NSns2.51dns.com2015-05-22 → 2015-05-22 · 3 obs

● 2015-05-22 00:46:12
○ 2016-04-04 05:50:24
○ 2026-07-15 05:58:04

●NSns2.judns.com2026-04-27 → 2026-07-15 · 3 obs

○ 2017-04-03 18:06:48
● 2026-04-27 12:22:54
● 2026-07-15 05:58:04

●NSns2.julydns.com2026-04-27 → 2026-07-15 · 3 obs

○ 2017-04-03 18:06:48
● 2026-04-27 12:22:54
● 2026-07-15 05:58:04

○A103.241.230.1352017-04-03 → 2017-04-03 · 4 obs

○ 2016-04-04 05:50:24
● 2017-04-03 18:06:48
○ 2026-04-27 12:22:54
○ 2026-07-15 05:58:04

○A103.241.230.1372017-04-03 → 2017-04-03 · 4 obs

○ 2016-04-04 05:50:24
● 2017-04-03 18:06:48
○ 2026-04-27 12:22:54
○ 2026-07-15 05:58:04

○A103.241.230.1382017-04-03 → 2017-04-03 · 4 obs

○ 2016-04-04 05:50:24
● 2017-04-03 18:06:48
○ 2026-04-27 12:22:54
○ 2026-07-15 05:58:04

○A103.241.230.1402017-04-03 → 2017-04-03 · 4 obs

○ 2016-04-04 05:50:24
● 2017-04-03 18:06:48
○ 2026-04-27 12:22:54
○ 2026-07-15 05:58:04

○A104.216.22.1082015-05-22 → 2015-05-22 · 3 obs

● 2015-05-22 00:46:12
○ 2015-10-19 19:15:00
○ 2026-07-15 05:58:04

○A107.167.19.802015-10-19 → 2015-10-19 · 4 obs

○ 2015-05-22 00:46:12
● 2015-10-19 19:15:00
○ 2015-12-25 02:58:16
○ 2026-07-15 05:58:04

○A107.167.19.812015-10-19 → 2015-10-19 · 4 obs

○ 2015-05-22 00:46:12
● 2015-10-19 19:15:00
○ 2015-12-25 02:58:16
○ 2026-07-15 05:58:04

●A156.235.204.1062026-04-27 → 2026-07-15 · 3 obs

○ 2017-04-03 18:06:48
● 2026-04-27 12:22:54
● 2026-07-15 05:58:04

○A59.188.71.2182015-12-25 → 2015-12-25 · 4 obs

○ 2015-10-19 19:15:00
● 2015-12-25 02:58:16
○ 2016-04-04 05:50:24
○ 2026-07-15 05:58:04

○CNAMEcs.ename.net2017-04-03 → 2017-04-03 · 4 obs

○ 2015-12-25 02:58:16
● 2017-04-03 18:06:48
○ 2026-04-27 12:22:54
○ 2026-07-15 05:58:04

○CNAMEpending-delete.ename.net2015-10-19 → 2015-10-19 · 3 obs

● 2015-10-19 19:15:00
○ 2015-12-25 02:58:16
○ 2026-07-15 05:58:04

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
cdlcf.com	ns1.judns.com, ns2.judns.com	2 records

✅ Authoritative Response

Server:162.159.27.251

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for cdlcf.com (unsigned zone)

⏱️ Timing

Total: 315ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`156.235.204.106`
NS	2	`ns1.julydns.com, ns2.julydns.com`
SOA	1	`ns1.julydns.com master.jmdns.com`

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

cdlcf.com points to a single IP number: 156.235.204.106.

Name Servers

cdlcf.com has four authoritative name servers: ns1.judns.com, ns2.judns.com, ns1.julydns.com and ns2.julydns.com.

cdlcf.com has at least partial name server overlap with other domains, such as quanzhizhe.com, ureur.cn, nangmang.com and two others.

It is common to see these name servers used together with name servers ns1.onclouddns.com and ns2.onclouddns.com.

ns1.judns.com and ns2.judns.com each resolve to 162.159.27.251, while ns1.julydns.com and ns2.julydns.com each resolve to 162.159.48.223.

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

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

cdlcf.com - robtex.com

cdlcf.com

com

Same first word

Similar names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

IP Addresses

Name Servers

`cdlcf.com`

`com`