Hostname
mechapunching.com
Last fetched
mechapunching.com resolves to 8 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in AU. WHOIS lists iana:468 as the registrar.
Nutrition Label
Resolution chain
mechapunching.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.64.50.128 | 18.64.48.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | AU |
| 18.64.50.23 | 18.64.48.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | AU |
| 18.64.50.4 | 18.64.48.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | AU |
| 18.64.50.55 | 18.64.48.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | AU |
| 3.164.206.113 | 3.164.206.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | FI |
| 3.164.206.115 | 3.164.206.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | FI |
| 3.164.206.125 | 3.164.206.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | FI |
| 3.164.206.18 | 3.164.206.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | FI |
WHOIS identity
- Registrar
- iana:468
- Organization
- on behalf of mechapunching.com owner
- Contact emails
- 0459de90-0f93-4a3b-ae75-3e7fdd842dc5@identity-protect.org
- 29727116-3350-44c2-9bd4-52cfe5c17f10@identity-protect.org
- 3a3c123e-5d32-46dc-894c-55582c584b85@identity-protect.org
- 57e65120-01d3-476a-9e8a-85e7ad9e7346@identity-protect.org
- 7cc4898e-38dc-4312-98fa-0895e1b1505f@identity-protect.org
- abcf46e0-2605-4c30-8f34-517bdc9792de@identity-protect.org
- owner-2517227@mechapunching.com.whoisprivacyservice.org
Threat posture
History
Related pages
Pivot deeper into the graph from mechapunching.com.
- IP · 18.64.50.128
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:468
- Country · AU
- Email · 0459de90-0f93-4a3b-ae75-3e7fdd842dc5@identity-protect.org
- TLD · .com
- Browse hostnames · me…
- 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: "mechapunching.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.