bitdefender.fr

Checked 22 October 2026, 01:57 UTC · via 8.8.8.8
!Passed with warnings
24 passed 3 warnings 0 failed 4 info

Registration

info

.fr country-code · EURODNS S.A. · expires 2029-10-19

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
EURODNS S.A.
Registered
7 October 2003
Last changed
1 September 2026
Expires
19 October 2029
Status
active
Registry nameservers
a1-39.akam.net, a10-64.akam.net, a20-66.akam.net, a3-65.akam.net, a6-65.akam.net, a9-64.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 2029-10-19 #3
    The registration is valid until 2029-10-19 (1093 days).
  • i
    No transfer lock
    The domain has no transfer lock (status: active). A registrar lock protects against unauthorized transfers.
    #4
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

a1-39.akam.net, a10-64.akam.net, a20-66.akam.net, a3-65.akam.net, a6-65.akam.net, a9-64.akam.net

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
a1-39.akam.net, a10-64.akam.net, a20-66.akam.net, a3-65.akam.net, a6-65.akam.net, a9-64.akam.net
NS in the zone
a1-39.akam.net, a10-64.akam.net, a20-66.akam.net, a3-65.akam.net, a6-65.akam.net, a9-64.akam.net
NameserverAddressesNetwork (AS)Glue
a1-39.akam.net193.108.91.39 2600:1401:2::27AS20940 AKAMAI-ASN1 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a10-64.akam.net96.7.50.64 2600:1480:d000::40AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a20-66.akam.net95.100.175.66 2a02:26f0:67::42AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a3-65.akam.net96.7.49.65 2600:1408:1c::41AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a6-65.akam.net23.211.133.65 2600:1401:1::41AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a9-64.akam.net184.85.248.64 2a02:26f0:117::40AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-

Checks

  • ✓ 6 nameservers #6
    Delegated to a1-39.akam.net, a10-64.akam.net, a20-66.akam.net, a3-65.akam.net, a6-65.akam.net, a9-64.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.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS20940 (AKAMAI-ASN1 - Akamai International B.V., NL): 1 address; AS21342 (AKAMAI-ASN2 - Akamai International B.V., NL): 11 addresses.
  • 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-39.akam.net 193.108.91.39NOERROR, 5 ms, authoritativenoyes / yesrefused41824.5
a1-39.akam.net 2600:1401:2::27NOERROR, 5 ms, authoritativenoyes / yesrefused41824.11
a10-64.akam.net 96.7.50.64NOERROR, 3 ms, authoritativenoyes / yesrefused48878.26
a10-64.akam.net 2600:1480:d000::40NOERROR, 4 ms, authoritativenoyes / yesrefused48878.26
a20-66.akam.net 95.100.175.66NOERROR, 4 ms, authoritativenoyes / yesrefused48878.29
a20-66.akam.net 2a02:26f0:67::42NOERROR, 3 ms, authoritativenoyes / yesrefused48878.26
a3-65.akam.net 96.7.49.65NOERROR, 3 ms, authoritativenoyes / yesrefused41824.5
a3-65.akam.net 2600:1408:1c::41NOERROR, 5 ms, authoritativenoyes / yesrefused41824.11
a6-65.akam.net 23.211.133.65NOERROR, 4 ms, authoritativenoyes / yesrefused48878.31
a6-65.akam.net 2600:1401:1::41NOERROR, 4 ms, authoritativenoyes / yesrefused48878.32
a9-64.akam.net 184.85.248.64NOERROR, 4 ms, authoritativenoyes / yesrefused41824.8
a9-64.akam.net 2a02:26f0:117::40NOERROR, 4 ms, authoritativenoyes / yesrefused41824.7

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-39.akam.net: "41824.5"; a1-39.akam.net: "41824.11"; a10-64.akam.net: "48878.26"; a20-66.akam.net: "48878.29"; a20-66.akam.net: "48878.26"; a3-65.akam.net: "41824.5"; a3-65.akam.net: "41824.11"; a6-65.akam.net: "48878.31"; a6-65.akam.net: "48878.32"; a9-64.akam.net: "41824.8"; a9-64.akam.net: "41824.7". 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

pass

serial 2026062903 · primary a1-39.akam.net

Found

Primary (MNAME)
a1-39.akam.net
Contact (RNAME)
tech-admin.bitdefender.com
Serial
2026062903
Refresh / retry
3600 s / 600 s
Expire
604800 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
a1-39.akam.net (193.108.91.39)2026062903
a1-39.akam.net (2600:1401:2::27)2026062903
a10-64.akam.net (96.7.50.64)2026062903
a10-64.akam.net (2600:1480:d000::40)2026062903
a20-66.akam.net (95.100.175.66)2026062903
a20-66.akam.net (2a02:26f0:67::42)2026062903
a3-65.akam.net (96.7.49.65)2026062903
a3-65.akam.net (2600:1408:1c::41)2026062903
a6-65.akam.net (23.211.133.65)2026062903
a6-65.akam.net (2600:1401:1::41)2026062903
a9-64.akam.net (184.85.248.64)2026062903
a9-64.akam.net (2a02:26f0:117::40)2026062903

Checks

  • ✓ Serial 2026062903 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 10m, expire 7d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver a1-39.akam.net is one of the listed nameservers.
  • ✓ Contact tech-admin@bitdefender.com #25
    The SOA RNAME tech-admin.bitdefender.com means tech-admin@bitdefender.com.
  • ✓ Date-based serial #26
    The serial 2026062903 follows the YYYYMMDDnn convention (2026-06-29).

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

warn

19 records at the apex

Found

Read from
193.108.91.39:53
TypeValueTTL
SOAa1-39.akam.net. tech-admin.bitdefender.com. 2026062903 3600 600 604800 30086400
NSa1-39.akam.net.900
NSa3-65.akam.net.900
NSa6-65.akam.net.900
NSa20-66.akam.net.900
NSa9-64.akam.net.900
NSa10-64.akam.net.900
A104.18.34.23060
A172.64.153.2660
AAAA2606:4700:4400::6812:22e660
AAAA2606:4700:4400::ac40:991a60
MX10 mx01.bitdefender.com.900
MX10 mx02.bitdefender.com.900
TXT"MS=BE03A44FEAE107831923B153715225E195F555A4"900
TXT"MS=ms88400843"900
TXT"google-site-verification=aGFS9l55daI6I8Wr7_HNXxrkaEsx322HwCA1VU3B7Rc"900
TXT"v=spf1 include:spf.protection.outlook.com include:spf.bitdefender.com include:_spf.salesforce.com include:spf.mandrillapp.com include:_spf.atlassian.net include:spf.mindmatrix.net include:341979.spf06.hubspotemail.net -all"900
TXT"atlassian-domain-verification=34BCGNE4goU2sS7B2H+sTVbt/m0DlOnbHn3+2vC9+ZdNW1QOnvvs8QysSIFKd8Wn"900
TXT"adobe-idp-site-verification=25991c04-c8f2-4fa8-a299-642b609565fc"900

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), AAAA (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1h and in the zone 15m; resolvers may use either.
    #32
  • ✓ 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