1. General Results, most used to calculate the result A name "rstvelosports.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://rstvelosports.com/ 142.93.155.100 https://client.codemountain.ca/ Correct redirect https to 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) B https://rstvelosports.com/ 142.93.155.100 Missing HSTS-Header B https://client.codemountain.ca/ Missing HSTS-Header B https://rstvelosports.com/ 159.203.28.87 Missing HSTS-Header B https://www.rstvelosports.com/ 142.93.155.100 Missing HSTS-Header B https://www.codemountain.ca/ Missing HSTS-Header B https://www.rstvelosports.com/ 159.203.28.87 Missing HSTS-Header 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. D http://rstvelosports.com/ 142.93.155.100 http://www.rstvelosports.com/ 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. D http://rstvelosports.com/ 159.203.28.87 http://codemountain.ca 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. D http://www.rstvelosports.com/ 159.203.28.87 http://codemountain.ca 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. D http://rstvelosports.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 142.93.155.100 http://www.rstvelosports.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 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. D http://rstvelosports.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 159.203.28.87 http://codemountain.ca 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. D http://www.rstvelosports.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 159.203.28.87 http://codemountain.ca 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. E http://codemountain.ca https://www.codemountain.ca/ 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. 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. I https://rstvelosports.com/ 159.203.28.87 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.rstvelosports.com/ 159.203.28.87 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.codemountain.ca/ Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part. I http://www.rstvelosports.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 142.93.155.100 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. K http://rstvelosports.com/ 142.93.155.100, Status 301 http://rstvelosports.com/ 159.203.28.87, Status 302 Configuration problem - different ip addresses with different status K http://www.rstvelosports.com/ 142.93.155.100, Status 200 http://www.rstvelosports.com/ 159.203.28.87, Status 302 Configuration problem - different ip addresses with different status K https://rstvelosports.com/ 142.93.155.100, Status 301 https://rstvelosports.com/ 159.203.28.87, Status 200 Configuration problem - different ip addresses with different status K https://www.rstvelosports.com/ 142.93.155.100, Status 301 https://www.rstvelosports.com/ 159.203.28.87, Status 200 Configuration problem - different ip addresses with different status K http://rstvelosports.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 142.93.155.100, Status 301 http://rstvelosports.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 159.203.28.87, Status 302 Configuration problem - different ip addresses with different status K http://www.rstvelosports.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 142.93.155.100, Status 404 http://www.rstvelosports.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 159.203.28.87, Status 302 Configuration problem - different ip addresses with different status N https://rstvelosports.com/ 142.93.155.100 https://client.codemountain.ca/ Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://rstvelosports.com/ 159.203.28.87 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://www.rstvelosports.com/ 142.93.155.100 https://client.codemountain.ca/ Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://www.rstvelosports.com/ 159.203.28.87 Error - Certificate isn't trusted, RemoteCertificateNameMismatch 2. DNS- and NameServer - Checks 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 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 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://client.codemountain.ca/ 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://rstvelosports.com/ 159.203.28.87 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.codemountain.ca/ 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.rstvelosports.com/ 159.203.28.87 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://client.codemountain.ca/ 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://rstvelosports.com/ 159.203.28.87 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.codemountain.ca/ 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.rstvelosports.com/ 159.203.28.87 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. Warning: CSS / JavaScript found without GZip support. Send these ressources with GZip. 11 external CSS / JavaScript files without GZip found - 115 with GZip, 126 complete A Good: All images with internal compression not sent via GZip. Images (.png, .jpg) are already compressed, so an additional GZip isn't helpful. 66 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. 43 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 5 with Cache-Control max-age too short (minimum 7 days), 114 with Cache-Control long enough, 162 complete. Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 18 image files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 0 with Cache-Control max-age too short (minimum 7 days), 69 with Cache-Control long enough, 87 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 http://www.rstvelosports.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 142.93.155.100 1.066 seconds Warning: 404 needs more then one second A Info: Different Server-Headers found A Duration: 199280 milliseconds, 199.280 seconds