Hostname
ahdmw.com
Last fetched
ahdmw.com resolves to 13.227.192.105, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. ahdmw.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 13.227.192.105
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.34
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.88
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.90
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.32.121.10
13.32.120.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.32.121.24
13.32.120.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.32.121.34
13.32.120.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.32.121.83
13.32.120.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.238.55.127
18.238.55.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 18.238.55.35
18.238.55.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 18.238.55.37
18.238.55.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 18.238.55.62
18.238.55.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- hefei secco culture media co.,ltd.
- Contact emails
- proxy@whoisprotectservice.com, wbpwbpwbp@qq.com, 044d5333-cf1a-4f9d-bdcc-d2341e6f0e4f@identity-protect.org, 13697ab5-f990-4385-a61f-fca2cc2afa00@identity-protect.org, 6db02e24-bc7e-42c7-b062-976ab801e405@identity-protect.org, e53974b6-9931-4cf4-ae46-b64d01bc7b40@identity-protect.org
Subdomains
Showing 4 of 4 subdomains (4 per page).
Mail and authentication
Nameservers
- ns-238.awsdns-29.com
- ns-679.awsdns-20.net
- ns-1320.awsdns-37.org
- ns-1682.awsdns-18.co.uk
Threat-feed evidence
History
Related pages
Pivot from ahdmw.com into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "ahdmw.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.