Hostname
difference.tokyo
Last fetched
difference.tokyo resolves to 12 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in US. WHOIS lists iana:49 as the registrar.
Nutrition Label
Resolution chain
difference.tokyo 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.169.202.59 | 3.169.200.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.169.202.6 | 3.169.200.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.169.202.60 | 3.169.200.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.169.202.83 | 3.169.200.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.170.42.127 | 3.170.40.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.170.42.56 | 3.170.40.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.170.42.61 | 3.170.40.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.170.42.84 | 3.170.40.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.171.214.100 | 3.171.212.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 3.171.214.125 | 3.171.212.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 3.171.214.58 | 3.171.212.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 3.171.214.7 | 3.171.212.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
WHOIS identity
- Registrar
- iana:49
- Organization
- —
- Contact emails
- —
Subdomains
19 observed subdomains of difference.tokyo.
Web-graph footprint
Distinct hostnames that link to or from difference.tokyo in the public web crawl.
165 sites link to this hostname.
186 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
4 SPF mechanisms authorising senders for difference.tokyo.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _spf.google.com |
| SPF_IP | 13.112.12.97 |
| SPF_IP | 13.112.84.50 |
| SPF_IP | 49.212.198.79 |
Related pages
Pivot deeper into the graph from difference.tokyo.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "difference.tokyo"})-[: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.