Hostname
amopus.com
Last fetched
amopus.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
amopus.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.49.114 | 18.238.48.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.238.49.3 | 18.238.48.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.238.49.56 | 18.238.48.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.238.49.89 | 18.238.48.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 99.84.203.118 | 99.84.200.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 99.84.203.120 | 99.84.200.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 99.84.203.124 | 99.84.200.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 99.84.203.3 | 99.84.200.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
WHOIS identity
- Registrar
- iana:468
- Organization
- on behalf of amopus.com owner
- Contact emails
- caomujiemian@hotmail.com
- 2db2887a-297c-4eb0-ab5b-8f8513c8e393@identity-protect.org
- 366930d6-d95f-4a82-bd82-99737c3d7e57@identity-protect.org
- 5b90525e-8476-47db-8a00-7fa7eb022e4f@identity-protect.org
- 64d324c0-c6b3-42ff-95e9-ad44d818f052@identity-protect.org
- 652da6e4-1871-4b0b-853b-af649e939b77@identity-protect.org
- c97b84de-1fbe-479c-bbc3-84d782f161a1@identity-protect.org
- dfd62629-dd56-4f30-a7a2-bf093bbbe6c2@identity-protect.org
Subdomains
6 observed subdomains of amopus.com.
Threat posture
History
Related pages
Pivot deeper into the graph from amopus.com.
- IP · 18.238.49.114
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:468
- Country · US
- Email · caomujiemian@hotmail.com
- TLD · .com
- Browse hostnames · am…
- 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: "amopus.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.