Hostname
help.play.hosting
Last fetched
help.play.hosting resolves to 66.33.60.129, announced in 66.33.60.0/24 by AMAZON-02 - Amazon.com, Inc. in US. help.play.hosting 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
- 66.33.60.129
66.33.60.0/24 · AMAZON-02 - Amazon.com, Inc. · Walnut, US
- 66.33.60.130
66.33.60.0/24 · AMAZON-02 - Amazon.com, Inc. · Walnut, US
- 66.33.60.194
66.33.60.0/24 · AMAZON-02 - Amazon.com, Inc. · Walnut, US
- 66.33.60.66
66.33.60.0/24 · AMAZON-02 - Amazon.com, Inc. · Walnut, US
- 76.76.21.142
- 76.76.21.22
- 76.76.21.61
- 76.76.21.93
IPv6 resolution
No AAAA record for help.play.hosting is recorded in WhisperGraph.
Attribution
amazon com
ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for help.play.hosting. 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
- gamma.seo-anomaly-beijing.online
- beta.seo-anomaly-delhi.online
- beta.seo-anomaly-dhaka.online
- gamma.seo-anomaly-dhaka.online
- gamma.seo-anomaly-jakarta.online
- gamma.seo-anomaly-lagos.online
- gamma.seo-anomaly-lahore.online
- gamma.seo-anomaly-manila.online
- beta.seo-anomaly-moscow.online
- gamma.seo-anomaly-osaka.online
Mail and authentication
Nameservers
- ns1.vercel-dns-3.com
- ns2.vercel-dns-3.com
- ns3.vercel-dns-3.com
- ns4.vercel-dns-3.com
Threat-feed evidence
History
Related pages
Pivot from help.play.hosting 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: "help.play.hosting"})-[: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.