1. General Results, most used to calculate the result A name "test.ecs.et" is subdomain, public suffix is ".et", top-level-domain is ".et", top-level-domain-type is "country-code", Country is Ethiopia, tld-manager is "Ethio telecom", num .et-domains preloaded: 6 (complete: 175327) A Good: All ip addresses are public addresses Warning: Only one ip address found: test.ecs.et has only one ip address. Warning: Only one ip address found: www.test.ecs.et 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: test.ecs.et 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.test.ecs.et has no ipv6 address. A Good: No asked Authoritative Name Server had a timeout A https://1.1.1.2/webAuth/index.htm?test.ecs.et/ https://one.one.one.one/family/ Correct redirect https to https A https://1.1.1.2/webAuth/index.htm?test.ecs.et/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de https://one.one.one.one/family/ Correct redirect https to https A Good: destination is https A Good: No cookie sent via http. A Good: every cookie sent via https is marked as secure A Good: Every cookie has a SameSite Attribute with a correct value Strict/Lax/None 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 (4 urls) https://one.one.one.one/family/ Url with incomplete Content-Type - header - missing charset B https://1.1.1.2/webAuth/index.htm?test.ecs.et/ Missing HSTS-Header B https://test.ecs.et/ 196.189.91.38 Missing HSTS-Header B https://www.test.ecs.et/ 196.189.91.38 Missing HSTS-Header B https://1.1.1.2/webAuth/index.htm?test.ecs.et/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 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://test.ecs.et/ 196.189.91.38 http://1.1.1.2/webAuth/index.htm?test.ecs.et/ 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://test.ecs.et/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 196.189.91.38 http://1.1.1.2/webAuth/index.htm?test.ecs.et/.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. I https://test.ecs.et/ 196.189.91.38 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.test.ecs.et/ 196.189.91.38 Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part. N https://test.ecs.et/ 196.189.91.38 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://www.test.ecs.et/ 196.189.91.38 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://196.189.91.38/ 196.189.91.38 Error - Certificate isn't trusted, RemoteCertificateNameMismatch 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 the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain test.ecs.et, 1 ip addresses, 1 different http results. 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 the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain www.test.ecs.et, 1 ip addresses, 1 different http results. 2. Header-Checks 3. DNS- and NameServer - Checks A Info:: 7 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers. A Info:: 7 Queries complete, 1 with IPv6, 6 with IPv4. Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses. Ok (4 - 8):: An average of 3.5 queries per domain name server required to find all ip addresses of all name servers. A Info:: 3 different Name Servers found: ns.test.ecs.et, ns1.telecom.net.et, ns2.telecom.net.et, 2 Name Servers included in Delegation: ns1.telecom.net.et, ns2.telecom.net.et, 2 Name Servers included in 2 Zone definitions: ns1.telecom.net.et, ns2.telecom.net.et, 1 Name Servers listed in SOA.Primary: ns.test.ecs.et. A Good: Only one SOA.Primary Name Server found.: ns.test.ecs.et. Error: SOA.Primary Name Server not included in the delegation set.: ns.test.ecs.et. 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.telecom.net.et, ns2.telecom.net.et A Good: All Name Server Domain Names have a Public Suffix. Error: Name Server Domain Names with Public Suffix and without ip address found.: 1 Name Servers without ipv4 and ipv6: 1 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: net.et A Good: Name Servers with different domain names found.: 2 different Domains found Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: ET A Info: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 213., 1 different subnets (first two Bytes): 213.55., 1 different subnets (first three Bytes): 213.55.64. X Fatal: All Name Server IPv4 addresses from the same subnet. Check https://www.iana.org/help/nameserver-requirements to learn some basics about name server configurations. If you manage these name servers, fix it. If it's your provider, change your provider.: A Info: Nameserver mit different domain names found. May be a problem with DNS-Updates 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 Nameserver doesn't pass all EDNS-Checks: ns.ecs.et: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result. Nameserver doesn't pass all EDNS-Checks: ns.test.ecs.et: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result. Nameserver doesn't pass all EDNS-Checks: ns.test.ecs.et: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result. 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 http://www.test.ecs.et/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 196.189.91.38 Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. A Good: Every https result with status 200 supports GZip. https://one.one.one.one/family/ 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. A Good: Every https result with status 200 has a minified Html-Content with a quota lower then 110 %. https://test.ecs.et/ 196.189.91.38 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.test.ecs.et/ 196.189.91.38 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://196.189.91.38/ 196.189.91.38 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://one.one.one.one/family/ Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 2 script elements without defer/async. A Good: All CSS / JavaScript files are sent with GZip. That reduces the content of the files. 3 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. 4 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, 3 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 3 complete. Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 21 image files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 4 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 25 complete. A Good: All checked attribute values are enclosed in quotation marks (" or '). A Good: Some img-elements have a valid alt-attribute.: 25 img-elements found, 21 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 Info: Different Server-Headers found A Duration: 655523 milliseconds, 655.523 seconds