Hostname
train321.com
Last fetched
train321.com resolves to 8 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in US. WHOIS lists iana:468 as the registrar.
Nutrition Label
Resolution chain
train321.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 |
|---|---|---|---|---|
| 108.139.47.107 | 108.139.44.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 108.139.47.12 | 108.139.44.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 108.139.47.127 | 108.139.44.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 108.139.47.39 | 108.139.44.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 54.240.174.19 | 54.240.174.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | GB |
| 54.240.174.60 | 54.240.174.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | GB |
| 54.240.174.70 | 54.240.174.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | GB |
| 54.240.174.80 | 54.240.174.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | GB |
WHOIS identity
- Registrar
- iana:468
- Organization
- on behalf of train321.com owner
- Contact emails
Subdomains
33 observed subdomains of train321.com.
Showing 25 of 33. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from train321.com in the public web crawl.
9 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
1 SPF mechanism authorising senders for train321.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | amazonses.com |
Related pages
Pivot deeper into the graph from train321.com.
- IP · 108.139.47.107
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:468
- Country · US
- Email · c6fed17c-7eb1-4324-9b3e-4115c9222680@identity-protect.org
- TLD · .com
- Browse hostnames · tr…
- 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: "train321.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.