Hostname
tracesurfer.com
Last fetched
tracesurfer.com resolves to 13.33.82.15, announced in 13.33.80.0/21 by AMAZON-02 - Amazon.com, Inc. in US. tracesurfer.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 13.33.82.15
13.33.80.0/21 · AMAZON-02 - Amazon.com, Inc. · Boston, US
- 13.33.82.37
13.33.80.0/21 · AMAZON-02 - Amazon.com, Inc. · Boston, US
- 13.33.82.46
13.33.80.0/21 · AMAZON-02 - Amazon.com, Inc. · Boston, US
- 13.33.82.58
13.33.80.0/21 · AMAZON-02 - Amazon.com, Inc. · Boston, US
- 18.239.208.119
18.239.208.0/21 · AMAZON-02 - Amazon.com, Inc. · Brussels, BE
- 18.239.208.43
18.239.208.0/21 · AMAZON-02 - Amazon.com, Inc. · Brussels, BE
- 18.239.208.70
18.239.208.0/21 · AMAZON-02 - Amazon.com, Inc. · Brussels, BE
- 18.239.208.83
18.239.208.0/21 · AMAZON-02 - Amazon.com, Inc. · Brussels, BE
IPv6 resolution
No AAAA record for tracesurfer.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- alium
- Contact emails
- 4cf0a8e7-0b62-4eb0-992a-7bc8a0657abf@identity-protect.org, 584a75b1-6d68-4cff-9323-fa84290c75f7@identity-protect.org, 68b5d5ae-57db-4a18-a505-7c7c9a02062f@identity-protect.org, 861ba140-0da8-4614-847e-ec3aa26e41ea@identity-protect.org, 8ccbdcd3-091c-4198-9ec6-67a31e3dc9c9@identity-protect.org, e82fee60-c87f-403f-a69c-ab3d893c2473@identity-protect.org, ec59568e-8f42-4ed2-8fc6-7d2cd66fe8ab@identity-protect.org, owner-7522524@tracesurfer.com.whoisprivacyservice.org
Subdomains
Showing 4 of 4 subdomains (4 per page).
Mail and authentication
Nameservers
- ns-125.awsdns-15.com
- ns-609.awsdns-12.net
- ns-1301.awsdns-34.org
- ns-1990.awsdns-56.co.uk
Threat-feed evidence
History
Related pages
Pivot from tracesurfer.com into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "tracesurfer.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.