1. General Results, most used to calculate the result A name "todologistics.com" is domain, public suffix is "com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services" A good: All ip addresses are public addresses A good: No asked Authoritative Name Server had a timeout A https://todologistics.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de https://todologistics.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de/ 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) A http://todologistics.com/ 134.209.190.59 https://todologistics.com/ correct redirect http - https with the same domain name B https://todologistics.com/ 134.209.190.59 Missing HSTS-Header B https://www.todologistics.com/ 134.209.190.59 Missing HSTS-Header E http://www.todologistics.com/ 134.209.190.59 https://todologistics.com/ Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. 2. DNS- and NameServer - Checks X Fatal: Inconsistency 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.: ns2.digitalocean.com (173.245.59.41): Delegation: ns1.servidor365.com,ns2.servidor365.com, Zone: ns1.digitalocean.com,ns2.digitalocean.com,ns3.digitalocean.com X Fatal: Inconsistency 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.: ns2.digitalocean.com (2400:cb00:2049:1::adf5:3b29): Delegation: ns1.servidor365.com,ns2.servidor365.com, Zone: ns1.digitalocean.com,ns2.digitalocean.com,ns3.digitalocean.com X Fatal: Inconsistency 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.: ns2.servidor365.com (190.34.179.57): Delegation: ns1.servidor365.com,ns2.servidor365.com, Zone: ns1.digitalocean.com,ns2.digitalocean.com,ns3.digitalocean.com X Fatal: Inconsistency 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.: ns3.digitalocean.com (198.41.222.173): Delegation: ns1.servidor365.com,ns2.servidor365.com, Zone: ns1.digitalocean.com,ns2.digitalocean.com,ns3.digitalocean.com X Fatal: Inconsistency 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.: ns3.digitalocean.com (2400:cb00:2049:1::c629:dead): Delegation: ns1.servidor365.com,ns2.servidor365.com, Zone: ns1.digitalocean.com,ns2.digitalocean.com,ns3.digitalocean.com X Fatal: Inconsistency 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.: ns1.digitalocean.com (173.245.58.51): Delegation: ns1.servidor365.com,ns2.servidor365.com, Zone: ns1.digitalocean.com,ns2.digitalocean.com,ns3.digitalocean.com X Fatal: Inconsistency 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.: ns1.digitalocean.com (2400:cb00:2049:1::adf5:3a33): Delegation: ns1.servidor365.com,ns2.servidor365.com, Zone: ns1.digitalocean.com,ns2.digitalocean.com,ns3.digitalocean.com X Fatal: Inconsistency 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.: ns1.servidor365.com (190.34.179.56): Delegation: ns1.servidor365.com,ns2.servidor365.com, Zone: ns1.digitalocean.com,ns2.digitalocean.com,ns3.digitalocean.com A Info: Nameserver mit different domain names found. May be a problem with DNS-Updates A Good: Nameserver supports TCP connections: 8 good Nameserver A Good: Nameserver supports Echo Capitalization: 8 good Nameserver A Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver A Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 6 good Nameserver Nameserver doesn't pass all EDNS-Checks: ns1.servidor365.com: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, NO OPT100 expected, OPT100 echoed. FLAGS: ok. V1: ok. V1OP100: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expected, Version greater 0 found, NO OPT100 expected, OPT100 echoed. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns1.servidor365.com / 190.34.179.56: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, NO OPT100 expected, OPT100 echoed. FLAGS: ok. V1: ok. V1OP100: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expected, Version greater 0 found, NO OPT100 expected, OPT100 echoed. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns2.servidor365.com / 190.34.179.57: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, NO OPT100 expected, OPT100 echoed. FLAGS: ok. V1: ok. V1OP100: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expected, Version greater 0 found, NO OPT100 expected, OPT100 echoed. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok. X Fatal error: Nameservers mit different SOA Serial Numbers 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. 3. Content- and Performance-critical Checks https://todologistics.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de/ Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. A Good: Every https result with status 200 supports GZip. https://todologistics.com/ 134.209.190.59 Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header. https://todologistics.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de/ Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header. https://todologistics.com/ 134.209.190.59 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://todologistics.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de/ 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://todologistics.com/ 134.209.190.59 Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2. https://todologistics.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de/ Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2. A Good: All CSS / JavaScript files are sent with GZip. That reduces the content of the files. 10 external CSS / JavaScript files found Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 10 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 0 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 10 complete. A Good: All checked attribute values are enclosed in quotation marks (" or '). 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: 101247 milliseconds, 101.247 seconds