jeux.fr

Checked 22 October 2026, 03:34 UTC · via 8.8.8.8
!Passed with warnings
21 passed 3 warnings 0 failed 7 info

Registration

info

.fr country-code · Hosting Concepts B.V. d/b/a Openprovider · expires 2027-10-15

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
Hosting Concepts B.V. d/b/a Openprovider
Registered
27 January 2009
Last changed
18 October 2026
Expires
15 October 2027
Status
active
Registry nameservers
max.ns.cloudflare.com, mimi.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-10-15 #3
    The registration is valid until 2027-10-15 (358 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

max.ns.cloudflare.com, mimi.ns.cloudflare.com

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
max.ns.cloudflare.com, mimi.ns.cloudflare.com
NS in the zone
max.ns.cloudflare.com, mimi.ns.cloudflare.com
NameserverAddressesNetwork (AS)Glue
max.ns.cloudflare.com108.162.193.132 173.245.59.132 172.64.33.132 2a06:98c1:50::ac40:2184 2606:4700:58::adf5:3b84 2803:f800:50::6ca2:c184AS13335 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-
mimi.ns.cloudflare.com172.64.32.203 173.245.58.203 108.162.192.203 2606:4700:50::adf5:3acb 2803:f800:50::6ca2:c0cb 2a06:98c1:50::ac40:20cbAS13335 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: max.ns.cloudflare.com, mimi.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
max.ns.cloudflare.com 108.162.193.132NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
max.ns.cloudflare.com 173.245.59.132NOERROR, 18 ms, authoritativenoyes / yesrefused2026.10.2
max.ns.cloudflare.com 172.64.33.132NOERROR, 17 ms, authoritativenoyes / yesrefused2026.10.2
max.ns.cloudflare.com 2a06:98c1:50::ac40:2184NOERROR, 17 ms, authoritativenoyes / yesrefused2026.10.2
max.ns.cloudflare.com 2606:4700:58::adf5:3b84NOERROR, 17 ms, authoritativenoyes / yesrefused2026.10.2
max.ns.cloudflare.com 2803:f800:50::6ca2:c184NOERROR, 17 ms, authoritativenoyes / yesrefused2026.10.2
mimi.ns.cloudflare.com 172.64.32.203NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
mimi.ns.cloudflare.com 173.245.58.203NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
mimi.ns.cloudflare.com 108.162.192.203NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
mimi.ns.cloudflare.com 2606:4700:50::adf5:3acbNOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
mimi.ns.cloudflare.com 2803:f800:50::6ca2:c0cbNOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
mimi.ns.cloudflare.com 2a06:98c1:50::ac40:20cbNOERROR, 16 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: max.ns.cloudflare.com: "2026.10.2"; mimi.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 2417762319 · primary max.ns.cloudflare.com

Found

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

Serial per nameserver

NameserverSerial
max.ns.cloudflare.com (108.162.193.132)2417762319
max.ns.cloudflare.com (173.245.59.132)2417762319
max.ns.cloudflare.com (172.64.33.132)2417762319
max.ns.cloudflare.com (2a06:98c1:50::ac40:2184)2417762319
max.ns.cloudflare.com (2606:4700:58::adf5:3b84)2417762319
max.ns.cloudflare.com (2803:f800:50::6ca2:c184)2417762319
mimi.ns.cloudflare.com (172.64.32.203)2417762319
mimi.ns.cloudflare.com (173.245.58.203)2417762319
mimi.ns.cloudflare.com (108.162.192.203)2417762319
mimi.ns.cloudflare.com (2606:4700:50::adf5:3acb)2417762319
mimi.ns.cloudflare.com (2803:f800:50::6ca2:c0cb)2417762319
mimi.ns.cloudflare.com (2a06:98c1:50::ac40:20cb)2417762319

Checks

  • ✓ Serial 2417762319 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 max.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 2417762319 is a Unix timestamp (2046-08-13 08:38 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

warn

9 records at the apex

Found

Read from
108.162.193.132:53
TypeValueTTL
SOAmax.ns.cloudflare.com. dns.cloudflare.com. 2417762319 10000 2400 604800 18001800
NSmax.ns.cloudflare.com.86400
NSmimi.ns.cloudflare.com.86400
A54.158.150.19816
A52.6.193.17916
A3.225.178.10216
TXT"42d0ybl9bky9g046fw3zvx35d8dlp4z2"300
TXT"google-site-verification=UikoxjqREwrXm33jY8Yid2QIj8STb3MrEWqfTwufEuA"300
TXT"v=spf1 include:spf.mandrillapp.com -all"300

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (16s). 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.
  • 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