doctolib.fr

Checked 22 October 2026, 02:35 UTC · via 8.8.8.8
!Passed with warnings
27 passed 2 warnings 0 failed 6 info

Registration

info

.fr country-code · CSC CORPORATE DOMAINS INC. · expires 2027-09-13

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
CSC CORPORATE DOMAINS INC.
Registered
9 July 2013
Last changed
14 September 2026
Expires
13 September 2027
Status
server update prohibited, server transfer prohibited, server delete prohibited, server recover prohibited
Registry nameservers
bob.ns.cloudflare.com, naomi.ns.cloudflare.com
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 2027-09-13 #3
    The registration is valid until 2027-09-13 (326 days).
  • ✓ Transfer locked #4
    Registry status: server update prohibited, server transfer prohibited, server delete prohibited, server recover prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

bob.ns.cloudflare.com, naomi.ns.cloudflare.com

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
bob.ns.cloudflare.com, naomi.ns.cloudflare.com
NS in the zone
bob.ns.cloudflare.com, naomi.ns.cloudflare.com
NameserverAddressesNetwork (AS)Glue
bob.ns.cloudflare.com172.64.33.104 173.245.59.104 108.162.193.104 2a06:98c1:50::ac40:2168 2606:4700:58::adf5:3b68 2803:f800:50::6ca2:c168AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US-
naomi.ns.cloudflare.com172.64.32.208 108.162.192.208 173.245.58.208 2606:4700:50::adf5:3ad0 2a06:98c1:50::ac40:20d0 2803:f800:50::6ca2:c0d0AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: bob.ns.cloudflare.com, naomi.ns.cloudflare.com.
    #6
  • ✓ 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 4 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS13335 (CLOUDFLARENET - Cloudflare, Inc., US): 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 .com
    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
bob.ns.cloudflare.com 172.64.33.104NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
bob.ns.cloudflare.com 173.245.59.104NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
bob.ns.cloudflare.com 108.162.193.104NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
bob.ns.cloudflare.com 2a06:98c1:50::ac40:2168NOERROR, 17 ms, authoritativenoyes / yesrefused2026.10.2
bob.ns.cloudflare.com 2606:4700:58::adf5:3b68NOERROR, 18 ms, authoritativenoyes / yesrefused2026.10.2
bob.ns.cloudflare.com 2803:f800:50::6ca2:c168NOERROR, 18 ms, authoritativenoyes / yesrefused2026.10.2
naomi.ns.cloudflare.com 172.64.32.208NOERROR, 13 ms, authoritativenoyes / yesrefused2026.10.2
naomi.ns.cloudflare.com 108.162.192.208NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
naomi.ns.cloudflare.com 173.245.58.208NOERROR, 13 ms, authoritativenoyes / yesrefused2026.10.2
naomi.ns.cloudflare.com 2606:4700:50::adf5:3ad0NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
naomi.ns.cloudflare.com 2a06:98c1:50::ac40:20d0NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
naomi.ns.cloudflare.com 2803:f800:50::6ca2:c0d0NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2

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: bob.ns.cloudflare.com: "2026.10.2"; naomi.ns.cloudflare.com: "2026.10.2". 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 2418003472 · primary bob.ns.cloudflare.com

Found

Primary (MNAME)
bob.ns.cloudflare.com
Contact (RNAME)
dns.cloudflare.com
Serial
2418003472
Refresh / retry
10000 s / 2400 s
Expire
604800 s
Negative TTL
1800 s

Serial per nameserver

NameserverSerial
bob.ns.cloudflare.com (172.64.33.104)2418003472
bob.ns.cloudflare.com (173.245.59.104)2418003472
bob.ns.cloudflare.com (108.162.193.104)2418003472
bob.ns.cloudflare.com (2a06:98c1:50::ac40:2168)2418003472
bob.ns.cloudflare.com (2606:4700:58::adf5:3b68)2418003472
bob.ns.cloudflare.com (2803:f800:50::6ca2:c168)2418003472
naomi.ns.cloudflare.com (172.64.32.208)2418003472
naomi.ns.cloudflare.com (108.162.192.208)2418003472
naomi.ns.cloudflare.com (173.245.58.208)2418003472
naomi.ns.cloudflare.com (2606:4700:50::adf5:3ad0)2418003472
naomi.ns.cloudflare.com (2a06:98c1:50::ac40:20d0)2418003472
naomi.ns.cloudflare.com (2803:f800:50::6ca2:c0d0)2418003472

Checks

  • ✓ Serial 2418003472 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h46m40s, retry 40m, expire 7d, negative TTL 30m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver bob.ns.cloudflare.com is one of the listed nameservers.
  • ✓ Contact dns@cloudflare.com #25
    The SOA RNAME dns.cloudflare.com means dns@cloudflare.com.
  • ✓ Timestamp serial #26
    The serial 2418003472 is a Unix timestamp (2046-08-16 03:37 UTC).

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC
Signatures valid until
23 October 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
2371ECDSAP256SHA256 (13)SHA256 08E16F75088F81A8…yes

DNSKEY in the zone

Key tagRoleAlgorithm
2371KSK (257)ECDSAP256SHA256 (13)
34505ZSK (256)ECDSAP256SHA256 (13)

Checks

  • ✓ Signed and validated #27
    The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
  • ✓ DS matches a key #28
    The DS record at the parent matches a key in the zone: key tag 2371 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Short-lived signatures (online signing) #30
    Signatures are valid for 50h0m0s and created on demand; the current one was made at 2026-10-21 01:35 UTC and expires at 2026-10-23 03:35 UTC.
  • i
    NSEC
    The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.
    #31

Records

warn

26 records at the apex

Found

Read from
172.64.33.104:53
TypeValueTTL
SOAbob.ns.cloudflare.com. dns.cloudflare.com. 2418003472 10000 2400 604800 18001800
NSbob.ns.cloudflare.com.86400
NSnaomi.ns.cloudflare.com.86400
A93.115.102.100300
AAAA2a14:7ac0::70300
MX1 aspmx.l.google.com.120
MX10 alt3.aspmx.l.google.com.120
MX10 alt4.aspmx.l.google.com.120
MX5 alt1.aspmx.l.google.com.120
MX5 alt2.aspmx.l.google.com.120
TXT"MS=ms68571408"120
TXT"Sendinblue-code:765d1b570edeb414a44195eced1dbafe"120
TXT"_gkep7ddlhxqydp8m01875j5u9p14vee"120
TXT"atlassian-domain-verification=KIPyq/2312gYkcvqtI8Twz8TRQ92quJEwM3dCZ3OFNB4O9kPzw9xVBvunLwSYSMh"120
TXT"brevo-code:96925617caa5da0d69f134979d0560a0"120
TXT"dtm-domain-verification=i7IVzxBMOGWOYVhsffs__siJs9oNxkdiHu9b-rc2Eds"120
TXT"facebook-domain-verification=o6c0o9mv5r8qix73w0kr2gobu8bec7"120
TXT"google-site-verification=32re7zAI83QQZ6RwYhwXVjWEpdHBIWuVQ5eO0X4Pqic"120
TXT"google-site-verification=3iYr341J9fZDafUlWgB0hTO64Yo0ysYAv0Ndm3b1JVY"120
TXT"google-site-verification=Av9770csh665de8NZFQQtjhv2Y-5w2UGZFE3f9CwA2I"120
TXT"google-site-verification=ST0yk9vBxcw8QyKCjjxzlGi71CvaVxWGlWzj_4DtlLY"120
TXT"google-site-verification=j2QU8_iYGz5oZdUzR3PnTwOMHUUbi4NIyCUS1abLs1g"120
TXT"google-site-verification=s3DGIXg1DhYFqdkYQRdhwip_Hcqyy8SwDXBHv_QgNjY"120
TXT"google-site-verification=ytpQIozJCrzKnkQZHhSeEmKNahAVtbvHSZUjGhNXs9s"120
TXT"v=spf1 include:_spf.google.com include:_spf.salesforce.com include:spf.sendinblue.com include:spf.flowmailer.net a:zgateway.zuora.com -all"120
TXT"y4c7hs3j7jz0l71mlp29r89hdggk7lsj"120

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: MX (2m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1h and in the zone 1d; 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