1. General Results, most used to calculate the result A name "rightdecisions.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: 153 (complete: 151507) A good: All ip addresses are public addresses A Good: Minimal 2 ip addresses per domain name found: rightdecisions.com.ar has 2 different ip addresses (authoritative). A Good: Minimal 2 ip addresses per domain name found: www.rightdecisions.com.ar has 2 different ip addresses (authoritative). A Good: Ipv4 and Ipv6 addresses per domain name found: rightdecisions.com.ar has 1 ipv4, 1 ipv6 addresses A Good: Ipv4 and Ipv6 addresses per domain name found: www.rightdecisions.com.ar has 1 ipv4, 1 ipv6 addresses A good: No asked Authoritative Name Server had a timeout 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):9 complete Content-Type - header (12 urls) https://rightdecisions.com.ar/ 2800:6c0:2::180 Url with incomplete Content-Type - header - missing charset https://www.rightdecisions.com.ar/ 2800:6c0:2::180 Url with incomplete Content-Type - header - missing charset https://[2800:06c0:0002:0000:0000:0000:0000:0180]/ 2800:6c0:2::180 Url with incomplete Content-Type - header - missing charset A http://rightdecisions.com.ar/ 178.128.144.5 https://rightdecisions.com.ar/ correct redirect http - https with the same domain name A http://www.rightdecisions.com.ar/ 178.128.144.5 https://www.rightdecisions.com.ar/ correct redirect http - https with the same domain name B https://rightdecisions.com.ar/ 2800:6c0:2::180 Missing HSTS-Header B https://www.rightdecisions.com.ar/ 2800:6c0:2::180 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. 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. K http://rightdecisions.com.ar/ 178.128.144.5, Status 301 http://rightdecisions.com.ar/ 200.58.112.185, Status -14 configuration problem - different ip addresses with different status K http://rightdecisions.com.ar/ 178.128.144.5, Status 301 http://rightdecisions.com.ar/ 2800:6c0:2::180, Status 200 configuration problem - different ip addresses with different status K http://rightdecisions.com.ar/ 200.58.112.185, Status -14 http://rightdecisions.com.ar/ 2800:6c0:2::180, Status 200 configuration problem - different ip addresses with different status K http://www.rightdecisions.com.ar/ 200.58.112.185, Status -14 http://www.rightdecisions.com.ar/ 2800:6c0:2::180, Status 200 configuration problem - different ip addresses with different status K http://www.rightdecisions.com.ar/ 200.58.112.185, Status -14 http://www.rightdecisions.com.ar/ 178.128.144.5, Status 301 configuration problem - different ip addresses with different status K http://www.rightdecisions.com.ar/ 2800:6c0:2::180, Status 200 http://www.rightdecisions.com.ar/ 178.128.144.5, Status 301 configuration problem - different ip addresses with different status K https://rightdecisions.com.ar/ 178.128.144.5, Status 200 https://rightdecisions.com.ar/ 200.58.112.185, Status -14 configuration problem - different ip addresses with different status K https://rightdecisions.com.ar/ 200.58.112.185, Status -14 https://rightdecisions.com.ar/ 2800:6c0:2::180, Status 200 configuration problem - different ip addresses with different status K https://www.rightdecisions.com.ar/ 200.58.112.185, Status -14 https://www.rightdecisions.com.ar/ 2800:6c0:2::180, Status 200 configuration problem - different ip addresses with different status K https://www.rightdecisions.com.ar/ 200.58.112.185, Status -14 https://www.rightdecisions.com.ar/ 178.128.144.5, Status 200 configuration problem - different ip addresses with different status K http://rightdecisions.com.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 178.128.144.5, Status 301 http://rightdecisions.com.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 200.58.112.185, Status -14 configuration problem - different ip addresses with different status K http://rightdecisions.com.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 178.128.144.5, Status 301 http://rightdecisions.com.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2800:6c0:2::180, Status 404 configuration problem - different ip addresses with different status K http://rightdecisions.com.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 200.58.112.185, Status -14 http://rightdecisions.com.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2800:6c0:2::180, Status 404 configuration problem - different ip addresses with different status K http://www.rightdecisions.com.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 200.58.112.185, Status -14 http://www.rightdecisions.com.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2800:6c0:2::180, Status 404 configuration problem - different ip addresses with different status K http://www.rightdecisions.com.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 200.58.112.185, Status -14 http://www.rightdecisions.com.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 178.128.144.5, Status 301 configuration problem - different ip addresses with different status K http://www.rightdecisions.com.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2800:6c0:2::180, Status 404 http://www.rightdecisions.com.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 178.128.144.5, Status 301 configuration problem - different ip addresses with different status N https://rightdecisions.com.ar/ 2800:6c0:2::180 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://www.rightdecisions.com.ar/ 2800:6c0:2::180 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://178.128.144.5/ 178.128.144.5 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://[2800:06c0:0002:0000:0000:0000:0000:0180]/ 2800:6c0:2::180 Error - Certificate isn't trusted, RemoteCertificateNameMismatch X Fatal error: Nameserver doesn't support TCP connection: ar.cctld.authdns.ripe.net: Fatal error (-14). Details: Unable to read data from the transport connection: Eine vorhandene Verbindung wurde vom Remotehost geschlossen. - Eine vorhandene Verbindung wurde vom Remotehost geschlossen 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 rightdecisions.com.ar, 2 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.rightdecisions.com.ar, 2 ip addresses. 2. DNS- and NameServer - Checks A Info:: 22 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 7 Name Servers. A Info:: 22 Queries complete, 11 with IPv6, 11 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.1 queries per domain name server required to find all ip addresses of all name servers. A Info:: 7 different Name Servers found: ns1.digitalocean.com, ns1.donweb.com, ns2.digitalocean.com, ns2.donweb.com, ns3.digitalocean.com, ns3.hostmar.com, ns4.hostmar.com, 5 Name Servers included in Delegation: ns1.digitalocean.com, ns1.donweb.com, ns2.digitalocean.com, ns2.donweb.com, ns3.digitalocean.com, 5 Name Servers included in 2 Zone definitions: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com, ns3.hostmar.com, ns4.hostmar.com, 2 Name Servers listed in SOA.Primary: ns1.digitalocean.com, ns3.hostmar.com. Error: Different SOA.Primary Name Servers found, different SOA Definitions.: ns1.digitalocean.com,ns3.hostmar.com. Error: SOA.Primary Name Server not included in the delegation set.: ns1.digitalocean.com,ns3.hostmar.com. X Fatal: Inconsistency 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.: ns1.digitalocean.com (173.245.58.51): Delegation: ns1.digitalocean.com, ns1.donweb.com, ns2.digitalocean.com, ns2.donweb.com, ns3.digitalocean.com, Zone: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com. Name Servers defined in Delegation, missing in Zone: ns1.donweb.com, ns2.donweb.com. X Fatal: Inconsistency 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.: ns1.digitalocean.com (2400:cb00:2049:1::adf5:3a33): Delegation: ns1.digitalocean.com, ns1.donweb.com, ns2.digitalocean.com, ns2.donweb.com, ns3.digitalocean.com, Zone: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com. Name Servers defined in Delegation, missing in Zone: ns1.donweb.com, ns2.donweb.com. X Fatal: Inconsistency 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.: ns1.donweb.com (200.58.112.193): Delegation: ns1.digitalocean.com, ns1.donweb.com, ns2.digitalocean.com, ns2.donweb.com, ns3.digitalocean.com, Zone: ns3.hostmar.com, ns4.hostmar.com. Name Servers defined in Delegation, missing in Zone: ns1.digitalocean.com, ns1.donweb.com, ns2.digitalocean.com, ns2.donweb.com, ns3.digitalocean.com.Name Servers defined in Zone, missing in Delegation: ns3.hostmar.com, ns4.hostmar.com. X Fatal: Inconsistency 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.: ns2.digitalocean.com (173.245.59.41): Delegation: ns1.digitalocean.com, ns1.donweb.com, ns2.digitalocean.com, ns2.donweb.com, ns3.digitalocean.com, Zone: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com. Name Servers defined in Delegation, missing in Zone: ns1.donweb.com, ns2.donweb.com. X Fatal: Inconsistency 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.: ns2.digitalocean.com (2400:cb00:2049:1::adf5:3b29): Delegation: ns1.digitalocean.com, ns1.donweb.com, ns2.digitalocean.com, ns2.donweb.com, ns3.digitalocean.com, Zone: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com. Name Servers defined in Delegation, missing in Zone: ns1.donweb.com, ns2.donweb.com. X Fatal: Inconsistency 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.: ns2.donweb.com (200.58.112.101): Delegation: ns1.digitalocean.com, ns1.donweb.com, ns2.digitalocean.com, ns2.donweb.com, ns3.digitalocean.com, Zone: ns3.hostmar.com, ns4.hostmar.com. Name Servers defined in Delegation, missing in Zone: ns1.digitalocean.com, ns1.donweb.com, ns2.digitalocean.com, ns2.donweb.com, ns3.digitalocean.com.Name Servers defined in Zone, missing in Delegation: ns3.hostmar.com, ns4.hostmar.com. X Fatal: Inconsistency 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.: ns3.digitalocean.com (198.41.222.173): Delegation: ns1.digitalocean.com, ns1.donweb.com, ns2.digitalocean.com, ns2.donweb.com, ns3.digitalocean.com, Zone: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com. Name Servers defined in Delegation, missing in Zone: ns1.donweb.com, ns2.donweb.com. X Fatal: Inconsistency 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.: ns3.digitalocean.com (2400:cb00:2049:1::c629:dead): Delegation: ns1.digitalocean.com, ns1.donweb.com, ns2.digitalocean.com, ns2.donweb.com, ns3.digitalocean.com, Zone: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com. Name Servers defined in Delegation, missing in Zone: ns1.donweb.com, ns2.donweb.com. X Fatal: Inconsistency 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.: ns3.hostmar.com (200.58.112.193): Delegation: ns1.digitalocean.com, ns1.donweb.com, ns2.digitalocean.com, ns2.donweb.com, ns3.digitalocean.com, Zone: ns3.hostmar.com, ns4.hostmar.com. Name Servers defined in Delegation, missing in Zone: ns1.digitalocean.com, ns1.donweb.com, ns2.digitalocean.com, ns2.donweb.com, ns3.digitalocean.com.Name Servers defined in Zone, missing in Delegation: ns3.hostmar.com, ns4.hostmar.com. X Fatal: Inconsistency 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.: ns4.hostmar.com (200.58.112.101): Delegation: ns1.digitalocean.com, ns1.donweb.com, ns2.digitalocean.com, ns2.donweb.com, ns3.digitalocean.com, Zone: ns3.hostmar.com, ns4.hostmar.com. Name Servers defined in Delegation, missing in Zone: ns1.digitalocean.com, ns1.donweb.com, ns2.digitalocean.com, ns2.donweb.com, ns3.digitalocean.com.Name Servers defined in Zone, missing in Delegation: ns3.hostmar.com, ns4.hostmar.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: 7 different Name Servers found A Good: Some Name Servers have IPv6 addresses: 3 Name Servers with IPv6 found (4 Name Servers without IPv6) 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.: 7 Name Servers, 1 Top Level Domain: com A Good: Name Servers with different domain names found.: 3 different Domains found A Good: Name servers with different Country locations found: 7 Name Servers, 2 Countries: AR, US A Info: Ipv4-Subnet-list: 7 Name Servers, 3 different subnets (first Byte): 173., 198., 200., 3 different subnets (first two Bytes): 173.245., 198.41., 200.58., 4 different subnets (first three Bytes): 173.245.58., 173.245.59., 198.41.222., 200.58.112. A Good: Name Server IPv4-addresses from different subnet found: A Info: IPv6-Subnet-list: 3 Name Servers with IPv6, 1 different subnets (first block): 2400:, 1 different subnets (first two blocks): 2400:cb00:, 1 different subnets (first three blocks): 2400:cb00:2049:, 1 different subnets (first four blocks): 2400:cb00:2049:0001: Fatal: All Name Server IPv6 addresses from the same subnet. A Info: Nameserver mit different domain names found. May be a problem with DNS-Updates A Good: Nameserver supports TCP connections: 10 good Nameserver A Good: Nameserver supports Echo Capitalization: 10 good Nameserver A Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 10 good Nameserver A Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 6 good Nameserver Nameserver doesn't pass all EDNS-Checks: ns1.donweb.com / 200.58.112.193: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (PowerDNS). COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns2.donweb.com / 200.58.112.101: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (PowerDNS). COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns3.hostmar.com / 200.58.112.193: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (PowerDNS). COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns4.hostmar.com / 200.58.112.101: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (PowerDNS). COOKIE: ok. CLIENTSUBNET: ok. X Fatal error: Nameservers with different SOA Serial Numbers 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 https://rightdecisions.com.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. https://www.rightdecisions.com.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://rightdecisions.com.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 200.58.112.185 Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. 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. http://www.rightdecisions.com.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 200.58.112.185 Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. 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. http://rightdecisions.com.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2800:6c0:2::180, Status 404 http://rightdecisions.com.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 178.128.144.5, Status 301 Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://rightdecisions.com.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2800:6c0:2::180, Status 404 http://rightdecisions.com.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 200.58.112.185, Status -14 Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://www.rightdecisions.com.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2800:6c0:2::180, Status 404 http://www.rightdecisions.com.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 200.58.112.185, Status -14 Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://www.rightdecisions.com.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2800:6c0:2::180, Status 404 http://www.rightdecisions.com.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 178.128.144.5, Status 301 Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. A Good: Every https result with status 200 supports GZip. https://rightdecisions.com.ar/ 178.128.144.5 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.rightdecisions.com.ar/ 178.128.144.5 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://rightdecisions.com.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 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.rightdecisions.com.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 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://178.128.144.5/ 178.128.144.5 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://rightdecisions.com.ar/ 2800:6c0:2::180 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.rightdecisions.com.ar/ 2800:6c0:2::180 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://178.128.144.5/ 178.128.144.5 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://[2800:06c0:0002:0000:0000:0000:0000:0180]/ 2800:6c0:2::180 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. https://rightdecisions.com.ar/ 178.128.144.5 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.: 6 script elements without defer/async. https://www.rightdecisions.com.ar/ 178.128.144.5 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.: 6 script elements without defer/async. https://rightdecisions.com.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 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.: 6 script elements without defer/async. https://www.rightdecisions.com.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 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.: 6 script elements without defer/async. https://178.128.144.5/ 178.128.144.5 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.: 7 script elements without defer/async. Warning: CSS / JavaScript found without GZip support. Send these ressources with GZip. 8 external CSS / JavaScript files without GZip found - 28 with GZip, 36 complete Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 10 external CSS / JavaScript files without Cache-Control-Header, 8 with Cache-Control, but no max-age, 4 with Cache-Control max-age too short (minimum 7 days), 24 with Cache-Control long enough, 46 complete. A Good: All checked attribute values are enclosed in quotation marks (" or '). 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 A Info: Different Server-Headers found A Duration: 430826 milliseconds, 430.826 seconds