Hostname
capovex.com
Last fetched
capovex.com resolves to 104.21.46.238, announced in 104.21.32.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. capovex.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.46.238
104.21.32.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 13.204.137.73
13.204.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 15.207.1.152
15.206.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 172.67.143.42
172.67.128.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 3.108.93.160
3.108.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 3.6.215.193
3.6.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 65.1.40.240
65.0.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 65.1.52.52
65.0.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 65.1.57.24
65.0.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 13.203.84.170
13.202.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 13.206.111.65
13.204.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 43.204.239.178
43.204.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 13.206.180.84
13.204.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 13.201.164.42
13.200.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 13.207.139.205
13.204.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 13.204.33.238
IPv6 resolution
No AAAA record for capovex.com is recorded in WhisperGraph.
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
Subdomains
Mail and authentication
Nameservers
- danica.ns.cloudflare.com
- justin.ns.cloudflare.com
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
SPF policy
- include: _spf.google.com
Threat-feed evidence
History
Related pages
Pivot from capovex.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: "capovex.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.