1. General Results, most used to calculate the result A name "unidn.com" is domain, public suffix is "com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services" A Good: All ip addresses are public addresses A Good: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset) B https://unidn.com/ 37.187.106.43 Missing HSTS-Header B https://www.unidn.com/ 37.187.106.43 Missing HSTS-Header B https://www.unidn.com/ 37.187.106.43 PHPSESSID=j0ab894ib0jur3n4k5phntsnon; Path=/; Domain=www.unidn.com Cookie sent via https, but not marked as secure 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://unidn.com/ 37.187.106.43, Status 200 http://unidn.com/ 2001:41d0:a:3a2b::1, Status -2 Configuration problem - different ip addresses with different status K https://unidn.com/ 37.187.106.43, Status 200 https://unidn.com/ 2001:41d0:a:3a2b::1, Status -2 Configuration problem - different ip addresses with different status K http://unidn.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 37.187.106.43, Status 401 http://unidn.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:41d0:a:3a2b::1, Status -2 Configuration problem - different ip addresses with different status N unidn.com:465 Error - Certificate isn't trusted, RemoteCertificateChainErrors N unidn.com:993 Error - Certificate isn't trusted, RemoteCertificateChainErrors N unidn.com:995 Error - Certificate isn't trusted, RemoteCertificateChainErrors N www.unidn.com:465 Error - Certificate isn't trusted, RemoteCertificateChainErrors N www.unidn.com:993 Error - Certificate isn't trusted, RemoteCertificateChainErrors N www.unidn.com:995 Error - Certificate isn't trusted, RemoteCertificateChainErrors N 37.187.106.43:465 Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors N 37.187.106.43:993 Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors N 37.187.106.43:995 Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors N https://unidn.com/ 37.187.106.43 Error - Certificate isn't trusted, RemoteCertificateChainErrors N https://www.unidn.com/ 37.187.106.43 Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors V http://unidn.com/ 2001:41d0:a:3a2b::1 Connect failure - perhaps firewall V https://unidn.com/ 2001:41d0:a:3a2b::1 Connect failure - perhaps firewall V http://unidn.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:41d0:a:3a2b::1 Connect failure - perhaps firewall X Fatal error: Nameserver isn't defined or has timeout X Fatal error: Nameserver doesn't support TCP connection: ns1.unidn.com / 2001:41d0:1:f2be::1: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it [2001:41d0:1:f2be::1]:53 2. Header-Checks 3. DNS- and NameServer - Checks Nameserver doesn't pass all EDNS-Checks: ns1.unidn.com / 2001:41d0:1:f2be::1: 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 http://unidn.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 37.187.106.43 Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://www.unidn.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 37.187.106.43 Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://unidn.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:41d0:a:3a2b::1 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. http://unidn.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:41d0:a:3a2b::1, Status -2 http://unidn.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 37.187.106.43, Status 401 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: 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: 99773 milliseconds, 99.773 seconds