Skip to content

Hostname

play.apps.appsplatform.us

Last fetched

play.apps.appsplatform.us resolves to 20.140.68.155, announced in 20.140.0.0/15 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in US. play.apps.appsplatform.us is listed by 2 threat feeds; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 2 threat feeds. At least one source recommends blocking.

Categories: Phishing

Threat feeds listing this
2
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:49:49 GMT
Last seen on a feed
Sun, 20 Sep 2026 20:18:26 GMT

Nutrition Label

WHISPER CANON · play.apps.appsplatform.usRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings6.8/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/play.apps.appsplatform.us

Resolution chain

IPv6 resolution

Attribution

Microsoft

cloud · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for play.apps.appsplatform.us. 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

Subdomain
instance-ude.play.apps.appsplatform.us

Showing 1 of 1 subdomain (1 per page).

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

  • 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
  • tm1.dns-tm.us
  • tm2.dns-tm.us
  • tm1.edgedns-tm.us
  • tm2.edgedns-tm.us

Threat-feed evidence

History

Related pages

Pivot from play.apps.appsplatform.us 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.apps.appsplatform.us"})-[: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.