Skip to content

Hostname

criminalip.com

Last fetched

criminalip.com resolves to 133.186.209.30, announced in 133.186.209.0/24 by NHN-AS-KR-KR - NHNCLOUD in JP. criminalip.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 · criminalip.comRouting diversity1.5/10Peering density3.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/criminalip.com

Resolution chain

IPv6 resolution

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

Attribution

nhncloud

ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of criminalip.com owner
Contact emails
0a898fcc-8096-407e-95ff-aa28a86041c9@identity-protect.org, 26786fec-92e8-4c0f-a109-42b4fe0cc035@identity-protect.org, 793a73b7-ce8a-4ba4-861f-2fe76e2f0c97@identity-protect.org, 9071eda2-b5af-4605-a870-a175fb23b2ac@identity-protect.org, 98033989-d351-4394-a5f2-abfc8edfbb1f@identity-protect.org, b8526e21-c952-4c95-9eb0-8adb49da35d8@identity-protect.org, c19edb5b-c49a-4fdf-98d7-44120f77709a@identity-protect.org, owner-5174357@criminalip.com.whoisprivacyservice.org, owner-5423987@criminalip.com.whoisprivacyservice.org, owner-5810904@criminalip.com.whoisprivacyservice.org, owner-5831223@criminalip.com.whoisprivacyservice.org, owner-6177799@criminalip.com.whoisprivacyservice.org, owner-6270685@criminalip.com.whoisprivacyservice.org, owner-8578348@criminalip.com.whoisprivacyservice.org

Subdomains

Subdomain
api.criminalip.com
security.criminalip.com
www.criminalip.com

Showing 3 of 3 subdomains (3 per page).

Mail and authentication

Nameservers

  • ns-97.awsdns-12.com
  • ns-1013.awsdns-62.net
  • ns-1501.awsdns-59.org
  • ns-2026.awsdns-61.co.uk

Threat-feed evidence

History

Related pages

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