Hostname
ves.com
Last fetched
ves.com resolves to 104.18.24.90, announced in 104.18.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. ves.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.18.24.90
104.18.16.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.18.25.90
104.18.16.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- on behalf of ves.com owner
- Contact emails
- 251800@privacy-link.com, 13e6175c-3baa-45db-a5bc-433ea9bc83e9@identity-protect.org, 30851671-e00f-4d8f-bafd-7ee55d481f5e@identity-protect.org, 37de3506-d2b2-4642-a320-37b1266da7d4@identity-protect.org, 77f73610-9aab-4685-ac75-0d63a638d62b@identity-protect.org, 7ac91825-d21c-483b-ac6e-695670f13b16@identity-protect.org, b609a332-11cb-40a8-b21d-d79c911c8217@identity-protect.org, d8b6d849-0ad9-4cd9-953e-8083a2a7816f@identity-protect.org, owner-11045124@ves.com.whoisprivacyservice.org, owner-3113218@ves.com.whoisprivacyservice.org, owner-8778836@ves.com.whoisprivacyservice.org
Subdomains
Showing 12 of 23. View all subdomains →
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- art.ns.cloudflare.com
- sharon.ns.cloudflare.com
MX records
- mx1.hc4848-77.iphmx.com
- mx2.hc4848-77.iphmx.com
SPF policy
- ip: 20.40.137.116/30
- ip: 20.40.137.120/29
- ip: 4.53.13.162/32
- ip: 192.58.198.162/32
- ip: 67.20.178.231/32
- ip: 192.48.98.254/32
- include: _spf.atoracle.com
- include: _spf.maximus.com
- include: spf.protection.outlook.com
- include: _spf.q4press.com
Threat-feed evidence
History
Related pages
Pivot from ves.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: "ves.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.