piecesauto.fr

Checked 22 October 2026, 04:47 UTC · via 8.8.8.8
!Passed with warnings
25 passed 2 warnings 0 failed 6 info

Registration

info

.fr country-code · INWX GmbH · expires 2027-05-25

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
INWX GmbH
Registered
4 May 2005
Last changed
30 May 2026
Expires
25 May 2027
Status
client transfer prohibited
Registry nameservers
amir.ns.cloudflare.com, dorthy.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-05-25 #3
    The registration is valid until 2027-05-25 (215 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

amir.ns.cloudflare.com, dorthy.ns.cloudflare.com

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
amir.ns.cloudflare.com, dorthy.ns.cloudflare.com
NS in the zone
amir.ns.cloudflare.com, dorthy.ns.cloudflare.com
NameserverAddressesNetwork (AS)Glue
amir.ns.cloudflare.com172.64.33.62 108.162.193.62 173.245.59.62 2606:4700:58::adf5:3b3e 2803:f800:50::6ca2:c13e 2a06:98c1:50::ac40:213eAS13335 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-
dorthy.ns.cloudflare.com172.64.32.249 108.162.192.249 173.245.58.249 2a06:98c1:50::ac40:20f9 2606:4700:50::adf5:3af9 2803:f800:50::6ca2:c0f9AS13335 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: amir.ns.cloudflare.com, dorthy.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
amir.ns.cloudflare.com 172.64.33.62NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
amir.ns.cloudflare.com 108.162.193.62NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
amir.ns.cloudflare.com 173.245.59.62NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
amir.ns.cloudflare.com 2606:4700:58::adf5:3b3eNOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
amir.ns.cloudflare.com 2803:f800:50::6ca2:c13eNOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
amir.ns.cloudflare.com 2a06:98c1:50::ac40:213eNOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
dorthy.ns.cloudflare.com 172.64.32.249NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
dorthy.ns.cloudflare.com 108.162.192.249NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
dorthy.ns.cloudflare.com 173.245.58.249NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
dorthy.ns.cloudflare.com 2a06:98c1:50::ac40:20f9NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
dorthy.ns.cloudflare.com 2606:4700:50::adf5:3af9NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
dorthy.ns.cloudflare.com 2803:f800:50::6ca2:c0f9NOERROR, 14 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: amir.ns.cloudflare.com: "2026.10.2"; dorthy.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 2417461281 · primary amir.ns.cloudflare.com

Found

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

Serial per nameserver

NameserverSerial
amir.ns.cloudflare.com (172.64.33.62)2417461281
amir.ns.cloudflare.com (108.162.193.62)2417461281
amir.ns.cloudflare.com (173.245.59.62)2417461281
amir.ns.cloudflare.com (2606:4700:58::adf5:3b3e)2417461281
amir.ns.cloudflare.com (2803:f800:50::6ca2:c13e)2417461281
amir.ns.cloudflare.com (2a06:98c1:50::ac40:213e)2417461281
dorthy.ns.cloudflare.com (172.64.32.249)2417461281
dorthy.ns.cloudflare.com (108.162.192.249)2417461281
dorthy.ns.cloudflare.com (173.245.58.249)2417461281
dorthy.ns.cloudflare.com (2a06:98c1:50::ac40:20f9)2417461281
dorthy.ns.cloudflare.com (2606:4700:50::adf5:3af9)2417461281
dorthy.ns.cloudflare.com (2803:f800:50::6ca2:c0f9)2417461281

Checks

  • ✓ Serial 2417461281 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 amir.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 2417461281 is a Unix timestamp (2046-08-09 21:01 UTC).

DNSSEC

warn

Signed, but no DS at parent

Found

Validated by resolver
no
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 03:47 UTC and expires at 2026-10-23 05:47 UTC.

Records

info

17 records at the apex

Found

Read from
172.64.33.62:53
TypeValueTTL
SOAamir.ns.cloudflare.com. dns.cloudflare.com. 2417461281 10000 2400 604800 18001800
NSamir.ns.cloudflare.com.86400
NSdorthy.ns.cloudflare.com.86400
A172.64.152.109300
A104.18.35.147300
AAAA2606:4700:4409::ac40:986d300
AAAA2606:4700:440c::6812:2393300
MX10 mailstream-central.mxrecord.mx.300
MX20 mailstream-east.mxrecord.io.300
MX20 mailstream-west.mxrecord.io.300
MX5 mailstream-eu1.mxrecord.io.300
TXT"facebook-domain-verification=ltvcks3siovy8v1l3s7vxnsvhossg9"300
TXT"google-site-verification=HeSiTJwIzTDzaE2zE7h0Slh8HUcAqtf2ToH6Q-HTC2Y"300
TXT"google-site-verification=bliDkmvILf1OZjRIyEwqa4PpZcrdBbudYt09-_LJucs"300
TXT"google-site-verification=ryxuuJc2oeW7qioEZaWJ1XLjloH4sgjYV0v_koDa604"300
TXT"v=spf1 include:autodoc.dev include:mail.zendesk.com include:_spf.newsautodoc.com ~all"300
TXT"yandex-verification: 34ff2ec26d7f7c84"300

Checks

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