directmatin.fr

Checked 22 October 2026, 02:34 UTC · via 8.8.8.8
!Passed with warnings
26 passed 2 warnings 0 failed 6 info

Registration

info

.fr country-code · NAMESHIELD · expires 2027-08-20

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
NAMESHIELD
Registered
2 March 2009
Last changed
23 August 2026
Expires
20 August 2027
Status
client transfer prohibited
Registry nameservers
chip.ns.cloudflare.com, tara.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-08-20 #3
    The registration is valid until 2027-08-20 (302 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

chip.ns.cloudflare.com, tara.ns.cloudflare.com

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
chip.ns.cloudflare.com, tara.ns.cloudflare.com
NS in the zone
chip.ns.cloudflare.com, tara.ns.cloudflare.com
NameserverAddressesNetwork (AS)Glue
chip.ns.cloudflare.com108.162.193.84 173.245.59.84 172.64.33.84 2606:4700:58::adf5:3b54 2803:f800:50::6ca2:c154 2a06:98c1:50::ac40:2154AS13335 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-
tara.ns.cloudflare.com173.245.58.225 172.64.32.225 108.162.192.225 2606:4700:50::adf5:3ae1 2a06:98c1:50::ac40:20e1 2803:f800:50::6ca2:c0e1AS13335 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: chip.ns.cloudflare.com, tara.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
chip.ns.cloudflare.com 108.162.193.84NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
chip.ns.cloudflare.com 173.245.59.84NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
chip.ns.cloudflare.com 172.64.33.84NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
chip.ns.cloudflare.com 2606:4700:58::adf5:3b54NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
chip.ns.cloudflare.com 2803:f800:50::6ca2:c154NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
chip.ns.cloudflare.com 2a06:98c1:50::ac40:2154NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
tara.ns.cloudflare.com 173.245.58.225NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
tara.ns.cloudflare.com 172.64.32.225NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
tara.ns.cloudflare.com 108.162.192.225NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
tara.ns.cloudflare.com 2606:4700:50::adf5:3ae1NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
tara.ns.cloudflare.com 2a06:98c1:50::ac40:20e1NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
tara.ns.cloudflare.com 2803:f800:50::6ca2:c0e1NOERROR, 15 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: chip.ns.cloudflare.com: "2026.10.2"; tara.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 2417481016 · primary chip.ns.cloudflare.com

Found

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

Serial per nameserver

NameserverSerial
chip.ns.cloudflare.com (108.162.193.84)2417481016
chip.ns.cloudflare.com (173.245.59.84)2417481016
chip.ns.cloudflare.com (172.64.33.84)2417481016
chip.ns.cloudflare.com (2606:4700:58::adf5:3b54)2417481016
chip.ns.cloudflare.com (2803:f800:50::6ca2:c154)2417481016
chip.ns.cloudflare.com (2a06:98c1:50::ac40:2154)2417481016
tara.ns.cloudflare.com (173.245.58.225)2417481016
tara.ns.cloudflare.com (172.64.32.225)2417481016
tara.ns.cloudflare.com (108.162.192.225)2417481016
tara.ns.cloudflare.com (2606:4700:50::adf5:3ae1)2417481016
tara.ns.cloudflare.com (2a06:98c1:50::ac40:20e1)2417481016
tara.ns.cloudflare.com (2803:f800:50::6ca2:c0e1)2417481016

Checks

  • ✓ Serial 2417481016 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 chip.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 2417481016 is a Unix timestamp (2046-08-10 02:30 UTC).

DNSSEC

warn

Signed, but no DS at parent

Found

Validated by resolver
no
Denial of existence
NSEC
Signatures valid until
23 October 2026

DNSKEY in the zone

Key tagRoleAlgorithm
2371KSK (257)ECDSAP256SHA256 (13)
34505ZSK (256)ECDSAP256SHA256 (13)

Checks

  • !
    Signed but not delegated securely
    The zone is signed but the parent has no DS record, so the signatures are not used. Publish the DS record at your registrar.
    #27
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Short-lived signatures (online signing) #30
    Signatures are valid for 50h0m0s and created on demand; the current one was made at 2026-10-21 01:34 UTC and expires at 2026-10-23 03:34 UTC.
  • i
    NSEC
    The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.
    #31

Records

info

5 records at the apex

Found

Read from
108.162.193.84:53
TypeValueTTL
SOAchip.ns.cloudflare.com. dns.cloudflare.com. 2417481016 10000 2400 604800 18001800
NSchip.ns.cloudflare.com.86400
NStara.ns.cloudflare.com.86400
A104.21.74.143300
A172.67.203.142300

Checks

  • ✓ TTLs within range #32
    TTLs: A 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.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • 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