Hostname
store.tleague.jp
Last fetched
store.tleague.jp resolves to 12 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in US.
Nutrition Label
Resolution chain
store.tleague.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 |
|---|---|---|---|---|
| 3.162.163.110 | 3.162.160.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.162.163.29 | 3.162.160.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.162.163.48 | 3.162.160.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.162.163.68 | 3.162.160.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.163.60.110 | 3.163.60.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | CO |
| 3.163.60.24 | 3.163.60.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | CO |
| 3.163.60.36 | 3.163.60.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | CO |
| 3.163.60.76 | 3.163.60.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | CO |
| 3.170.221.53 | 3.170.220.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 3.170.221.64 | 3.170.220.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 3.170.221.77 | 3.170.220.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 3.170.221.79 | 3.170.220.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
WHOIS identity
No WHOIS records are currently associated with store.tleague.jp in WhisperGraph.
Subdomains
1 observed subdomain of store.tleague.jp.
| Subdomain |
|---|
| eccube01.store.tleague.jp |
Web-graph footprint
Distinct hostnames that link to or from store.tleague.jp in the public web crawl.
9 sites link to this hostname.
23 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
3 SPF mechanisms authorising senders for store.tleague.jp.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | kagoya.net |
| SPF_IP | 54.168.139.88 |
| SPF_IP | 54.199.255.242 |
Related pages
Pivot deeper into the graph from store.tleague.jp.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "store.tleague.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.