caf.fr

Checked 22 October 2026, 02:04 UTC · via 8.8.8.8
✗Problems found
19 passed 3 warnings 2 failed 7 info

Registration

info

.fr country-code · NAMEBAY · expires 2027-02-22

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
NAMEBAY
Registered
2 April 1998
Last changed
11 February 2026
Expires
22 February 2027
Status
active
Registry nameservers
ns.caf.fr, ns1.caf.fr
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-02-22 #3
    The registration is valid until 2027-02-22 (123 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

warn

ns.caf.fr, ns1.caf.fr

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
ns.caf.fr, ns1.caf.fr
NS in the zone
ns.caf.fr, ns1.caf.fr, ns3.caf.fr
NameserverAddressesNetwork (AS)Glue
ns.caf.fr91.231.174.240AS204835 IMS3 - Caisse Nationale des Allocations Familiales (CNAF), FR91.231.174.240
ns1.caf.fr91.231.174.241AS204835 IMS3 - Caisse Nationale des Allocations Familiales (CNAF), FR91.231.174.241
ns3.caf.fr (zone only)195.138.204.240AS204835 IMS3 - Caisse Nationale des Allocations Familiales (CNAF), FR-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns.caf.fr, ns1.caf.fr.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only in the zone: ns3.caf.fr. ns.caf.fr, ns1.caf.fr, ns3.caf.fr report NS ns.caf.fr ns1.caf.fr ns3.caf.fr.
    #7
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns.caf.fr, ns1.caf.fr.
  • ✓ 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 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS204835 (IMS3 - Caisse Nationale des Allocations Familiales (CNAF), FR): 3 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 .fr
    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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

fail

3 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.caf.fr 91.231.174.240NOERROR, 46 ms, authoritativeOPENno / yesrefused-
ns1.caf.fr 91.231.174.241NOERROR, 47 ms, authoritativeOPENno / yesrefused-
ns3.caf.fr 195.138.204.240NOERROR, 20 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 3 nameserver addresses answered.
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✗
    Open recursion
    These nameservers resolve names for anyone, which makes them usable for DNS amplification attacks and cache poisoning: ns.caf.fr (91.231.174.240), ns1.caf.fr (91.231.174.241). Disable recursion on authoritative servers.
    #16
  • ✓ 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.
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns.caf.fr (91.231.174.240): dial tcp 91.231.174.240:53: i/o timeout; ns1.caf.fr (91.231.174.241): dial tcp 91.231.174.241:53: i/o timeout.
    #19
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2021092987 · primary ns.caf.fr

Found

Primary (MNAME)
ns.caf.fr
Contact (RNAME)
postmaster.caf.fr
Serial
2021092987
Refresh / retry
21600 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns.caf.fr (91.231.174.240)2021092987
ns1.caf.fr (91.231.174.241)2021092987
ns3.caf.fr (195.138.204.240)2021092987

Checks

  • ✓ Serial 2021092987 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 6h, retry 1h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.caf.fr is one of the listed nameservers.
  • ✓ Contact postmaster@caf.fr #25
    The SOA RNAME postmaster.caf.fr means postmaster@caf.fr.
  • ✓ Date-based serial #26
    The serial 2021092987 follows the YYYYMMDDnn convention (2021-09-29).

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

9 records at the apex

Found

Read from
91.231.174.240:53
TypeValueTTL
SOAns.caf.fr. postmaster.caf.fr. 2021092987 21600 3600 604800 3600300
NSns.caf.fr.300
NSns1.caf.fr.300
NSns3.caf.fr.300
A66.22.41.120300
MX10 mel2.cnaf.fr.300
MX10 mel1.cnaf.fr.300
TXT"MS=ms16169453"300
TXT"v=spf1 ip4:195.138.204.0/24 ip4:91.231.174.0/24 include:spf.protection.outlook.com ~all"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 5m, NS 5m. The NS TTL at the parent is 1h and in the zone 5m; 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