Hostname
bedoca.com
Last fetched
bedoca.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
bedoca.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.238.152.121 | 18.238.152.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.238.152.35 | 18.238.152.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.238.152.36 | 18.238.152.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.238.152.41 | 18.238.152.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 99.86.159.122 | 99.86.158.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | PT |
| 99.86.159.14 | 99.86.158.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | PT |
| 99.86.159.19 | 99.86.158.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | PT |
| 99.86.159.46 | 99.86.158.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | PT |
WHOIS identity
- Registrar
- iana:468
- Organization
- on behalf of bedoca.com owner
- Contact emails
- 0c26969f-4e9e-4628-b43c-4e83b10923c1@identity-protect.org
- 35a2d534-82f8-4494-9d76-ee2743c899dc@identity-protect.org
- 3a31a203-bc09-4f88-ae35-ae17c3b63fa0@identity-protect.org
- 4b4803ea-d16e-4ab2-b2b8-1410601fe271@identity-protect.org
- 8ce79949-d38b-4d52-ad67-34b2d5ba7c54@identity-protect.org
- d27d77c4-1037-424a-8d50-4ec7d4951168@identity-protect.org
- d9d0f1c5-b43d-41ad-96bb-d9b90b42cd8f@identity-protect.org
Threat posture
History
Related pages
Pivot deeper into the graph from bedoca.com.
- IP · 18.238.152.121
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:468
- Country · US
- Email · 0c26969f-4e9e-4628-b43c-4e83b10923c1@identity-protect.org
- TLD · .com
- Browse hostnames · be…
- 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: "bedoca.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.