lcp.fr

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

Registration

info

.fr country-code · GANDI · expires 2027-10-13

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
GANDI
Registered
13 October 2008
Last changed
17 September 2026
Expires
13 October 2027
Status
client transfer prohibited
Registry nameservers
ns0.claranet.com, ns1.clara.net, ns2.claranet.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-13 #3
    The registration is valid until 2027-10-13 (356 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

ns0.claranet.com, ns1.clara.net, ns2.claranet.com

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
ns0.claranet.com, ns1.clara.net, ns2.claranet.com
NS in the zone
ns0.claranet.com, ns1.clara.net, ns2.claranet.com
NameserverAddressesNetwork (AS)Glue
ns0.claranet.com185.77.72.50 2001:67c:1088::50AS8426 CLARANET-AS - Claranet Limited, GB AS8426 CLARANET-AS - Claranet Limited, GB-
ns1.clara.net185.77.72.11 2001:67c:1088::11AS8426 CLARANET-AS - Claranet Limited, GB AS8426 CLARANET-AS - Claranet Limited, GB-
ns2.claranet.com195.245.201.50 2001:a88:0:fffa::50AS8426 CLARANET-AS - Claranet Limited, GB AS8426 CLARANET-AS - Claranet Limited, GB-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns0.claranet.com, ns1.clara.net, ns2.claranet.com.
  • ✓ 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 2 IPv4 /24s and 2 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS8426 (CLARANET-AS - Claranet Limited, GB): 6 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .com, .net.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns0.claranet.com 185.77.72.50NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns0.claranet.com 2001:67c:1088::50NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns1.clara.net 185.77.72.11NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns1.clara.net 2001:67c:1088::11NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns2.claranet.com 195.245.201.50NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2.claranet.com 2001:a88:0:fffa::50NOERROR, 4 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 2021020803 · primary ns0.clara.net

Found

Primary (MNAME)
ns0.clara.net
Contact (RNAME)
root.typhon.net
Serial
2021020803
Refresh / retry
21600 s / 3600 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns0.claranet.com (185.77.72.50)2021020803
ns0.claranet.com (2001:67c:1088::50)2021020803
ns1.clara.net (185.77.72.11)2021020803
ns1.clara.net (2001:67c:1088::11)2021020803
ns2.claranet.com (195.245.201.50)2021020803
ns2.claranet.com (2001:a88:0:fffa::50)2021020803

Checks

  • ✓ Serial 2021020803 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 6h, retry 1h, expire 7d, negative TTL 1d.
  • i
    Hidden master
    The primary nameserver ns0.clara.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 root@typhon.net #25
    The SOA RNAME root.typhon.net means root@typhon.net.
  • ✓ Date-based serial #26
    The serial 2021020803 follows the YYYYMMDDnn convention (2021-02-08).

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

10 records at the apex

Found

Read from
185.77.72.50:53
TypeValueTTL
SOAns0.clara.net. root.typhon.net. 2021020803 21600 3600 604800 86400600
NSns1.clara.net.600
NSns2.claranet.com.600
NSns0.claranet.com.600
A89.185.35.165120
MX50 mx2.typhon.net.600
MX10 mx1.typhon.net.600
TXT"n1nvrkdd4955tkncqv13jln7bltpj4t7"120
TXT"google-site-verification=EEdJH-T6B1UCcaE7_O6Edl8x-Hwaqe3GEWbb9XmOT4Q"120
TXT"google-site-verification=czWIxyP_kkS9gOJlo0ojYSDty7yPkdGa2SI59EWGR5Y"120

Checks

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