1. General Results, most used to calculate the result A name "tresacolor.com.ar" is domain, public suffix is ".com.ar", top-level-domain is ".ar", top-level-domain-type is "country-code", Country is Argentina, tld-manager is "Presidencia de la Nación – Secretaría Legal y Técnica", num .ar-domains preloaded: 200 (complete: 216710) A Good: All ip addresses are public addresses A Good: No asked Authoritative Name Server had a timeout A Good: destination is https 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: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):4 complete Content-Type - header (5 urls) https://200.58.112.226/ 200.58.112.226 Url with incomplete Content-Type - header - missing charset A http://tresacolor.com.ar/ 200.58.112.226 https://tresacolor.com.ar/ Correct redirect http - https with the same domain name A http://www.tresacolor.com.ar/ 200.58.112.226 https://www.tresacolor.com.ar/ Correct redirect http - https with the same domain name B https://tresacolor.com.ar/ 200.58.112.226 Missing HSTS-Header B https://www.tresacolor.com.ar/ 200.58.112.226 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. I https://www.tresacolor.com.ar/ 200.58.112.226 Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part. N https://tresacolor.com.ar/ 200.58.112.226 Error - Certificate isn't trusted, RemoteCertificateChainErrors N https://www.tresacolor.com.ar/ 200.58.112.226 Error - Certificate isn't trusted, RemoteCertificateChainErrors N https://200.58.112.226/ 200.58.112.226 Error - Certificate isn't trusted, RemoteCertificateNameMismatch X Fatal error: Nameserver doesn't support TCP connection: a.dns.ar / 2801:140::10: Timeout B No _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.tresacolor.com.ar 2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete) F tresacolor.com.ar 200.58.112.226 Content-Security-Policy Critical: Missing Header: F tresacolor.com.ar 200.58.112.226 X-Content-Type-Options Critical: Missing Header: F tresacolor.com.ar 200.58.112.226 Referrer-Policy Critical: Missing Header: F tresacolor.com.ar 200.58.112.226 Permissions-Policy Critical: Missing Header: F www.tresacolor.com.ar 200.58.112.226 Content-Security-Policy Critical: Missing Header: F www.tresacolor.com.ar 200.58.112.226 X-Content-Type-Options Critical: Missing Header: F www.tresacolor.com.ar 200.58.112.226 Referrer-Policy Critical: Missing Header: F www.tresacolor.com.ar 200.58.112.226 Permissions-Policy Critical: Missing Header: 3. DNS- and NameServer - Checks A Info:: 1 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 0 Name Servers. A Info:: 1 Queries complete, 1 with IPv6, 0 with IPv4. A Good: All DNS Queries done via IPv6. A Info:: 5 different Name Servers found: a.dns.ar, b.dns.ar, c.dns.ar, e.dns.ar, f.dns.ar, 5 Name Servers included in Delegation: a.dns.ar, b.dns.ar, c.dns.ar, e.dns.ar, f.dns.ar, 5 Name Servers included in 1 Zone definitions: a.dns.ar, b.dns.ar, c.dns.ar, e.dns.ar, f.dns.ar, 1 Name Servers listed in SOA.Primary: c.dns.ar. A Good: Only one SOA.Primary Name Server found.: c.dns.ar. A Good: SOA.Primary Name Server included in the delegation set.: c.dns.ar. 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 Info: Ipv4-Subnet-list: 5 Name Servers, 3 different subnets (first Byte): 130., 170., 200., 3 different subnets (first two Bytes): 130.59., 170.238., 200.108., 5 different subnets (first three Bytes): 130.59.31., 170.238.66., 200.108.145., 200.108.147., 200.108.148. A Good: Name Server IPv4-addresses from different subnet found: A Info: IPv6-Subnet-list: 5 Name Servers with IPv6, 2 different subnets (first block): 2001:, 2801:, 2 different subnets (first two blocks): 2001:0620:, 2801:0140:, 5 different subnets (first three blocks): 2001:0620:0000:, 2801:0140:0000:, 2801:0140:0010:, 2801:0140:0011:, 2801:0140:eeee:, 5 different subnets (first four blocks): 2001:0620:0000:00ff:, 2801:0140:0000:0000:, 2801:0140:0010:0000:, 2801:0140:0011:0000:, 2801:0140:eeee:0000: A Good: Name Server IPv6 addresses from different subnets found. X Nameserver Timeout checking Echo Capitalization: a.dns.ar / 2801:140::10 X Nameserver Timeout checking Echo Capitalization: e.dns.ar / 2801:140:eeee::50 X Nameserver Timeout checking EDNS512: a.dns.ar / 2801:140::10 Nameserver doesn't pass all EDNS-Checks: a.dns.ar / 2801:140::10: 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: f.dns.ar: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (sako.switch.ch). COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns1.tresacolor.com.ar: 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: ns2.tresacolor.com.ar: 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 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. A Good: No https + http status 200 with inline CSS / JavaScript found https://tresacolor.com.ar/ 200.58.112.226 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.tresacolor.com.ar/ 200.58.112.226 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://200.58.112.226/ 200.58.112.226 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. 6 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. 1 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. 8 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 0 with Cache-Control max-age too short (minimum 7 days), 2 with Cache-Control long enough, 10 complete. Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 2 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), 0 with Cache-Control long enough, 2 complete. A Good: All checked attribute values are enclosed in quotation marks (" or '). A Good: All img-elements have a valid alt-attribute.: 2 img-elements 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: 251406 milliseconds, 251.406 seconds