Hostname
tp-cdn.com
Last fetched
tp-cdn.com resolves to 13.38.60.183, announced in 13.36.0.0/14 by AMAZON-02 - Amazon.com, Inc. in FR. tp-cdn.com is listed by 1 threat feed; reconciled level HIGH.
Threat posture
40threat score (procedure-native scale)
HIGHListed by 1 threat feed. At least one source recommends blocking.
- Threat feeds listing this
- 1
- Verdict coverage
- malicious-evidenced
- First seen on a feed
- Wed, 26 Aug 2026 14:51:25 GMT
- Last seen on a feed
- Sun, 13 Sep 2026 23:27:23 GMT
Nutrition Label
Resolution chain
- 13.38.60.183
13.36.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Paris, FR
- 134.209.106.11
- 134.209.151.13
134.209.144.0/20 · DIGITALOCEAN-ASN - DigitalOcean, LLC · Bengaluru, IN
- 142.93.106.44
- 159.223.39.167
- 159.65.80.89
159.65.80.0/20 · DIGITALOCEAN-ASN - DigitalOcean, LLC · London, GB
- 165.22.209.237
165.22.208.0/20 · DIGITALOCEAN-ASN - DigitalOcean, LLC · Bengaluru, IN
- 165.227.171.157
165.227.160.0/20 · DIGITALOCEAN-ASN - DigitalOcean, LLC · Frankfurt am Main, DE
- 206.189.89.35
- 209.97.173.191
- 46.101.165.137
46.101.128.0/17 · DIGITALOCEAN-ASN - DigitalOcean, LLC · Frankfurt am Main, DE
- 64.227.164.47
64.227.160.0/20 · DIGITALOCEAN-ASN - DigitalOcean, LLC · Bengaluru, IN
- 64.227.177.130
64.227.176.0/20 · DIGITALOCEAN-ASN - DigitalOcean, LLC · Bengaluru, IN
IPv6 resolution
No AAAA record for tp-cdn.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:2086
- Registrant organisation
- domain administrator
- Contact emails
- tp-cdn.com@namebrightprivacy.com, hostmaster@visa.com
Subdomains
Showing 4 of 4 subdomains (4 per page).
Mail and authentication
Nameservers
- ns-117.awsdns-14.com
- ns-218.awsdns-27.com
- ns-639.awsdns-15.net
- ns-747.awsdns-29.net
- ns-1120.awsdns-12.org
- ns-1441.awsdns-52.org
- ns-1743.awsdns-25.co.uk
- ns-1939.awsdns-50.co.uk
Threat-feed evidence
History
Related pages
Pivot from tp-cdn.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: "tp-cdn.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.