Hostname
chatbuddy.buzz
Last fetched
chatbuddy.buzz resolves to 187.127.148.171, announced in 187.127.128.0/18 by AS-HOSTINGER - Hostinger International Limited in BR. chatbuddy.buzz is listed by 3 threat feeds; reconciled level HIGH.
Threat posture
40threat score (procedure-native scale)
HIGHListed by 3 threat feeds. At least one source recommends blocking.
Categories: Phishing
- Threat feeds listing this
- 3
- Verdict coverage
- malicious-evidenced
- First seen on a feed
- Wed, 26 Aug 2026 14:49:27 GMT
- Last seen on a feed
- Wed, 23 Sep 2026 00:32:13 GMT
Nutrition Label
Resolution chain
- 187.127.148.171
187.127.128.0/18 · AS-HOSTINGER - Hostinger International Limited
- 207.180.212.116
207.180.212.0/23 · CONTABO - Contabo GmbH · Frankfurt am Main, DE
- 95.111.240.227
95.111.240.0/23 · CONTABO - Contabo GmbH · Frankfurt am Main, DE
- 172.233.211.57
172.233.208.0/20 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.239.61.123
172.239.32.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.233.211.67
172.233.208.0/20 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
IPv6 resolution
No AAAA record for chatbuddy.buzz is recorded in WhisperGraph.
Attribution
hostinger international
ORIGIN_AS
WHOIS identity
- Registrar
- iana:1250
Subdomains
Mail and authentication
Nameservers
- a.nic.buzz
- b.nic.buzz
- c.nic.buzz
- ns1.dns.nic.buzz
- ns2.dns.nic.buzz
- ns3.dns.nic.buzz
- ns1.parklogic.com
- ns2.parklogic.com
- ns2.xhost.co.in
- ns4.xhost.co.in
- 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
MX records
- mail.chatbuddy.buzz
- mx156.hostedmxserver.com
SPF policy
- a: chatbuddy.buzz
- mx: chatbuddy.buzz
- ip: 207.180.212.116
Threat-feed evidence
History
Related pages
Pivot from chatbuddy.buzz 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: "chatbuddy.buzz"})-[: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.