1. General Results, most used to calculate the result A name "habibindustry.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: No asked Authoritative Name Server had a timeout A Good: destination is https A Good: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset) B https://habibindustry.com/ 118.179.70.235 Missing HSTS-Header B https://www.habibindustry.com/ 118.179.70.235 Missing HSTS-Header B https://habibindustry.com/ 118.179.70.235 csrftoken=JnEZ5BmcFXuoKWzEqwRR1s8a31GSTdPFhYfQ55RpmuePURXREOylQMJD7Mk3Gicg; Path=/; Domain=habibindustry.com; Expires=2020-06-27 21:20:17 Cookie sent via https, but not marked as secure B https://www.habibindustry.com/ 118.179.70.235 csrftoken=dcgDb6XFCVfuTXlW4WqKyhD2WW0UGy9SNEodIS3rB9o1OpU1qD8lRrq3tmng6dLY; Path=/; Domain=www.habibindustry.com; Expires=2020-06-27 21:20:20 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. I https://habibindustry.com/ 118.179.70.235 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.habibindustry.com/ 118.179.70.235 Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part. 2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete) 3. DNS- and NameServer - Checks A Good: Nameserver supports TCP connections: 4 good Nameserver A Good: Nameserver supports Echo Capitalization: 4 good Nameserver A Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver A Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver 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://habibindustry.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 118.179.70.235 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.habibindustry.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 118.179.70.235 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. 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: 155187 milliseconds, 155.187 seconds