stake-official.fr

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

Registration

info

.fr country-code · Hostinger operations UAB · expires 2027-04-01

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
Hostinger operations UAB
Registered
1 April 2026
Last changed
6 April 2026
Expires
1 April 2027
Status
active
Registry nameservers
sevki.ns.cloudflare.com, virginia.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-04-01 #3
    The registration is valid until 2027-04-01 (161 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

sevki.ns.cloudflare.com, virginia.ns.cloudflare.com

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
sevki.ns.cloudflare.com, virginia.ns.cloudflare.com
NS in the zone
sevki.ns.cloudflare.com, virginia.ns.cloudflare.com
NameserverAddressesNetwork (AS)Glue
sevki.ns.cloudflare.com108.162.195.164 172.64.35.164 162.159.44.164 2606:4700:58::a29f:2ca4 2803:f800:50::6ca2:c3a4 2a06:98c1:50::ac40:23a4AS13335 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-
virginia.ns.cloudflare.com162.159.38.37 172.64.34.37 108.162.194.37 2a06:98c1:50::ac40:2225 2606:4700:50::a29f:2625 2803:f800:50::6ca2:c225AS13335 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: sevki.ns.cloudflare.com, virginia.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
sevki.ns.cloudflare.com 108.162.195.164NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
sevki.ns.cloudflare.com 172.64.35.164NOERROR, 17 ms, authoritativenoyes / yesrefused2026.10.2
sevki.ns.cloudflare.com 162.159.44.164NOERROR, 32 ms, authoritativenoyes / yesrefused2026.10.2
sevki.ns.cloudflare.com 2606:4700:58::a29f:2ca4NOERROR, 18 ms, authoritativenoyes / yesrefused2026.10.2
sevki.ns.cloudflare.com 2803:f800:50::6ca2:c3a4NOERROR, 18 ms, authoritativenoyes / yesrefused2026.10.2
sevki.ns.cloudflare.com 2a06:98c1:50::ac40:23a4NOERROR, 17 ms, authoritativenoyes / yesrefused2026.10.2
virginia.ns.cloudflare.com 162.159.38.37NOERROR, 32 ms, authoritativenoyes / yesrefused2026.10.2
virginia.ns.cloudflare.com 172.64.34.37NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
virginia.ns.cloudflare.com 108.162.194.37NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
virginia.ns.cloudflare.com 2a06:98c1:50::ac40:2225NOERROR, 18 ms, authoritativenoyes / yesrefused2026.10.2
virginia.ns.cloudflare.com 2606:4700:50::a29f:2625NOERROR, 18 ms, authoritativenoyes / yesrefused2026.10.2
virginia.ns.cloudflare.com 2803:f800:50::6ca2:c225NOERROR, 17 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: sevki.ns.cloudflare.com: "2026.10.2"; virginia.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 2417328674 · primary sevki.ns.cloudflare.com

Found

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

Serial per nameserver

NameserverSerial
sevki.ns.cloudflare.com (108.162.195.164)2417328674
sevki.ns.cloudflare.com (172.64.35.164)2417328674
sevki.ns.cloudflare.com (162.159.44.164)2417328674
sevki.ns.cloudflare.com (2606:4700:58::a29f:2ca4)2417328674
sevki.ns.cloudflare.com (2803:f800:50::6ca2:c3a4)2417328674
sevki.ns.cloudflare.com (2a06:98c1:50::ac40:23a4)2417328674
virginia.ns.cloudflare.com (162.159.38.37)2417328674
virginia.ns.cloudflare.com (172.64.34.37)2417328674
virginia.ns.cloudflare.com (108.162.194.37)2417328674
virginia.ns.cloudflare.com (2a06:98c1:50::ac40:2225)2417328674
virginia.ns.cloudflare.com (2606:4700:50::a29f:2625)2417328674
virginia.ns.cloudflare.com (2803:f800:50::6ca2:c225)2417328674

Checks

  • ✓ Serial 2417328674 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 sevki.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 2417328674 is a Unix timestamp (2046-08-08 08:11 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

8 records at the apex

Found

Read from
108.162.195.164:53
TypeValueTTL
SOAsevki.ns.cloudflare.com. dns.cloudflare.com. 2417328674 10000 2400 604800 18001800
NSsevki.ns.cloudflare.com.86400
NSvirginia.ns.cloudflare.com.86400
A172.67.144.162300
A104.21.95.108300
AAAA2606:4700:3034::6815:5f6c300
AAAA2606:4700:3033::ac43:90a2300
TXT"google-site-verification=i5ek8b4eOESvyJNh47CrEYUC6HywTCjNdRUBn4wKkzA"120

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, AAAA 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