1. General Results, most used to calculate the result A name "sawaugust.com" is domain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 63591 (complete: 175327) A good: All ip addresses are public addresses A Good: Minimal 2 ip addresses per domain name found: sawaugust.com has 8 different ip addresses (authoritative). A Good: Minimal 2 ip addresses per domain name found: www.sawaugust.com has 2 different ip addresses (authoritative). A Good: Ipv4 and Ipv6 addresses per domain name found: sawaugust.com has 4 ipv4, 4 ipv6 addresses A Good: Ipv4 and Ipv6 addresses per domain name found: www.sawaugust.com has 1 ipv4, 1 ipv6 addresses A good: No asked Authoritative Name Server had a timeout A good: destination is https A good - only one version with Http-Status 200 A good: one preferred version: www is preferred A Good: No cookie sent via http. 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://www.sawaugust.com/ 142.250.179.179 https://www.sawaugust.com/ correct redirect http - https with the same domain name A http://www.sawaugust.com/ 142.251.36.19 https://www.sawaugust.com/ correct redirect http - https with the same domain name A http://www.sawaugust.com/ 2a00:1450:400e:802::2013 https://www.sawaugust.com/ correct redirect http - https with the same domain name B https://sawaugust.com/ 216.239.32.21 Missing HSTS-Header B https://sawaugust.com/ 216.239.34.21 Missing HSTS-Header B https://sawaugust.com/ 216.239.36.21 Missing HSTS-Header B https://sawaugust.com/ 216.239.38.21 Missing HSTS-Header B https://sawaugust.com/ 2001:4860:4802:32::15 Missing HSTS-Header B https://sawaugust.com/ 2001:4860:4802:34::15 Missing HSTS-Header B https://sawaugust.com/ 2001:4860:4802:36::15 Missing HSTS-Header B https://sawaugust.com/ 2001:4860:4802:38::15 Missing HSTS-Header B https://www.sawaugust.com/ 142.250.179.179 Missing HSTS-Header B https://www.sawaugust.com/ 142.251.36.19 Missing HSTS-Header B https://www.sawaugust.com/ 2a00:1450:400e:802::2013 Missing HSTS-Header B https://www.sawaugust.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Missing HSTS-Header D http://sawaugust.com/ 216.239.32.21 http://www.sawaugust.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://sawaugust.com/ 216.239.34.21 http://www.sawaugust.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://sawaugust.com/ 216.239.36.21 http://www.sawaugust.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://sawaugust.com/ 216.239.38.21 http://www.sawaugust.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://sawaugust.com/ 2001:4860:4802:32::15 http://www.sawaugust.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://sawaugust.com/ 2001:4860:4802:34::15 http://www.sawaugust.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://sawaugust.com/ 2001:4860:4802:36::15 http://www.sawaugust.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://sawaugust.com/ 2001:4860:4802:38::15 http://www.sawaugust.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://sawaugust.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 216.239.32.21 http://www.sawaugust.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://sawaugust.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 216.239.34.21 http://www.sawaugust.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://sawaugust.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 216.239.36.21 http://www.sawaugust.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://sawaugust.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 216.239.38.21 http://www.sawaugust.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://sawaugust.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:4860:4802:32::15 http://www.sawaugust.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://sawaugust.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:4860:4802:34::15 http://www.sawaugust.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://sawaugust.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:4860:4802:36::15 http://www.sawaugust.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://sawaugust.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:4860:4802:38::15 http://www.sawaugust.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. P https://216.239.32.21/ 216.239.32.21 Error creating a TLS-Connection: No more details available. P https://216.239.34.21/ 216.239.34.21 Error creating a TLS-Connection: No more details available. P https://216.239.36.21/ 216.239.36.21 Error creating a TLS-Connection: No more details available. P https://216.239.38.21/ 216.239.38.21 Error creating a TLS-Connection: No more details available. P https://[2001:4860:4802:0032:0000:0000:0000:0015]/ 2001:4860:4802:32::15 Error creating a TLS-Connection: No more details available. P https://[2001:4860:4802:0034:0000:0000:0000:0015]/ 2001:4860:4802:34::15 Error creating a TLS-Connection: No more details available. P https://[2001:4860:4802:0036:0000:0000:0000:0015]/ 2001:4860:4802:36::15 Error creating a TLS-Connection: No more details available. P https://[2001:4860:4802:0038:0000:0000:0000:0015]/ 2001:4860:4802:38::15 Error creating a TLS-Connection: No more details available. P https://142.250.179.179/ 142.250.179.179 Error creating a TLS-Connection: No more details available. P https://142.251.36.19/ 142.251.36.19 Error creating a TLS-Connection: No more details available. P https://[2a00:1450:400e:0802:0000:0000:0000:2013]/ 2a00:1450:400e:802::2013 Error creating a TLS-Connection: No more details available. A Good: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain sawaugust.com, 8 ip addresses. A Good: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain www.sawaugust.com, 2 ip addresses. Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain sawaugust.com, 8 ip addresses. Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain www.sawaugust.com, 2 ip addresses. 2. DNS- and NameServer - Checks A Info:: 13 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers. A Info:: 13 Queries complete, 13 with IPv6, 0 with IPv4. A Good: All DNS Queries done via IPv6. Ok (4 - 8):: An average of 3.3 queries per domain name server required to find all ip addresses of all name servers. A Info:: 4 different Name Servers found: ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com, 4 Name Servers included in Delegation: ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com, 4 Name Servers included in 1 Zone definitions: ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com, 1 Name Servers listed in SOA.Primary: ns-cloud-d1.googledomains.com. A Good: Only one SOA.Primary Name Server found.: ns-cloud-d1.googledomains.com. A Good: SOA.Primary Name Server included in the delegation set.: ns-cloud-d1.googledomains.com. 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-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com A Good: All Name Server Domain Names have a Public Suffix. A Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address. A Good: All Name Server ip addresses are public. A Good: Minimal 2 different name servers (public suffix and public ip address) found: 4 different Name Servers found Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 4 Name Servers, 1 Top Level Domain: com Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: googledomains.com Warning: All Name Servers from the same Country / IP location.: 4 Name Servers, 1 Countries: US A A Info: IPv6-Subnet-list: 4 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:4860:, 1 different subnets (first three blocks): 2001:4860:4802:, 4 different subnets (first four blocks): 2001:4860:4802:0032:, 2001:4860:4802:0034:, 2001:4860:4802:0036:, 2001:4860:4802:0038: A Good: Name Server IPv6 addresses from different subnets found. 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: All SOA have the same Serial Number A good: CAA entries found, creating certificate is limited: pki.goog is allowed to create certificates 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://www.sawaugust.com/ 142.250.179.179 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.sawaugust.com/ 142.251.36.19 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.sawaugust.com/ 2a00:1450:400e:802::2013 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.sawaugust.com/ 142.250.179.179 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.sawaugust.com/ 142.251.36.19 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.sawaugust.com/ 2a00:1450:400e:802::2013 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 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 https://www.sawaugust.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.593 seconds Warning: 404 needs more then one second A Info: Different Server-Headers found A Duration: 190063 milliseconds, 190.063 seconds