vans.fr

Checked 22 October 2026, 05:40 UTC · via 8.8.8.8
!Passed with warnings
24 passed 2 warnings 0 failed 5 info

Registration

info

.fr country-code · MARKMONITOR Inc. · expires 2026-11-29

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
MARKMONITOR Inc.
Registered
12 September 2002
Last changed
24 April 2026
Expires
29 November 2026
Status
client update prohibited, client transfer prohibited, client delete prohibited
Registry nameservers
a1-250.akam.net, a12-64.akam.net, a13-67.akam.net, a2-65.akam.net, a24-64.akam.net, a5-66.akam.net
RDAP server
https://rdap.nic.fr/

Checks

  • i
    .fr is a country-code TLD (ccTLD)
    Country-code TLD: governed by its local registry under national policy, not by an ICANN contract. Registrar accreditation, dispute resolution and RDAP/WHOIS rules are set by the registry.
    #1
  • ✓ TLD delegated and signed #2
    .fr is delegated in the root zone and DNSSEC-signed.
  • ✓ Expires on 2026-11-29 #3
    The registration is valid until 2026-11-29 (38 days).
  • ✓ Transfer locked #4
    Registry status: client update prohibited, client transfer prohibited, client delete prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

a1-250.akam.net, a12-64.akam.net, a13-67.akam.net, a2-65.akam.net, a24-64.akam.net, a5-66.akam.net

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
a1-250.akam.net, a12-64.akam.net, a13-67.akam.net, a2-65.akam.net, a24-64.akam.net, a5-66.akam.net
NS in the zone
a1-250.akam.net, a12-64.akam.net, a13-67.akam.net, a2-65.akam.net, a24-64.akam.net, a5-66.akam.net
NameserverAddressesNetwork (AS)Glue
a1-250.akam.net193.108.91.250 2600:1401:2::faAS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a12-64.akam.net184.26.160.64 2600:1480:f000::40AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a13-67.akam.net2.22.230.67 2600:1480:800::43AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a2-65.akam.net95.100.174.65 2600:1480:7000::41AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a24-64.akam.net2.16.130.64 2600:1480:9800::40AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a5-66.akam.net95.100.168.66 2600:1480:b000::42AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-

Checks

  • ✓ 6 nameservers #6
    Delegated to a1-250.akam.net, a12-64.akam.net, a13-67.akam.net, a2-65.akam.net, a24-64.akam.net, a5-66.akam.net.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 6 IPv4 /24s and 6 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS21342 (AKAMAI-ASN2 - Akamai International B.V., NL): 12 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • i
    All nameserver names under .net
    All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.
    #12
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

12 of 12 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
a1-250.akam.net 193.108.91.250NOERROR, 4 ms, authoritativenoyes / yesrefused41824.6
a1-250.akam.net 2600:1401:2::faNOERROR, 3 ms, authoritativenoyes / yesrefused41824.4
a12-64.akam.net 184.26.160.64NOERROR, 4 ms, authoritativenoyes / yesrefused48878.30
a12-64.akam.net 2600:1480:f000::40NOERROR, 4 ms, authoritativenoyes / yesrefused48878.32
a13-67.akam.net 2.22.230.67NOERROR, 5 ms, authoritativenoyes / yesrefused41824.8
a13-67.akam.net 2600:1480:800::43NOERROR, 5 ms, authoritativenoyes / yesrefused41824.5
a2-65.akam.net 95.100.174.65NOERROR, 3 ms, authoritativenoyes / yesrefused48878.29
a2-65.akam.net 2600:1480:7000::41NOERROR, 4 ms, authoritativenoyes / yesrefused48878.31
a24-64.akam.net 2.16.130.64NOERROR, 5 ms, authoritativenoyes / yesrefused48878.27
a24-64.akam.net 2600:1480:9800::40NOERROR, 5 ms, authoritativenoyes / yesrefused48878.33
a5-66.akam.net 95.100.168.66NOERROR, 5 ms, authoritativenoyes / yesrefused41824.5
a5-66.akam.net 2600:1480:b000::42NOERROR, 5 ms, authoritativenoyes / yesrefused41824.10

Checks

  • ✓ All respond #14
    All 12 nameserver addresses answered.
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-250.akam.net: "41824.6"; a1-250.akam.net: "41824.4"; a12-64.akam.net: "48878.30"; a12-64.akam.net: "48878.32"; a13-67.akam.net: "41824.8"; a13-67.akam.net: "41824.5"; a2-65.akam.net: "48878.29"; a2-65.akam.net: "48878.31"; a24-64.akam.net: "48878.27"; a24-64.akam.net: "48878.33"; a5-66.akam.net: "41824.5"; a5-66.akam.net: "41824.10". Hide or replace the version string.
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✓ TCP supported #19
    All nameservers answer over TCP.
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

info

serial 2016012184 · primary ns1.vfc.com

Found

Primary (MNAME)
ns1.vfc.com
Contact (RNAME)
vfs_network_security.vfc.com
Serial
2016012184
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
900 s

Serial per nameserver

NameserverSerial
a1-250.akam.net (193.108.91.250)2016012184
a1-250.akam.net (2600:1401:2::fa)2016012184
a12-64.akam.net (184.26.160.64)2016012184
a12-64.akam.net (2600:1480:f000::40)2016012184
a13-67.akam.net (2.22.230.67)2016012184
a13-67.akam.net (2600:1480:800::43)2016012184
a2-65.akam.net (95.100.174.65)2016012184
a2-65.akam.net (2600:1480:7000::41)2016012184
a24-64.akam.net (2.16.130.64)2016012184
a24-64.akam.net (2600:1480:9800::40)2016012184
a5-66.akam.net (95.100.168.66)2016012184
a5-66.akam.net (2600:1480:b000::42)2016012184

Checks

  • ✓ Serial 2016012184 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 15m.
  • i
    Hidden master
    The primary nameserver ns1.vfc.com is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact vfs_network_security@vfc.com #25
    The SOA RNAME vfs_network_security.vfc.com means vfs_network_security@vfc.com.
  • ✓ Date-based serial #26
    The serial 2016012184 follows the YYYYMMDDnn convention (2016-01-21).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Records

info

18 records at the apex

Found

Read from
193.108.91.250:53
TypeValueTTL
SOAns1.vfc.com. vfs_network_security.vfc.com. 2016012184 10800 3600 604800 900300
NSa5-66.akam.net.300
NSa24-64.akam.net.300
NSa2-65.akam.net.300
NSa12-64.akam.net.300
NSa1-250.akam.net.300
NSa13-67.akam.net.300
A184.30.213.231800
MX5 mx2.ovh.net.28800
MX1 mx1.ovh.net.28800
TXT"_5skd3qz350w9pu070m4ctatgtzdgtz1"300
TXT"kqxrdfprxf2qkyq58ylhjfdcvh20thtd"300
TXT"qvqc40vxnk5r38mvnp6m7ty17wjr1qbj"300
TXT"facebook-domain-verification=10kcf9aac1tcpgawjkoerrcegxzo98"300
TXT"v=spf1 -all"300
TXT"_0gl17x85pj29n4vu6h9pp0i0ykvct44"300
TXT"google-site-verification=qXEggSgDhEXjCZ7LrNCDmrme0Fv3hmgEeBCV-DHutjc"300
TXT"_ydn9pyifpff2lh7vk5xgk7ttm2lz34l"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 30m, MX 8h, NS 5m. The NS TTL at the parent is 1h and in the zone 5m; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • i
    No CAA records
    Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.
    #35