Skip to content

Hostname

justplaycrazy.com

Last fetched

justplaycrazy.com resolves to 13.227.192.21, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. justplaycrazy.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 · justplaycrazy.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/justplaycrazy.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of justplaycrazy.com owner
Contact emails
13d4a4c0-6b4e-47a0-90b1-8a5c26e3f3f6@identity-protect.org, 2a004ec2-e5ec-46e4-85e5-fc6e95dd32d2@identity-protect.org, 74015a55-a9ec-491b-ae68-0649c81e2440@identity-protect.org, 74ec6e9b-9de2-45af-a285-b030317ada7f@identity-protect.org, 8d60f833-4631-496b-b4aa-fcac0e8febd8@identity-protect.org, b2a7d717-399b-4fdb-ba7b-ae7f448d01d3@identity-protect.org, c50ff4ca-c111-4d66-ae63-62ca0fd62dec@identity-protect.org

Subdomains

Subdomain
api.justplaycrazy.com
chat.justplaycrazy.com
log.justplaycrazy.com
res.justplaycrazy.com
ss.justplaycrazy.com

Showing 5 of 10. View all subdomains →

Mail and authentication

Nameservers

  • ns-455.awsdns-56.com
  • ns-810.awsdns-37.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-1240.awsdns-27.org
  • ns-1952.awsdns-52.co.uk

Threat-feed evidence

History

Related pages

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