Hostname
hataractive.jp
Last fetched
hataractive.jp resolves to 12 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in US.
Nutrition Label
Resolution chain
hataractive.jp 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.160.172.113 | 18.160.168.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.160.172.117 | 18.160.168.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.160.172.24 | 18.160.168.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.160.172.7 | 18.160.168.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.164.13.12 | 18.164.12.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | PE |
| 18.164.13.16 | 18.164.12.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | PE |
| 18.164.13.62 | 18.164.12.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | PE |
| 18.164.13.8 | 18.164.12.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | PE |
| 65.8.131.103 | 65.8.130.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 65.8.131.109 | 65.8.130.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 65.8.131.44 | 65.8.130.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 65.8.131.58 | 65.8.130.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
WHOIS identity
- Registrar
- —
- Organization
- leverages_inc
- Contact emails
Subdomains
8 observed subdomains of hataractive.jp.
Web-graph footprint
Distinct hostnames that link to or from hataractive.jp in the public web crawl.
749 sites link to this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
7 SPF mechanisms authorising senders for hataractive.jp.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | mktomail.com |
| SPF_IP | 153.122.0.54 |
| SPF_IP | 157.7.162.109/32 |
| SPF_IP | 157.7.171.46 |
| SPF_IP | 18.180.248.129 |
| SPF_IP | 3.115.1.60 |
| SPF_MX | hataractive.jp |
Related pages
Pivot deeper into the graph from hataractive.jp.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "hataractive.jp"})-[: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.