1. General Results, most used to calculate the result A name "theeasyoffice.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 Good: destination is https A Good: every https has a Strict Transport Security Header 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) C Error - no preferred version www or non-www. Select one version as preferred version, then add a redirect https + not-preferred version to https + preferred version. Perhaps in your port 443 vHost something like "RewriteEngine on" + "RewriteCond %{SERVER_NAME} = example.com" + "ReWriteRule ^ https://www.example.com%{REQUEST_URI} [END,QSA,R=permanent]" (three rows, without the "). That should create a redirect https + example.com ⇒ https + www.example.com. Or switch both values to use the non-www version as your preferred version. 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. E http://theeasyoffice.com/ 52.48.226.65 https://theeasyoffice/ 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. E http://www.theeasyoffice.com/ 52.48.226.65 https://theeasyoffice/ 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. R http://theeasyoffice.com/ 52.48.226.65 https://theeasyoffice/ Redirect to not existing domain R http://www.theeasyoffice.com/ 52.48.226.65 https://theeasyoffice/ Redirect to not existing domain R http://theeasyoffice.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 52.48.226.65 https://theeasyoffice/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Redirect to not existing domain R http://www.theeasyoffice.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 52.48.226.65 https://theeasyoffice/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Redirect to not existing domain 2. Header-Checks 3. DNS- and NameServer - Checks 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: ns-1326.awsdns-37.org,ns-1906.awsdns-46.co.uk,ns-275.awsdns-34.com,ns-858.awsdns-43.net 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): 8 good Nameserver 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 https://theeasyoffice/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Fatal: Check of /.well-known/acme-challenge/random-filename redirects to not-existing domain. Creating a Letsencrypt certificate via http-01 challenge can't work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. https://theeasyoffice.com/ 52.48.226.65 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://www.theeasyoffice.com/ 52.48.226.65 Warning: https result with status 200 and size greater then 1024 Bytes without GZip found. Add GZip support so the html content is compressed. A Good: No https + http status 200 with inline CSS / JavaScript found A Good: Every https result with status 200 has a minified Html-Content with a quota lower then 110 %. A Good: Every https connection via port 443 supports the http/2 protocol via ALPN. Warning: CSS / JavaScript found without GZip support. Send these ressources with GZip. 10 external CSS / JavaScript files without GZip found - 4 with GZip, 14 complete Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 0 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 14 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 14 complete. 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 https://theeasyoffice.com/ 52.48.226.65 Strict-Transport-Security: âmax-age=15768000â Parse Error - Header can't be parsed https://www.theeasyoffice.com/ 52.48.226.65 Strict-Transport-Security: âmax-age=15768000â Parse Error - Header can't be parsed A Duration: 58544 milliseconds, 58.544 seconds