new.fr

Checked 22 October 2026, 04:31 UTC · via 8.8.8.8
✗Problems found
20 passed 4 warnings 2 failed 5 info

Registration

info

.fr country-code · KEY-SYSTEMS GmbH · expires 2027-04-14

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
KEY-SYSTEMS GmbH
Registered
7 November 2017
Last changed
7 May 2026
Expires
14 April 2027
Status
active
Registry nameservers
ns1.sedoparking.com, ns2.sedoparking.com, ns3.sedoparking.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-04-14 #3
    The registration is valid until 2027-04-14 (174 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

ns1.sedoparking.com, ns2.sedoparking.com, ns3.sedoparking.com

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
ns1.sedoparking.com, ns2.sedoparking.com, ns3.sedoparking.com
NS in the zone
ns1.sedoparking.com, ns2.sedoparking.com
NameserverAddressesNetwork (AS)Glue
ns1.sedoparking.com91.195.241.8 3.130.216.63AS47846 SEDO-AS - SEDO GmbH, DE AS16509 AMAZON-02 - Amazon.com, Inc., US-
ns2.sedoparking.com91.195.240.8 34.211.188.210AS47846 SEDO-AS - SEDO GmbH, DE AS16509 AMAZON-02 - Amazon.com, Inc., US-
ns3.sedoparking.com (parent only)64.190.63.136AS47846 SEDO-AS - SEDO GmbH, DE-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.sedoparking.com, ns2.sedoparking.com, ns3.sedoparking.com.
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only at the parent: ns3.sedoparking.com. ns1.sedoparking.com, ns2.sedoparking.com report NS ns1.sedoparking.com ns2.sedoparking.com.
    #7
  • ✓ 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 5 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS16509 (AMAZON-02 - Amazon.com, Inc., US): 2 addresses; AS47846 (SEDO-AS - SEDO GmbH, DE): 3 addresses.
  • 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

fail

4 of 5 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.sedoparking.com 91.195.241.8NOERROR, 10 ms, authoritativeOPENyes / yesrefused-
ns1.sedoparking.com 3.130.216.63NOERROR, 107 ms, authoritativenoyes / yesrefused-
ns2.sedoparking.com 91.195.240.8NOERROR, 11 ms, authoritativenoyes / yesrefused-
ns2.sedoparking.com 34.211.188.210NOERROR, 173 ms, authoritativenoyes / yesrefused-
ns3.sedoparking.com 64.190.63.136no responsenono / no--

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns3.sedoparking.com (64.190.63.136): read udp 46.225.38.91:57115->64.190.63.136:53: i/o timeout.
    #14
  • ✓ 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: ns1.sedoparking.com (91.195.241.8). 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.
  • ✓ 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 2018051601 · primary ns1.sedoparking.com

Found

Primary (MNAME)
ns1.sedoparking.com
Contact (RNAME)
hostmaster.sedo.de
Serial
2018051601
Refresh / retry
86400 s / 10800 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.sedoparking.com (91.195.241.8)2018051601
ns1.sedoparking.com (3.130.216.63)2018051601
ns2.sedoparking.com (91.195.240.8)2018051601
ns2.sedoparking.com (34.211.188.210)2018051601

Checks

  • ✓ Serial 2018051601 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1d, retry 3h, expire 7d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.sedoparking.com is one of the listed nameservers.
  • ✓ Contact hostmaster@sedo.de #25
    The SOA RNAME hostmaster.sedo.de means hostmaster@sedo.de.
  • ✓ Date-based serial #26
    The serial 2018051601 follows the YYYYMMDDnn convention (2018-05-16).

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

6 records at the apex

Found

Read from
91.195.241.8:53
TypeValueTTL
SOAns1.sedoparking.com. hostmaster.sedo.de. 2018051601 86400 10800 604800 8640086400
NSns1.sedoparking.com.86400
NSns2.sedoparking.com.86400
A64.190.63.11160
MX0 localhost.3600
TXT"v=spf1 -all"3600

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 1d; 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