Hostname
criminalpages.com
Last fetched
criminalpages.com resolves to 8 IPv4 addresses operated by AMAZON-AES - Amazon.com, Inc. in US. WHOIS lists iana:146 as the registrar.
Nutrition Label
Resolution chain
criminalpages.com resolves to 8 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 18.233.4.14 | 18.232.0.0/14 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.221.115.17 | 3.208.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 34.197.132.114 | 34.192.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.20.173.61 | 52.20.0.0/14 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.86.56.99 | 52.86.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.80.73.89 | 54.80.0.0/14 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.82.120.4 | 54.80.0.0/14 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 98.95.150.241 | 98.88.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
WHOIS identity
- Registrar
- iana:146
- Organization
- domain privacy service fbo registrant.
- Contact emails
Subdomains
3 observed subdomains of criminalpages.com.
Web-graph footprint
Distinct hostnames that link to or from criminalpages.com in the public web crawl.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
4 SPF mechanisms authorising senders for criminalpages.com.
| Mechanism | Target |
|---|---|
| SPF_A | criminalpages.com |
| SPF_INCLUDE | mail.zendesk.com |
| SPF_IP | 74.206.229.142 |
| SPF_MX | criminalpages.com |
Related pages
Pivot deeper into the graph from criminalpages.com.
- IP · 18.233.4.14
- ASN · AS14618AMAZON-AES - Amazon.com, Inc.
- Registrar · iana:146
- Country · US
- Email · criminalpages.com@domainprivacygroup.com
- TLD · .com
- Browse hostnames · cr…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
- United States internet infrastructure
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "criminalpages.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.