1. General Results, most used to calculate the result A name "essa.website" is domain, public suffix is "website", top-level-domain-type is "generic", tld-manager is "DotWebsite Inc." A good: All ip addresses are public addresses A good: No asked Authoritative Name Server had a timeout A good: one preferred version: non-www is preferred A good: every https has a Strict Transport Security Header A good: HSTS max-age is long enough, 31536000 seconds = 365 days 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: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):2 complete Content-Type - header (4 urls) http://essa.website/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.92.150.182 Url with incomplete Content-Type - header - missing charset http://www.essa.website/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.92.150.182 Url with incomplete Content-Type - header - missing charset C Error - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200. D http://www.essa.website/ 185.92.150.182 http://essa.website/ Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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. H Fatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. 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. N essa.website:8083 Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors N www.essa.website:8083 Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors N 185.92.150.182:8083 Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors 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.zomro.ru (190.115.18.100): Delegation: ns1.zomro.net,ns2.zomro.ru,ns3.zomro.com, Zone: ns1.zomro.net,ns2.zomro.ru,ns3.zomro.com,ns4.zomro.su 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.zomro.com (87.98.180.6): Delegation: ns1.zomro.net,ns2.zomro.ru,ns3.zomro.com, Zone: ns1.zomro.net,ns2.zomro.ru,ns3.zomro.com,ns4.zomro.su 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.: ns4.zomro.su (116.202.0.200): Delegation: ns1.zomro.net,ns2.zomro.ru,ns3.zomro.com, Zone: ns1.zomro.net,ns2.zomro.ru,ns3.zomro.com,ns4.zomro.su 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.zomro.net (212.8.245.252): Delegation: ns1.zomro.net,ns2.zomro.ru,ns3.zomro.com, Zone: ns1.zomro.net,ns2.zomro.ru,ns3.zomro.com,ns4.zomro.su A Good: Nameserver supports TCP connections: 4 good Nameserver A Good: Nameserver supports Echo Capitalization: 4 good Nameserver A Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver A Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver Nameserver doesn't pass all EDNS-Checks: d.nic.website: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (hivecast-2-defra.as15135.net Radix-D). COOKIE: fatal timeout. CLIENTSUBNET: ok. 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. 3. Content- and Performance-critical Checks A http://essa.website/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.92.150.182 Good: Acme-Check - Answer looks like a correct keyAuthorization - String: Filename + "." + base64url(Thumbprint(accountKey)). So creating a Letsencrypt certificate using that integrated solution should work. Don't use another client (like Certbot). Don't mix integrated solutions with own ACME-clients, that may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. A http://www.essa.website/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.92.150.182 Good: Acme-Check - Answer looks like a correct keyAuthorization - String: Filename + "." + base64url(Thumbprint(accountKey)). So creating a Letsencrypt certificate using that integrated solution should work. Don't use another client (like Certbot). Don't mix integrated solutions with own ACME-clients, that may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. A Good: Every https result with status 200 supports GZip. https://essa.website/ 185.92.150.182 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://essa.website/ 185.92.150.182 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 Good: All CSS / JavaScript files are sent with GZip. That reduces the content of the files. 5 external CSS / JavaScript files found A Good: All CSS / JavaScript files are sent with a long Cache-Control header (minimum 7 days). So the browser can re-use these files, no download is required. 5 external CSS / JavaScript files with long Cache-Control max-age found 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 http://essa.website/ 185.92.150.182 Warning: HSTS header sent via http has no effect http://www.essa.website/ 185.92.150.182 Warning: HSTS header sent via http has no effect A Duration: 65800 milliseconds, 65.800 seconds