Skip to content

Hostname

play.net

Last fetched

play.net resolves to 108.139.60.41, announced in 108.139.60.0/22 by AMAZON-02 - Amazon.com, Inc. in AE. play.net is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · play.netRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/play.net

Resolution chain

IPv6 resolution

No AAAA record for play.net is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:106
Contact emails
88e0a7755f804f1b8aa10589f04d6797.protect@whoisguard.com, a951c5c543994640a54ed13a6b1e5cf8.protect@whoisguard.com, b2dccf161baf47e2aa4f99739948e875.protect@whoisguard.com, baa321380dcf49058ffc3a3c104f139d.protect@whoisguard.com, ff08d58ef1834dbba90374293bbfd3b7.protect@whoisguard.com, 204d8079dcad40c28eea413afc5b88e7.protect@withheldforprivacy.com, 9f4f3b8e27c54f4b95949760c85fee8c.protect@withheldforprivacy.com, e7b84f6276004131ae7039d2e2b9e70c.protect@withheldforprivacy.com

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • ns-379.awsdns-47.com
  • ns-893.awsdns-47.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-1162.awsdns-17.org
  • ns-1881.awsdns-43.co.uk

MX records

  • sire.simutronics.com
  • newman.simutronics.com

SPF policy

  • redirect: simutronics.com

Threat-feed evidence

History

Related pages

Pivot from 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: "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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.