🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`clockcyclecloud.com`

DNSSEC	⚠️ Not signed
A	173.44.133.121^{🇺🇸 EONIX-NA173.44.132.0/22}
NS	`ns1.kouming.net` ⭐ ⚠️ Not in zone NS records
		A	2400:ede0:8000:1::5^{🇭🇰 HKKF-12400:ede0::/32 client's prefix}
		A	2610:150:c011:5::422^{🇺🇸 SHARKTECH-12610:150:c000::/34 Sharktech Inc.}
		A	45.58.166.210^{🇺🇸 SHARKTECH-145.58.166.0/24}
			PTR	`customer.sharktech.net`
		A	103.97.0.249^{🇭🇰 SZKF-AS-AP103.97.0.0/24 HKKF}
NS	`ns1.kouming.com` ⚠️ Not in parent delegation
		A	2610:150:c011:5::330^{🇺🇸 SHARKTECH-12610:150:c000::/34 Sharktech Inc.}
		A	170.178.174.195^{🇺🇸 SHARKTECH-1170.178.174.0/24 CMI (Customer Route)}
			PTR	`rdns3.pepsii.com.br`
NS	`ns2.kouming.com` ⚠️ Not in parent delegation
		A	2610:150:c011:5::330^{🇺🇸 SHARKTECH-12610:150:c000::/34 Sharktech Inc.}
		A	170.178.174.195^{🇺🇸 SHARKTECH-1170.178.174.0/24 CMI (Customer Route)}
			PTR	`rdns3.pepsii.com.br`
NS	`ns2.kouming.net` ⚠️ Not in zone NS records
		A	2400:ede0:8000:1::5^{🇭🇰 HKKF-12400:ede0::/32 client's prefix}
		A	47.85.40.90^{🇺🇸 Alibaba-Cloud47.85.0.0/17 Proxy-registered route object}
SOA	`ns1.kouming.net`root@kouming.net serial=1793815627

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

Same first word

clockcyclecloud.com

Previous names

Next names

DNS History

5 records (5 active, 0 former)

●NSns1.kouming.com2026-11-08 → 2026-11-09 · 3 obs

○ 2026-04-04 11:22:22
● 2026-11-08 09:32:42
● 2026-11-09 14:34:42

●NSns1.kouming.net2026-04-04 → 2026-11-09 · 2 obs

● 2026-04-04 11:22:22
● 2026-11-09 14:34:42

●NSns2.kouming.com2026-11-08 → 2026-11-09 · 3 obs

○ 2026-04-04 11:22:22
● 2026-11-08 09:32:42
● 2026-11-09 14:34:42

●NSns2.kouming.net2026-04-04 → 2026-11-09 · 2 obs

● 2026-04-04 11:22:22
● 2026-11-09 14:34:42

●A173.44.133.1212026-11-08 → 2026-11-09 · 2 obs

● 2026-11-08 09:32:42
● 2026-11-09 14:34:42

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
clockcyclecloud.com	ns1.kouming.net, ns2.kouming.net	-

✅ Authoritative Response

Server:47.85.40.90

NS records: ns1.kouming.net, ns2.kouming.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

Root DNSKEY fetch failed: Error: connect EADDRNOTAVAIL 198.41.0.4:53 - Local (0.0.0.0:0)

⏱️ Timing

Total: 573ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`173.44.133.121`
NS	2	`ns1.kouming.com, ns2.kouming.com`
SOA	1	`ns1.kouming.net root.kouming.net`

Analysis

IP Addresses

clockcyclecloud.com resolves to one IP address: 173.44.133.121.

datahivenetwork.com, for instance, is one of the other host names sharing IP numbers with clockcyclecloud.com.

Name Servers

The authoritative name servers for clockcyclecloud.com are ns1.kouming.com, ns2.kouming.com, ns1.kouming.net and ns2.kouming.net.

The name servers of clockcyclecloud.com overlap at least partially with those of other domains — among them xxsoso.com, qiaoyanchao.com, dlhyw.com and two more.

These name servers commonly appear alongside the name servers ns1.sgaddress.net and ns2.sgaddress.net.

Hosts that point to four IP numbers:

ns1.kouming.net resolves to 45.58.166.210, 103.97.0.249, 2400:ede0:8000:1::5 and 2610:150:c011:5::422.

Hostnames that resolve to two IP addresses:

ns1.kouming.com directs traffic to 170.178.174.195 and 2610:150:c011:5::330.

ns2.kouming.com directs traffic to 170.178.174.195 and 2610:150:c011:5::330.

ns2.kouming.net directs traffic to 47.85.40.90 and 2400:ede0:8000:1::5.

Both ns1.kouming.net and ns2.kouming.net resolve to 2400:ede0:8000:1::5 IP addresses each.

Both ns1.kouming.com and ns2.kouming.com resolve to 2610:150:c011:5::330 IP addresses each.

Both ns1.kouming.com and ns2.kouming.com resolve to 170.178.174.195 IP addresses each.