cloudsecure.top - dns.ninja

`cloudsecure.top`

DNSSEC	⚠️ Not signed
A	154.89.152.167^{🇭🇰 ABCCLOUDSDNBHD-AS-AP154.89.152.0/24}
NS	`ns1.dnsowl.com` ⭐
		A	2400:cb00:2049:1::a29f:1a88^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	2400:cb00:2049:1::a29f:1bad^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.26.136^{Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	162.159.27.173^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns2.dnsowl.com`
		A	2400:cb00:2049:1::a29f:1a31^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	2400:cb00:2049:1::a29f:1b82^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.26.49^{Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	162.159.27.130^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns3.dnsowl.com`
		A	2400:cb00:2049:1::a29f:1aea^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	2400:cb00:2049:1::a29f:1b62^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.26.234^{Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	162.159.27.98^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns4.md5host.com` ⚠️ Not in zone NS records
NS	`ns5.md5host.com` ⚠️ Not in zone NS records
SOA	`ns1.dnsowl.com`hostmaster@dnsowl.com serial=1782296810

`top`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.zdnscloud.com` ⭐
	NS	`a.zdnscloud.cn`
	NS	`b.zdnscloud.cn`
	NS	`c.zdnscloud.com`
	NS	`d.zdnscloud.com`
	NS	`e.zdnscloud.cn`
	NS	`f.zdnscloud.cn`
	NS	`i.zdnscloud.cn`
	NS	`j.zdnscloud.com`
	TXT	`2026-06-24_18:25:02`
	SOA	`a.zdnscloud.com`td_dns_gtld@knet.cn serial=1396233289

⚠️ On DNS blocklist: tif

Same first word

Similar names

DNS History

14 records (6 active, 8 former)

○NSbecky.ns.cloudflare.com2017-03-16 → 2017-03-16 · 3 obs

● 2017-03-16 18:03:12
○ 2018-11-30 09:05:08
○ 2026-06-24 10:30:52

○NSmatt.ns.cloudflare.com2017-03-16 → 2017-03-16 · 3 obs

● 2017-03-16 18:03:12
○ 2018-11-30 09:05:08
○ 2026-06-24 10:30:52

●NSns1.dnsowl.com2026-04-15 → 2026-06-24 · 3 obs

○ 2018-11-30 09:05:08
● 2026-04-15 15:49:26
● 2026-06-24 10:30:52

●NSns2.dnsowl.com2026-04-15 → 2026-06-24 · 3 obs

○ 2018-11-30 09:05:08
● 2026-04-15 15:49:26
● 2026-06-24 10:30:52

●NSns3.dnsowl.com2026-04-15 → 2026-06-24 · 3 obs

○ 2018-11-30 09:05:08
● 2026-04-15 15:49:26
● 2026-06-24 10:30:52

●NSns4.md5host.com2026-04-15 → 2026-06-24 · 3 obs

○ 2018-11-30 09:05:08
● 2026-04-15 15:49:26
● 2026-06-24 10:30:52

●NSns5.md5host.com2026-04-15 → 2026-06-24 · 3 obs

○ 2018-11-30 09:05:08
● 2026-04-15 15:49:26
● 2026-06-24 10:30:52

○MXmailforward1.cloudns.net2017-03-16 → 2017-03-16 · 3 obs

● 2017-03-16 18:03:12
○ 2018-11-30 09:05:08
○ 2026-06-24 10:30:52

○MXmailforward2.cloudns.net2017-03-16 → 2017-03-16 · 3 obs

● 2017-03-16 18:03:12
○ 2018-11-30 09:05:08
○ 2026-06-24 10:30:52

○A104.24.100.1352017-03-16 → 2017-03-16 · 3 obs

● 2017-03-16 18:03:12
○ 2018-11-30 09:05:08
○ 2026-06-24 10:30:52

○A104.24.101.1352017-03-16 → 2017-03-16 · 3 obs

● 2017-03-16 18:03:12
○ 2018-11-30 09:05:08
○ 2026-06-24 10:30:52

●A154.89.152.1672026-04-15 → 2026-06-24 · 3 obs

○ 2018-11-30 09:05:08
● 2026-04-15 15:49:26
● 2026-06-24 10:30:52

○A2400:cb00:2048:1::6818:64872017-03-16 → 2017-03-16 · 3 obs

● 2017-03-16 18:03:12
○ 2018-11-30 09:05:08
○ 2026-06-24 10:30:52

○A2400:cb00:2048:1::6818:65872017-03-16 → 2017-03-16 · 3 obs

● 2017-03-16 18:03:12
○ 2018-11-30 09:05:08
○ 2026-06-24 10:30:52

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
top	a.zdnscloud.cn, b.zdnscloud.cn, c.zdnscloud.com, d.zdnscloud.com...	9 records
cloudsecure.top	ns1.dnsowl.com, ns2.dnsowl.com, ns3.dnsowl.com, ns4.md5host.com...	-

✅ Authoritative Response

Server:162.159.27.173

NS records: ns1.dnsowl.com, ns2.dnsowl.com, ns3.dnsowl.com, ns4.md5host.com, ns5.md5host.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for cloudsecure.top (unsigned zone)

⏱️ Timing

Total: 404ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`154.89.152.167`
NS	3	`ns1.dnsowl.com, ns2.dnsowl.com...`
SOA	1	`ns1.dnsowl.com hostmaster.dnsowl.com`

📌 Glue Records Collected

Total: 9

Out-of-bailiwick: 9 (a.zdnscloud.cn, b.zdnscloud.cn, c.zdnscloud.com...)

Analysis

IP Addresses

cloudsecure.top has exactly one IP address — 154.89.152.167.

Name Servers

Five name servers handle delegation for cloudsecure.top: ns1.dnsowl.com, ns2.dnsowl.com, ns3.dnsowl.com and two others.

cloudsecure.top shares at least some of its name servers with other domains, including safe-google.click, agency.coach, tomorrowtracks.com and two others.

These name servers are frequently paired with the name servers ns4.md5host.com and ns5.md5host.com.

Each of the hosts ns1.dnsowl.com, ns2.dnsowl.com and ns3.dnsowl.com resolves to four IP addresses: ns1.dnsowl.com points to 162.159.26.136, 162.159.27.173, 2400:cb00:2049:1::a29f:1a88 and 2400:cb00:2049:1::a29f:1bad; ns2.dnsowl.com points to 162.159.26.49, 162.159.27.130, 2400:cb00:2049:1::a29f:1a31 and 2400:cb00:2049:1::a29f:1b82; and ns3.dnsowl.com points to 162.159.26.234, 162.159.27.98, 2400:cb00:2049:1::a29f:1aea and 2400:cb00:2049:1::a29f:1b62.