Hostname
askhemy.com
Last fetched
askhemy.com resolves to 8 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in US. WHOIS lists iana:468 as the registrar.
Nutrition Label
Resolution chain
askhemy.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.154.185.42 | 18.154.184.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.154.185.52 | 18.154.184.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.154.185.93 | 18.154.184.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.154.185.98 | 18.154.184.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.161.136.4 | 3.161.136.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.161.136.49 | 3.161.136.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.161.136.52 | 3.161.136.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.161.136.69 | 3.161.136.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
WHOIS identity
- Registrar
- iana:468
- Organization
- on behalf of askhemy.com owner
- Contact emails
- 1ee989c7-09a0-4520-b99f-5ed0018a8f80@identity-protect.org
- 492c8c27-19b7-4798-9653-f9eb1b96f434@identity-protect.org
- 7f285f0d-8914-400f-a6bc-d4bbdc29b5b2@identity-protect.org
- 906fd160-3d73-4197-a77e-bbbde3b7e72e@identity-protect.org
- e94087bf-c609-4983-b444-c1bb5fdde60c@identity-protect.org
- eb4f8a56-dabd-46bb-ac83-f13d27b9bbfb@identity-protect.org
Subdomains
1 observed subdomain of askhemy.com.
| Subdomain |
|---|
| www.askhemy.com |
Threat posture
History
Related pages
Pivot deeper into the graph from askhemy.com.
- IP · 18.154.185.42
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:468
- Country · US
- Email · 1ee989c7-09a0-4520-b99f-5ed0018a8f80@identity-protect.org
- TLD · .com
- Browse hostnames · as…
- 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: "askhemy.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.