Skip to content

Hostname

playdemic.com

Last fetched

playdemic.com resolves to 18.173.132.102, announced in 18.173.132.0/22 by AMAZON-02 - Amazon.com, Inc. in US. playdemic.com 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 · playdemic.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/playdemic.com

Resolution chain

IPv6 resolution

No AAAA record for playdemic.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:299
Registrant organisation
domain administrator
Contact emails
adrian.hall@playdemic.com, hostmaster2@ea.com, dataprivacyprotected@1und1.de, dataprivacyprotected@ionos.de

Subdomains

Subdomain
analytics.playdemic.com
autodiscover.playdemic.com
cdn.playdemic.com
cdn2.playdemic.com
email.playdemic.com
ftp.playdemic.com
playgk-admin.playdemic.com
playgk.playdemic.com
playgr.playdemic.com
privacy.playdemic.com
staging.playdemic.com
store.playdemic.com

Showing 12 of 26. View all subdomains →

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

Mail and authentication

Nameservers

  • ns-78.awsdns-09.com
  • ns-1002.awsdns-61.net
  • ns-1259.awsdns-29.org
  • ns-1752.awsdns-27.co.uk

MX records

  • playdemic-com.mail.protection.outlook.com

SPF policy

  • include: amazonses.com
  • include: spf.protection.outlook.com
  • include: spfb.wbgames.com
  • include: spfc.wbgames.com
  • ip: 195.171.165.141
  • ip: 205.220.160.51
  • ip: 205.220.172.51

Threat-feed evidence

History

Related pages

Pivot from playdemic.com 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: "playdemic.com"})-[: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.