Hostname
mytrafficdata2.com
Last fetched
mytrafficdata2.com resolves to 8 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in DE. WHOIS lists iana:468 as the registrar.
Nutrition Label
Resolution chain
mytrafficdata2.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 |
|---|---|---|---|---|
| 13.33.187.108 | 13.33.197.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 13.33.187.114 | 13.33.197.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 13.33.187.17 | 13.33.197.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 13.33.187.81 | 13.33.197.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 13.35.20.40 | 13.35.29.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IN |
| 13.35.20.77 | 13.35.29.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IN |
| 13.35.20.82 | 13.35.29.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IN |
| 13.35.20.96 | 13.35.29.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IN |
WHOIS identity
- Registrar
- iana:468
- Organization
- on behalf of mytrafficdata2.com owner
- Contact emails
Subdomains
10 observed subdomains of mytrafficdata2.com.
Web-graph footprint
Distinct hostnames that link to or from mytrafficdata2.com in the public web crawl.
Sample inbound links
Threat posture
History
Mail and authentication
SPF policy
1 SPF mechanism authorising senders for mytrafficdata2.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _spf.mailersend.net |
Related pages
Pivot deeper into the graph from mytrafficdata2.com.
- IP · 13.33.187.108
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:468
- Country · DE
- Email · 2567a9ca-c098-4ffc-b153-a370ccb5aec3@identity-protect.org
- TLD · .com
- Browse hostnames · my…
- 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: "mytrafficdata2.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.