Hostname

hassbian.com

Last fetched Mon, 21 Sep 2026 22:48:18 GMT

hassbian.com resolves to 101.33.17.208, announced in 101.33.17.0/24 by TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue in JP. hassbian.com is listed by 1 threat feed; reconciled level CRITICAL.

Threat posture

60threat score (procedure-native scale)

CRITICAL

Listed by 1 threat feed. At least one source recommends blocking.

Categories: Command-and-control

Threat feeds listing this: 1
Verdict coverage: malicious-evidenced
First seen on a feed: Wed, 26 Aug 2026 14:45:24 GMT
Last seen on a feed: Sun, 20 Sep 2026 19:41:37 GMT

Nutrition Label

Resolution chain

101.33.17.208
101.33.17.0/24 · TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue
43.132.85.153
43.132.85.0/24 · ACE-AS-AP - ACE
43.152.26.58
43.152.26.0/24 · ACE-AS-AP - ACE
43.174.246.40
43.174.246.0/24 · ACE-AS-AP - ACE
43.174.247.40
43.174.247.0/24 · ACE-AS-AP - ACE
43.175.182.15
43.175.182.0/24 · ACE-AS-AP - ACE · Tucumcari, US
43.175.44.57
43.175.44.0/24 · ACE-AS-AP - ACE · Hong Kong, HK
101.33.10.10
101.33.10.0/24 · ACE-AS-AP - ACE · Frankfurt am Main, DE

IPv6 resolution

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

Attribution

shenzhen tencent computer

ORIGIN_AS

WHOIS identity

Registrar: iana:120
Registrant organisation: jin ping gao
Contact emails: 910211574@126.com

Subdomains

Subdomain
bbs.hassbian.com
cutimg.hassbian.com
wghaos.hassbian.com
www.hassbian.com

Showing 4 of 4 subdomains (4 per page).

Mail and authentication

Nameservers

ns3.dnsv4.com
ns4.dnsv4.com
ns1.qeodns.com
ns2.qeodns.com
meteorologist.dnspod.net
zenobia.dnspod.net
a.root-servers.net
b.root-servers.net
c.root-servers.net
d.root-servers.net
e.root-servers.net
f.root-servers.net
g.root-servers.net
h.root-servers.net
i.root-servers.net
j.root-servers.net
k.root-servers.net
l.root-servers.net
m.root-servers.net

Threat-feed evidence

History

Pivot from hassbian.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: "hassbian.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.