1. General Results, most used to calculate the result A name "simboti.co.za" is domain, public suffix is "co.za", top-level-domain-type is "country-code", Country is South Africa, tld-manager is "ZA Domain Name Authority" A Good: All ip addresses are public addresses A Good: No asked Authoritative Name Server had a timeout A Good: destination is https 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://simboti.co.za/ 54.197.57.31 https://simboti.co.za/ Correct redirect http - https with the same domain name A http://www.simboti.co.za/ 54.197.57.31 https://www.simboti.co.za/ Correct redirect http - https with the same domain name B https://simboti.co.za/ 54.197.57.31 Missing HSTS-Header B https://www.simboti.co.za/ 54.197.57.31 Missing HSTS-Header B https://simboti.co.za/ 54.197.57.31 PHPSESSID=kq4do4pk8irlm08bp2c7002ctq; Path=/; Domain=simboti.co.za Cookie sent via https, but not marked as secure B https://www.simboti.co.za/ 54.197.57.31 PHPSESSID=v6618m05btlldotpoq61i9hutk; Path=/; Domain=www.simboti.co.za Cookie sent via https, but not marked as secure 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. I https://simboti.co.za/ 54.197.57.31 Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part. I https://www.simboti.co.za/ 54.197.57.31 Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part. I https://simboti.co.za/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Not used to calculate the result because it's a http - check. But listed so you should fix it. I https://www.simboti.co.za/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Not used to calculate the result because it's a http - check. But listed so you should fix it. N https://simboti.co.za/ 54.197.57.31 Error - Certificate isn't trusted, RemoteCertificateChainErrors N https://www.simboti.co.za/ 54.197.57.31 Error - Certificate isn't trusted, RemoteCertificateChainErrors N https://simboti.co.za/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Error - Certificate isn't trusted, RemoteCertificateChainErrors N https://www.simboti.co.za/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Error - Certificate isn't trusted, RemoteCertificateChainErrors 2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete) 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: cdns1.hkdns.co.za,cdns2.hkdns.co.za 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 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 A Good: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. A Good: Every https result with status 200 supports GZip. https://simboti.co.za/ 54.197.57.31 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://www.simboti.co.za/ 54.197.57.31 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://simboti.co.za/ 54.197.57.31 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://www.simboti.co.za/ 54.197.57.31 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://simboti.co.za/ 54.197.57.31 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://www.simboti.co.za/ 54.197.57.31 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. 192 external CSS / JavaScript files found A Good: All images with internal compression not sent via GZip. Images (.png, .jpg) are already compressed, so an additional GZip isn't helpful. 220 images (type image/png, image/jpg) found without additional GZip. Not required because these images are already compressed Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 102 external CSS / JavaScript files without Cache-Control-Header, 4 with Cache-Control, but no max-age, 6 with Cache-Control max-age too short (minimum 7 days), 80 with Cache-Control long enough, 192 complete. Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 234 image files without Cache-Control-Header, 26 with Cache-Control, but no max-age, 0 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 260 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://simboti.co.za/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.270 seconds Warning: 404 needs more then one second https://www.simboti.co.za/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.156 seconds Warning: 404 needs more then one second A Duration: 470716 milliseconds, 470.716 seconds