Hostname
torrentclaw.com
Last fetched
torrentclaw.com resolves to 104.21.51.129, announced in 104.21.48.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. torrentclaw.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
- 104.21.51.129
104.21.48.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.21.68.56
104.21.64.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.26.10.63
104.26.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.26.11.63
104.26.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.180.156
172.67.176.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.187.190
172.67.176.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.69.198
172.67.64.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.96.3
188.114.96.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.97.3
188.114.97.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for torrentclaw.com. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Subdomains
| Subdomain |
|---|
| addon.torrentclaw.com |
| git.torrentclaw.com |
| staging.torrentclaw.com |
| stremio.torrentclaw.com |
| t.torrentclaw.com |
| tracker.torrentclaw.com |
Showing 6 of 6 subdomains (6 per page).
Mail and authentication
Nameservers
- carla.ns.cloudflare.com
- jack.ns.cloudflare.com
- rita.ns.cloudflare.com
- robert.ns.cloudflare.com
MX records
- route1.mx.cloudflare.net
- route2.mx.cloudflare.net
- route3.mx.cloudflare.net
Threat-feed evidence
History
Related pages
Pivot from torrentclaw.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: "torrentclaw.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.