Hostname
beta.play.net
Last fetched
beta.play.net resolves to 18.172.242.102, announced in 18.172.240.0/21 by AMAZON-02 - Amazon.com, Inc. in HU. beta.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
- 18.172.242.102
18.172.240.0/21 · AMAZON-02 - Amazon.com, Inc. · Budapest, HU
- 18.172.242.3
18.172.240.0/21 · AMAZON-02 - Amazon.com, Inc. · Budapest, HU
- 18.172.242.30
18.172.240.0/21 · AMAZON-02 - Amazon.com, Inc. · Budapest, HU
- 18.172.242.62
18.172.240.0/21 · AMAZON-02 - Amazon.com, Inc. · Budapest, HU
- 54.192.117.101
54.192.117.0/24 · AMAZON-02 - Amazon.com, Inc. · Kuala Lumpur, MY
- 54.192.117.110
54.192.117.0/24 · AMAZON-02 - Amazon.com, Inc. · Kuala Lumpur, MY
- 54.192.117.14
54.192.117.0/24 · AMAZON-02 - Amazon.com, Inc. · Kuala Lumpur, MY
- 54.192.117.96
54.192.117.0/24 · AMAZON-02 - Amazon.com, Inc. · Kuala Lumpur, MY
IPv6 resolution
No AAAA record for beta.play.net is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for beta.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.
Mail and authentication
Nameservers
- ns-130.awsdns-16.com
- ns-969.awsdns-57.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
- 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 beta.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: "beta.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.