flunch.fr

Checked 22 October 2026, 03:04 UTC · via 8.8.8.8
!Passed with warnings
24 passed 2 warnings 0 failed 5 info

Registration

info

.fr country-code · GANDI · expires 2026-11-28

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
GANDI
Registered
27 March 1997
Last changed
2 November 2025
Expires
28 November 2026
Status
client transfer prohibited
Registry nameservers
ns-209-c.gandi.net, ns-211-a.gandi.net, ns-31-b.gandi.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 2026-11-28 #3
    The registration is valid until 2026-11-28 (37 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

ns-209-c.gandi.net, ns-211-a.gandi.net, ns-31-b.gandi.net

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
ns-209-c.gandi.net, ns-211-a.gandi.net, ns-31-b.gandi.net
NS in the zone
ns-209-c.gandi.net, ns-211-a.gandi.net, ns-31-b.gandi.net
NameserverAddressesNetwork (AS)Glue
ns-209-c.gandi.net217.70.187.210 2604:3400:aaac::d2AS29169 GANDI-AS - GANDI SAS, FR AS209453 GANDI-LIVEDNS - GANDI SAS, FR-
ns-211-a.gandi.net173.246.100.212 2001:4b98:aaaa::d4AS209453 GANDI-LIVEDNS - GANDI SAS, FR AS209453 GANDI-LIVEDNS - GANDI SAS, FR-
ns-31-b.gandi.net213.167.230.32 2001:4b98:aaab::20AS209453 GANDI-LIVEDNS - GANDI SAS, FR AS209453 GANDI-LIVEDNS - GANDI SAS, FR-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns-209-c.gandi.net, ns-211-a.gandi.net, ns-31-b.gandi.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 3 IPv4 /24s and 3 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS209453 (GANDI-LIVEDNS - GANDI SAS, FR): 5 addresses; AS29169 (GANDI-AS - GANDI SAS, FR): 1 address.
  • 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

pass

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns-209-c.gandi.net 217.70.187.210NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns-209-c.gandi.net 2604:3400:aaac::d2NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns-211-a.gandi.net 173.246.100.212NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns-211-a.gandi.net 2001:4b98:aaaa::d4NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns-31-b.gandi.net 213.167.230.32NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns-31-b.gandi.net 2001:4b98:aaab::20NOERROR, 3 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 6 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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ 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

info

serial 1792627200 · primary ns1.gandi.net

Found

Primary (MNAME)
ns1.gandi.net
Contact (RNAME)
hostmaster.gandi.net
Serial
1792627200
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
10800 s

Serial per nameserver

NameserverSerial
ns-209-c.gandi.net (217.70.187.210)1792627200
ns-209-c.gandi.net (2604:3400:aaac::d2)1792627200
ns-211-a.gandi.net (173.246.100.212)1792627200
ns-211-a.gandi.net (2001:4b98:aaaa::d4)1792627200
ns-31-b.gandi.net (213.167.230.32)1792627200
ns-31-b.gandi.net (2001:4b98:aaab::20)1792627200

Checks

  • ✓ Serial 1792627200 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 3h.
  • i
    Hidden master
    The primary nameserver ns1.gandi.net is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact hostmaster@gandi.net #25
    The SOA RNAME hostmaster.gandi.net means hostmaster@gandi.net.
  • ✓ Timestamp serial #26
    The serial 1792627200 is a Unix timestamp (2026-10-22 00:00 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

19 records at the apex

Found

Read from
217.70.187.210:53
TypeValueTTL
SOAns1.gandi.net. hostmaster.gandi.net. 1792627200 10800 3600 604800 1080010800
NSns-31-b.gandi.net.10800
NSns-209-c.gandi.net.10800
NSns-211-a.gandi.net.10800
A13.32.99.8060
A13.32.99.8760
A13.32.99.7160
A13.32.99.6160
MX1 aspmx.l.google.com.3600
MX10 ALT3.aspmx.l.google.com.3600
MX5 alt1.aspmx.l.google.com.3600
MX5 alt2.aspmx.l.google.com.3600
MX10 aspmx3.googlemail.com.3600
MX10 aspmx2.googlemail.com.3600
TXT"MS=ms62437832"300
TXT"google-site-verification=RDBp89Mm-C34OM5cdJDdBpxsfi70j2BLkOnVbHCcnvQ"300
TXT"v=spf1 include:_spf.google.com include:amazonses.com ip4:62.160.65.242 ip4:212.31.129.106 ip4:34.252.31.96 ip4:35.181.25.130 ip4:5.135.233.59 ip4:52.51.186.35 ip4:185.225.64.14 ip4:185.225.64.16 ip4:185.225.64.55 ip4:213.41.42.93 ~all"300
TXT"google-site-verification=LS1UpcHQilbkOj7lukb7Sfspc9gJmoq4dsRwiSiQu3I"300
TXT"MS=9D8B54345E236D46E6C847691F775E392BB6F27F"300

Checks

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