`384sf.com`

DNSSEC	⚠️ Not signed
A	103.244.148.49^{🇭🇰 harry-ASN103.244.148.0/22 HONG KONG KOWLOON TELECOMMUNICATIONS CO.,LIMITED}
NS	`ns1.julydns.com` ⭐ ⚠️ Not in parent delegation
		A	47.97.51.45^{🇨🇳 Alibaba-Cloud47.96.0.0/15 Aliyun Computing Co., LTD}
			PTR	`ip-47-97-51-45.defastlink.net`
NS	`ns1.judns.com` ⚠️ Not in zone NS records
		A	47.97.51.45^{🇨🇳 Alibaba-Cloud47.96.0.0/15 Aliyun Computing Co., LTD}
			PTR	`ip-47-97-51-45.defastlink.net`
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}
			PTR	`ip-162-159-27-251.defastlink.net`
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}
			PTR	`ip-162-159-48-223.defastlink.net`
SOA	`ns1.julydns.com`master@jmdns.com serial=1774018776

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

Same first word

384sf.com

Similar names

483sf.com

sf348.com

DNS History

11 records (5 active, 6 former)

○NSf1g1ns1.dnspod.net2015-08-06 → 2016-03-21 · 4 obs

● 2015-08-06 20:37:00
● 2016-03-21 06:30:26
○ 2016-07-15 14:27:28
○ 2026-03-24 04:06:20

○NSf1g1ns2.dnspod.net2015-08-06 → 2016-03-21 · 4 obs

● 2015-08-06 20:37:00
● 2016-03-21 06:30:26
○ 2016-07-15 14:27:28
○ 2026-03-24 04:06:20

●NSns1.judns.com2026-03-21 → 2026-03-24 · 3 obs

○ 2017-03-28 04:30:24
● 2026-03-21 08:21:36
● 2026-03-24 04:06:20

●NSns1.julydns.com2026-03-21 → 2026-03-24 · 3 obs

○ 2017-03-28 04:30:24
● 2026-03-21 08:21:36
● 2026-03-24 04:06:20

○NSns1.maff.com2016-07-15 → 2017-03-28 · 5 obs

○ 2016-03-21 06:30:26
● 2016-07-15 14:27:28
● 2017-03-28 04:30:24
○ 2026-03-21 08:21:36
○ 2026-03-24 04:06:20

●NSns2.judns.com2026-03-21 → 2026-03-24 · 3 obs

○ 2017-03-28 04:30:24
● 2026-03-21 08:21:36
● 2026-03-24 04:06:20

●NSns2.julydns.com2026-03-21 → 2026-03-24 · 3 obs

○ 2017-03-28 04:30:24
● 2026-03-21 08:21:36
● 2026-03-24 04:06:20

○NSns2.maff.com2016-07-15 → 2016-07-15 · 4 obs

○ 2016-03-21 06:30:26
● 2016-07-15 14:27:28
○ 2017-03-28 04:30:24
○ 2026-03-24 04:06:20

●A103.244.148.492026-03-21 → 2026-03-24 · 3 obs

○ 2017-03-28 04:30:24
● 2026-03-21 08:21:36
● 2026-03-24 04:06:20

○A156.238.231.1382026-03-21 → 2026-03-24 · 2 obs

○ 2026-03-21 08:21:36
○ 2026-03-24 04:06:20

○A47.89.60.1042017-03-28 → 2017-03-28 · 3 obs

● 2017-03-28 04:30:24
○ 2026-03-21 08:21:36
○ 2026-03-24 04:06:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	m.gtld-servers.net, l.gtld-servers.net, k.gtld-servers.net, j.gtld-servers.net...	-
384sf.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 384sf.com (unsigned zone)

⏱️ Timing

Total: 401ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`103.244.148.49`
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

384sf.com points to IP number 103.244.148.49.

Other host names, for example 862sf.com and 028sf.com, share IPs with 384sf.com.

Name Servers

384sf.com is delegated to four name servers: ns1.judns.com, ns2.judns.com, ns1.julydns.com and ns2.julydns.com.

384sf.com shares name servers with other domains at least partially, for example c669c.com, xalipin.com, jdule.com, saiodq.com and khjjj.cn.