A name "smidish.epizy.com" is subdomain, 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: No asked Authoritative Name Server had a timeout A Good: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (6 urls) http://smidish.epizy.com/ 185.27.134.149 Url with incomplete Content-Type - header - missing charset http://www.smidish.epizy.com/ 185.27.134.149 Url with incomplete Content-Type - header - missing charset https://smidish.epizy.com/ 185.27.134.149 Url with incomplete Content-Type - header - missing charset https://www.smidish.epizy.com/ 185.27.134.149 Url with incomplete Content-Type - header - missing charset http://smidish.epizy.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.27.134.149 Url with incomplete Content-Type - header - missing charset http://www.smidish.epizy.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.27.134.149 Url with incomplete Content-Type - header - missing charset B https://smidish.epizy.com/ 185.27.134.149 200 Missing HSTS-Header B https://www.smidish.epizy.com/ 185.27.134.149 200 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. 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. 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. J https://smidish.epizy.com/ 185.27.134.149 200 Fatal: Script /aes.js found. Looks like your hoster has a Bot-Check-Detection, so Letsencrypt can't check your http-validation file. J https://www.smidish.epizy.com/ 185.27.134.149 200 Fatal: Script /aes.js found. Looks like your hoster has a Bot-Check-Detection, so Letsencrypt can't check your http-validation file. J http://smidish.epizy.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.27.134.149 200 Fatal: Script /aes.js found. Looks like your hoster has a Bot-Check-Detection, so Letsencrypt can't check your http-validation file. J http://www.smidish.epizy.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.27.134.149 200 Fatal: Script /aes.js found. Looks like your hoster has a Bot-Check-Detection, so Letsencrypt can't check your http-validation file. N https://smidish.epizy.com/ 185.27.134.149 200 Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors N https://www.smidish.epizy.com/ 185.27.134.149 200 Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors A Good: Nameserver supports TCP connections: 1 good Nameserver A Good: Nameserver supports Echo Capitalization: 1 good Nameserver A Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver A Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 1 good Nameserver Nameserver doesn't pass all EDNS-Checks: ns1.byet.org: 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 (ns1.byet.org). COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns1.epizy.com: 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 (ns1.byet.org). COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns1.epizy.com: 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 (ns1.byet.org). COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns1.epizy.com / 198.251.86.152: 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 (ns1.byet.org). COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns2.byet.org: 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 (ns1.byet.org). COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns2.epizy.com: 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 (ns1.byet.org). COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns3.byet.org: 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 (internaldns.byetcluster.com). COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns5.byet.org: 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 (ns1.byet.org). COOKIE: ok. CLIENTSUBNET: ok. 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 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: 64396 milliseconds, 64.396 seconds