Hostname
loopcatch.com
Last fetched
loopcatch.com resolves to 104.21.16.106, announced in 104.21.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. loopcatch.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.16.106
104.21.16.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.21.19.97
104.21.16.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.167.64
172.67.160.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.185.187
172.67.176.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 loopcatch.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 |
|---|
| www.loopcatch.com |
Showing 1 of 1 subdomain (1 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- anastasia.ns.cloudflare.com
- andy.ns.cloudflare.com
- elijah.ns.cloudflare.com
- jobs.ns.cloudflare.com
- lauryn.ns.cloudflare.com
- mallory.ns.cloudflare.com
- max.ns.cloudflare.com
- paislee.ns.cloudflare.com
- paityn.ns.cloudflare.com
- tim.ns.cloudflare.com
Threat-feed evidence
History
Related pages
Pivot from loopcatch.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: "loopcatch.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.