Hostname

zzacjt.com

Last fetched Tue, 15 Sep 2026 07:46:31 GMT

zzacjt.com resolves to 156.233.235.168, announced in 156.233.234.0/23 by COGNETCLOUD-2 - cognetcloud INC in HK. zzacjt.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this: 0
Verdict coverage: known-clean

Nutrition Label

Resolution chain

156.233.235.168
156.233.234.0/23 · COGNETCLOUD-2 - cognetcloud INC · Hong Kong, HK
38.76.213.91
38.76.212.0/23 · COGNETCLOUD-2 - cognetcloud INC · San Jose, US
23.147.52.136
23.147.52.0/24 · PEEKABO - Peekabo Networks · Aurora, US
38.76.213.122
38.76.212.0/23 · COGNETCLOUD-2 - cognetcloud INC · San Jose, US
38.76.213.92
38.76.212.0/23 · COGNETCLOUD-2 - cognetcloud INC · San Jose, US
103.249.110.192
103.249.110.0/24 · SONDERCLOUDLIMITED-AS-AP - SonderCloud Limited · Mong Kok, HK
23.147.52.135
23.147.52.0/24 · PEEKABO - Peekabo Networks · Aurora, US
38.76.213.90
38.76.212.0/23 · COGNETCLOUD-2 - cognetcloud INC · San Jose, US
103.254.149.143
103.254.149.0/24 · SONDERCLOUDLIMITED-AS-AP - SonderCloud Limited · Mong Kok, HK
103.254.150.138
103.254.150.0/24 · SONDERCLOUDLIMITED-AS-AP - SonderCloud Limited · Mong Kok, HK
103.254.148.177
103.254.148.0/24 · SONDERCLOUDLIMITED-AS-AP - SonderCloud Limited · Mong Kok, HK
103.59.147.66
103.59.147.0/24 · SONDERCLOUDLIMITED-AS-AP - SonderCloud Limited · Mong Kok, HK

IPv6 resolution

No AAAA record for zzacjt.com is recorded in WhisperGraph.

Attribution

cognetcloud

ORIGIN_AS

WHOIS identity

Registrar: iana:3758

Mail and authentication

Nameservers

delilah.ns.cloudflare.com
neil.ns.cloudflare.com
ns1.judns.com
ns2.judns.com
a.gtld-servers.net
b.gtld-servers.net
c.gtld-servers.net
d.gtld-servers.net
e.gtld-servers.net
f.gtld-servers.net
g.gtld-servers.net
h.gtld-servers.net
i.gtld-servers.net
j.gtld-servers.net
k.gtld-servers.net
l.gtld-servers.net
m.gtld-servers.net

Threat-feed evidence

History

Pivot from zzacjt.com into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "zzacjt.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.