Hostname
buddy.play.net
Last fetched
buddy.play.net resolves to 108.138.106.21, announced in 108.138.106.0/23 by AMAZON-02 - Amazon.com, Inc. in US. buddy.play.net 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
- 108.138.106.21
108.138.106.0/23 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 108.138.106.24
108.138.106.0/23 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 108.138.106.47
108.138.106.0/23 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 108.138.106.89
108.138.106.0/23 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 13.35.186.103
13.35.186.0/24 · AMAZON-02 - Amazon.com, Inc. · Hong Kong, HK
- 13.35.186.27
13.35.186.0/24 · AMAZON-02 - Amazon.com, Inc. · Hong Kong, HK
- 13.35.186.30
13.35.186.0/24 · AMAZON-02 - Amazon.com, Inc. · Hong Kong, HK
- 13.35.186.76
13.35.186.0/24 · AMAZON-02 - Amazon.com, Inc. · Hong Kong, HK
IPv6 resolution
No AAAA record for buddy.play.net is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for buddy.play.net. 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.
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
Sample outbound links
Mail and authentication
Nameservers
- ns-130.awsdns-16.com
- ns-969.awsdns-57.net
- ns-1135.awsdns-13.org
- ns-1679.awsdns-17.co.uk
MX records
- sire.simutronics.com
SPF policy
- ip: 199.188.208.0/24
- include: amazonses.com
- include: _spf.google.com
- a: ifewiki.play.net
- ip: 99.178.155.241
Threat-feed evidence
History
Related pages
Pivot from buddy.play.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: "buddy.play.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.