1. General Results, most used to calculate the result A name "sriflix.xyz" is domain, public suffix is "xyz", top-level-domain-type is "generic", tld-manager is "XYZ.COM LLC" A Good: All ip addresses are public addresses Warning: Only one ip address found: sriflix.xyz has only one ip address. Warning: Only one ip address found: www.sriflix.xyz has only one ip address. Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: sriflix.xyz has no ipv6 address. Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: www.sriflix.xyz has no ipv6 address. A Good: No asked Authoritative Name Server had a timeout A Good: one preferred version: non-www is preferred A Good: every cookie sent via https is marked as secure 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):3 complete Content-Type - header (5 urls) http://sriflix.xyz/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 173.212.200.103 Url with incomplete Content-Type - header - missing charset http://www.sriflix.xyz/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 173.212.200.103 Url with incomplete Content-Type - header - missing charset B https://sriflix.xyz/ 173.212.200.103 Missing HSTS-Header B https://www.sriflix.xyz/ 173.212.200.103 Missing HSTS-Header B https://173.212.200.103/ 173.212.200.103 Missing HSTS-Header 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.sriflix.xyz/ 173.212.200.103 http://sriflix.xyz/ 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. I https://173.212.200.103/ 173.212.200.103 Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part. N https://173.212.200.103/ 173.212.200.103 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N 173.212.200.103:2083 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N 173.212.200.103:2087 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N 173.212.200.103:2096 Error - Certificate isn't trusted, RemoteCertificateNameMismatch X Fatal error: Nameserver doesn't support TCP connection: ns1.aryhost.com / 43.3.228.92: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns1.aryhost.com / 46.4.227.96: Refused X Fatal error: Nameserver doesn't support TCP connection: ns2.aryhost.com / 45.3.226.95: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns2.aryhost.com / 46.4.227.96: Refused X Fatal error: Nameserver doesn't support TCP connection: ns2.aryhost.com / 46.5.228.97: Timeout Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are different. So that domain requires Server Name Indication (SNI), so the server is able to select the correct certificate.: Domain sriflix.xyz, 1 ip addresses. Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are different. So that domain requires Server Name Indication (SNI), so the server is able to select the correct certificate.: Domain www.sriflix.xyz, 1 ip addresses. 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: ns1.aryhost.com,ns2.aryhost.com A Good: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 2 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.: 2 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: aryhost.com A Good: Name servers with different Country locations found: 2 Name Servers, 3 Countries: DE, JP, US A Info: Ipv4-Subnet-list: 7 Name Servers, 4 different subnets (first Byte): 173., 43., 45., 46., 5 different subnets (first two Bytes): 173.212., 43.3., 45.3., 46.4., 46.5., 5 different subnets (first three Bytes): 173.212.200., 43.3.228., 45.3.226., 46.4.227., 46.5.228. A Good: Name Server IPv4-addresses from different subnet found: X Nameserver Timeout checking Echo Capitalization: ns1.aryhost.com / 43.3.228.92 X Nameserver Timeout checking Echo Capitalization: ns2.aryhost.com / 45.3.226.95 X Nameserver Timeout checking Echo Capitalization: ns2.aryhost.com / 46.5.228.97 X Nameserver Timeout checking EDNS512: ns1.aryhost.com / 43.3.228.92 X Nameserver Timeout checking EDNS512: ns2.aryhost.com / 45.3.226.95 X Nameserver Timeout checking EDNS512: ns2.aryhost.com / 46.5.228.97 Nameserver doesn't pass all EDNS-Checks: ns1.aryhost.com / 43.3.228.92: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout. Nameserver doesn't pass all EDNS-Checks: ns1.aryhost.com / 46.4.227.96: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns2.aryhost.com / 45.3.226.95: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout. Nameserver doesn't pass all EDNS-Checks: ns2.aryhost.com / 46.4.227.96: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns2.aryhost.com / 46.5.228.97: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout. 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://sriflix.xyz/ 173.212.200.103 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://173.212.200.103/ 173.212.200.103 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://sriflix.xyz/ 173.212.200.103 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://173.212.200.103/ 173.212.200.103 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. 31 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. 2 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. 0 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 1 with Cache-Control max-age too short (minimum 7 days), 30 with Cache-Control long enough, 31 complete. Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 1 image files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 2 with Cache-Control max-age too short (minimum 7 days), 60 with Cache-Control long enough, 63 complete. A Good: All checked attribute values are enclosed in quotation marks (" or '). A Good: Some img-elements have a valid alt-attribute.: 63 img-elements found, 59 img-elements with correct alt-attributes (defined, not an empty value). Wrong: img-elements without alt-attribute or empty alt-attribute found. The alt-attribute ("alternative") is required and should describe the img. So Screenreader and search engines are able to use these informations.: 4 img-elements without alt-attribute, 0 img-elements with empty alt-attribute 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 A Duration: 389200 milliseconds, 389.200 seconds