Hostname
buzzy.now
Last fetched
buzzy.now resolves to 216.150.1.129, announced in 216.150.1.0/24 by AMAZON-02 - Amazon.com, Inc. in US. buzzy.now is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 216.150.1.129
216.150.1.0/24 · AMAZON-02 - Amazon.com, Inc. · Walnut, US
- 216.150.1.193
216.150.1.0/24 · AMAZON-02 - Amazon.com, Inc. · Walnut, US
- 216.150.1.65
216.150.1.0/24 · AMAZON-02 - Amazon.com, Inc. · Walnut, US
- 216.150.16.1
216.150.16.0/24 · AMAZON-02 - Amazon.com, Inc. · Walnut, US
- 216.150.16.129
216.150.16.0/24 · AMAZON-02 - Amazon.com, Inc. · Walnut, US
- 216.150.16.193
216.150.16.0/24 · AMAZON-02 - Amazon.com, Inc. · Walnut, US
- 216.150.16.65
216.150.16.0/24 · AMAZON-02 - Amazon.com, Inc. · Walnut, US
IPv6 resolution
IPv6 resolution is temporarily unavailable.
The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.
Attribution is temporarily unavailable.
The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for buzzy.now. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Subdomains
Subdomains is temporarily unavailable.
The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.
Mail and authentication
Nameservers
- dylan.ns.cloudflare.com
- kay.ns.cloudflare.com
MX records
- mx1.feishu.cn
- mx2.feishu.cn
- mx3.feishu.cn
SPF policy
- include: _netblocks.m.feishu.cn
Threat-feed evidence
History
Related pages
Pivot from buzzy.now 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: "buzzy.now"})-[: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.