Hostname
hackerbot.net
Last fetched
hackerbot.net resolves to 104.26.12.89, announced in 104.28.1.0/24 by CLOUDFLARENET - Cloudflare, Inc. in CA. hackerbot.net is listed by 1 threat feed; reconciled level HIGH.
Threat posture
40threat score (procedure-native scale)
HIGHListed by 1 threat feed. At least one source recommends blocking.
Categories: Phishing
- Threat feeds listing this
- 1
- Verdict coverage
- malicious-evidenced
- First seen on a feed
- Wed, 26 Aug 2026 14:50:40 GMT
- Last seen on a feed
- Sun, 13 Sep 2026 00:52:19 GMT
Nutrition Label
Resolution chain
- 104.26.12.89
104.28.1.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.26.13.89
104.28.1.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.72.105
172.68.4.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 8.47.69.0
8.47.97.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Bratislava, SK
- 8.6.112.0
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:1328
- Registrant organisation
- littlesquid
- Contact emails
- samstein@hispeed.ch, samstein@hotmail.de, info@domain-contact.org
Subdomains
| Subdomain |
|---|
| forum.hackerbot.net |
| www.hackerbot.net |
Showing 2 of 2 subdomains (2 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- ian.ns.cloudflare.com
- pat.ns.cloudflare.com
- 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
Related pages
Pivot from hackerbot.net 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: "hackerbot.net"})-[: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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.