Hostname
zmcarry.com
Last fetched
zmcarry.com resolves to 12 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in US. WHOIS lists iana:244 as the registrar.
Nutrition Label
Resolution chain
zmcarry.com resolves to 12 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 18.154.253.11 | 18.154.252.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.154.253.14 | 18.154.252.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.154.253.52 | 18.154.252.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.154.253.96 | 18.154.252.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.164.68.101 | 3.164.68.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | FI |
| 3.164.68.117 | 3.164.68.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | FI |
| 3.164.68.120 | 3.164.68.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | FI |
| 3.164.68.46 | 3.164.68.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | FI |
| 3.171.139.121 | 3.171.136.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.171.139.32 | 3.171.136.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.171.139.78 | 3.171.136.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.171.139.86 | 3.171.136.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
WHOIS identity
- Registrar
- iana:244
- Organization
- hyunkyu kim
- Contact emails
Subdomains
2 observed subdomains of zmcarry.com.
| Subdomain |
|---|
| ask.zmcarry.com |
| www.zmcarry.com |
Threat posture
History
Mail and authentication
MX records
Related pages
Pivot deeper into the graph from zmcarry.com.
- IP · 18.154.253.11
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:244
- Country · US
- Email · zmcarryy@gmail.com
- TLD · .com
- Browse hostnames · zm…
- 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: "zmcarry.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.