sagessesante.fr

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

Registration

info

.fr country-code · Realtime Register B.V. · expires 2026-12-01

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
Realtime Register B.V.
Registered
1 December 2017
Last changed
3 December 2025
Expires
1 December 2026
Status
active
Registry nameservers
jill.ns.cloudflare.com, phil.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 2026-12-01 #3
    The registration is valid until 2026-12-01 (40 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

jill.ns.cloudflare.com, phil.ns.cloudflare.com

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
jill.ns.cloudflare.com, phil.ns.cloudflare.com
NS in the zone
jill.ns.cloudflare.com, phil.ns.cloudflare.com
NameserverAddressesNetwork (AS)Glue
jill.ns.cloudflare.com172.64.32.122 108.162.192.122 173.245.58.122 2606:4700:50::adf5:3a7a 2a06:98c1:50::ac40:207a 2803:f800:50::6ca2:c07aAS13335 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-
phil.ns.cloudflare.com172.64.33.137 173.245.59.137 108.162.193.137 2606:4700:58::adf5:3b89 2803:f800:50::6ca2:c189 2a06:98c1:50::ac40:2189AS13335 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: jill.ns.cloudflare.com, phil.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
jill.ns.cloudflare.com 172.64.32.122NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
jill.ns.cloudflare.com 108.162.192.122NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
jill.ns.cloudflare.com 173.245.58.122NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
jill.ns.cloudflare.com 2606:4700:50::adf5:3a7aNOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
jill.ns.cloudflare.com 2a06:98c1:50::ac40:207aNOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
jill.ns.cloudflare.com 2803:f800:50::6ca2:c07aNOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
phil.ns.cloudflare.com 172.64.33.137NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
phil.ns.cloudflare.com 173.245.59.137NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
phil.ns.cloudflare.com 108.162.193.137NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
phil.ns.cloudflare.com 2606:4700:58::adf5:3b89NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
phil.ns.cloudflare.com 2803:f800:50::6ca2:c189NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
phil.ns.cloudflare.com 2a06:98c1:50::ac40:2189NOERROR, 15 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: jill.ns.cloudflare.com: "2026.10.2"; phil.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 2416047365 · primary jill.ns.cloudflare.com

Found

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

Serial per nameserver

NameserverSerial
jill.ns.cloudflare.com (172.64.32.122)2416047365
jill.ns.cloudflare.com (108.162.192.122)2416047365
jill.ns.cloudflare.com (173.245.58.122)2416047365
jill.ns.cloudflare.com (2606:4700:50::adf5:3a7a)2416047365
jill.ns.cloudflare.com (2a06:98c1:50::ac40:207a)2416047365
jill.ns.cloudflare.com (2803:f800:50::6ca2:c07a)2416047365
phil.ns.cloudflare.com (172.64.33.137)2416047365
phil.ns.cloudflare.com (173.245.59.137)2416047365
phil.ns.cloudflare.com (108.162.193.137)2416047365
phil.ns.cloudflare.com (2606:4700:58::adf5:3b89)2416047365
phil.ns.cloudflare.com (2803:f800:50::6ca2:c189)2416047365
phil.ns.cloudflare.com (2a06:98c1:50::ac40:2189)2416047365

Checks

  • ✓ Serial 2416047365 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 jill.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 2416047365 is a Unix timestamp (2046-07-24 12:16 UTC).

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

11 records at the apex

Found

Read from
172.64.32.122:53
TypeValueTTL
SOAjill.ns.cloudflare.com. dns.cloudflare.com. 2416047365 10000 2400 604800 18001800
NSjill.ns.cloudflare.com.86400
NSphil.ns.cloudflare.com.86400
A172.67.220.80300
A104.21.94.61300
AAAA2606:4700:3035::6815:5e3d300
AAAA2606:4700:3032::ac43:dc50300
MX10 mail.sagessesante.fr.300
TXT"facebook-domain-verification=0xoynqkxgy2x718nicctsgi6dosa23"300
TXT"google-site-verification=vbQj6P1p4cpGLxAfUNKcVp0m6EJZ0FRy4mgq2g_LlHc"300
TXT"v=spf1 ip4:157.97.170.23 include:_spf.transip.email include:emsd1.com include:_spf.paypro.nl include:mailgun.org -all"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, AAAA 5m, MX 5m, NS 1d. The NS TTL at the parent is 1h and in the zone 1d; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • 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