1. General Results, most used to calculate the result A name "lorban-ftp.com" is domain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 85538 (complete: 220007) A Good: All ip addresses are public addresses Warning: Only one ip address found: lorban-ftp.com has only one ip address. Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: lorban-ftp.com has no ipv6 address. A Good: No asked Authoritative Name Server had a timeout A DNS: "Name Error" means: No www-dns-entry defined. This isn't a problem A https://lorban-ftp.com/owa/ https://lorban-ftp.com/owa/auth/logon.aspx?url=https%3a%2f%2florban-ftp.com%2fowa%2f&reason=0 Correct redirect https to https A https://lorban-ftp.com/ 185.13.213.66 https://lorban-ftp.com/owa/ Correct redirect https to https A https://185.13.213.66/owa/ https://185.13.213.66/owa/auth/logon.aspx?url=https%3a%2f%2f185.13.213.66%2fowa%2f&reason=0 Correct redirect https to https A https://185.13.213.66/ 185.13.213.66 https://185.13.213.66/owa/ Correct redirect https to https A Good: destination is https A Good - only one version with Http-Status 200 A Good: one preferred version: non-www is preferred HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List. A Good: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset) B https://lorban-ftp.com/owa/ Missing HSTS-Header B https://lorban-ftp.com/ 185.13.213.66 Missing HSTS-Header B https://lorban-ftp.com/owa/auth/logon.aspx?url=https%3a%2f%2florban-ftp.com%2fowa%2f&reason=0 Missing HSTS-Header N https://lorban-ftp.com/owa/ https://lorban-ftp.com/owa/auth/logon.aspx?url=https%3a%2f%2florban-ftp.com%2fowa%2f&reason=0 Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors N https://lorban-ftp.com/ 185.13.213.66 https://lorban-ftp.com/owa/ Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors N https://lorban-ftp.com/owa/auth/logon.aspx?url=https%3a%2f%2florban-ftp.com%2fowa%2f&reason=0 Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors N https://185.13.213.66/owa/ https://185.13.213.66/owa/auth/logon.aspx?url=https%3a%2f%2f185.13.213.66%2fowa%2f&reason=0 Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors N https://185.13.213.66/ 185.13.213.66 https://185.13.213.66/owa/ Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors N https://185.13.213.66/owa/auth/logon.aspx?url=https%3a%2f%2f185.13.213.66%2fowa%2f&reason=0 Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors N lorban-ftp.com:10000 Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors O lorban-ftp.com / 185.13.213.66 / 443 Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 7 Cipher Suites without Forward Secrecy found O lorban-ftp.com / 185.13.213.66 / 10000 Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 5 Cipher Suites without Forward Secrecy found Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain lorban-ftp.com, 1 ip addresses, 1 different http results. B No _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.lorban-ftp.com 2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete) A lorban-ftp.com X-Frame-Options Ok: Header without syntax errors found: SAMEORIGIN B Info: Header is deprecated. May not longer work in modern browsers. SAMEORIGIN. Better solution: Use a Content-Security-Policy Header with a frame-ancestors directive. DENY - use 'none', SAMEORIGIN - use 'self'. If you want to allow some domains to frame your page, add these urls. F lorban-ftp.com Content-Security-Policy Critical: Missing Header: F lorban-ftp.com X-Content-Type-Options Critical: Missing Header: F lorban-ftp.com Referrer-Policy Critical: Missing Header: F lorban-ftp.com Permissions-Policy Critical: Missing Header: 3. DNS- and NameServer - Checks A Info:: 9 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers. A Info:: 9 Queries complete, 5 with IPv6, 4 with IPv4. Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses. Ok (4 - 8):: An average of 4.5 queries per domain name server required to find all ip addresses of all name servers. A Info:: 2 different Name Servers found: ns1.lerelaisinternet.com, ns2.lerelaisinternet.com, 2 Name Servers included in Delegation: ns1.lerelaisinternet.com, ns2.lerelaisinternet.com, 2 Name Servers included in 1 Zone definitions: ns1.lerelaisinternet.com, ns2.lerelaisinternet.com, 1 Name Servers listed in SOA.Primary: ns1.lerelaisinternet.com. A Good: Only one SOA.Primary Name Server found.: ns1.lerelaisinternet.com. A Good: SOA.Primary Name Server included in the delegation set.: ns1.lerelaisinternet.com. A Good: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: ns1.lerelaisinternet.com, ns2.lerelaisinternet.com A Good: All Name Server Domain Names have a Public Suffix. A Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address. A Good: All Name Server ip addresses are public. A Good: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 2 different Name Servers found Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 2 Name Servers, 1 Top Level Domain: com Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: lerelaisinternet.com Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: FR A Info: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 194., 1 different subnets (first two Bytes): 194.206., 1 different subnets (first three Bytes): 194.206.126. X Fatal: All Name Server IPv4 addresses from the same subnet. Check https://www.iana.org/help/nameserver-requirements to learn some basics about name server configurations. If you manage these name servers, fix it. If it's your provider, change your provider.: A Good: Nameserver supports TCP connections: 2 good Nameserver A Good: Nameserver supports Echo Capitalization: 2 good Nameserver A Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver A Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver Nameserver doesn't pass all EDNS-Checks: ns1.lerelaisinternet.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result. A Good: All SOA have the same Serial Number Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries. 4. Content- and Performance-critical Checks http://lorban-ftp.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.13.213.66 Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. https://lorban-ftp.com/owa/auth/logon.aspx?url=https%3a%2f%2florban-ftp.com%2fowa%2f&reason=0 Warning: https result with status 200 and size greater then 1024 Bytes without GZip found. Add GZip support so the html content is compressed. https://185.13.213.66/owa/auth/logon.aspx?url=https%3a%2f%2f185.13.213.66%2fowa%2f&reason=0 Warning: https result with status 200 and size greater then 1024 Bytes without GZip found. Add GZip support so the html content is compressed. https://lorban-ftp.com/owa/auth/logon.aspx?url=https%3a%2f%2florban-ftp.com%2fowa%2f&reason=0 Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space. https://185.13.213.66/owa/auth/logon.aspx?url=https%3a%2f%2f185.13.213.66%2fowa%2f&reason=0 Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space. A Good: Every https connection via port 443 supports the http/2 protocol via ALPN. A Info: No img element found, no alt attribute checked A Good: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx A Duration: 305204 milliseconds, 305.204 seconds