Hostname
vans.fr
Last fetched
vans.fr resolves to 104.100.51.140, announced in 104.100.48.0/20 by AKAMAI-AS - Akamai Technologies, Inc. in US. vans.fr 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.100.51.140
104.100.48.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · Santa Clara, US
- 104.102.34.162
104.102.32.0/19 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
- 184.30.213.23
184.30.208.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
- 2.16.30.190
2.16.30.0/23 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
- 23.197.132.33
23.197.128.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
- 23.212.211.148
23.212.208.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
- 23.36.236.202
23.36.232.0/21 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
- 23.37.43.106
23.37.32.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
- 23.9.117.107
23.9.112.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · Hyderabad, IN
IPv6 resolution
No AAAA record for vans.fr is recorded in WhisperGraph.
Attribution
akamai
ORIGIN_AS
WHOIS identity
- Registrar
- registrar:markmonitor inc.
- Registrant organisation
- vans sas
- Contact emails
- ccops@markmonitor.com, webmasters@double-m.net
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
Sample outbound links
Mail and authentication
Nameservers
- ns1.vfc.com
- a1-250.akam.net
- a12-64.akam.net
- a13-67.akam.net
- a2-65.akam.net
- a24-64.akam.net
- a5-66.akam.net
MX records
- mx1.ovh.net
- mx2.ovh.net
Threat-feed evidence
History
Related pages
Pivot from vans.fr 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: "vans.fr"})-[: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.