Hostname
do-eels-exist.com
Last fetched
do-eels-exist.com resolves to 8 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in BR. WHOIS lists iana:468 as the registrar.
Nutrition Label
Resolution chain
do-eels-exist.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.164.32.111 | 18.164.32.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | BR |
| 18.164.32.49 | 18.164.32.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | BR |
| 18.164.32.52 | 18.164.32.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | BR |
| 18.164.32.57 | 18.164.32.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | BR |
| 99.84.234.103 | 99.84.232.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 99.84.234.125 | 99.84.232.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 99.84.234.14 | 99.84.232.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 99.84.234.99 | 99.84.232.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
WHOIS identity
- Registrar
- iana:468
- Organization
- on behalf of do-eels-exist.com owner
- Contact emails
- 3dc031cc-2f55-4552-ba64-9727a89b541b@identity-protect.org
- 50ec4a76-3761-4453-98d9-9e2deb3565af@identity-protect.org
- 75c56f38-28ad-4a20-842e-514433874551@identity-protect.org
- 7fe90b60-e7c0-418d-8eb1-9969af5016e2@identity-protect.org
- b66afb4a-745c-4587-9098-e72c366af7bf@identity-protect.org
- f3b83894-16e4-4d3e-b05c-b4cfef80cd5e@identity-protect.org
- owner-7214052@do-eels-exist.com.whoisprivacyservice.org
Threat posture
History
Related pages
Pivot deeper into the graph from do-eels-exist.com.
- IP · 18.164.32.111
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:468
- Country · BR
- Email · 3dc031cc-2f55-4552-ba64-9727a89b541b@identity-protect.org
- TLD · .com
- Browse hostnames · do…
- 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: "do-eels-exist.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.