1. General Results, most used to calculate the result A name "harbaharummart.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: one preferred version: www is preferred 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):1 complete Content-Type - header (5 urls) http://harbaharummart.com/ 178.128.217.145 Url with incomplete Content-Type - header - missing charset http://www.harbaharummart.com/ 49.50.8.232 Url with incomplete Content-Type - header - missing charset https://www.harbaharummart.com/ 49.50.8.232 Url with incomplete Content-Type - header - missing charset http://harbaharummart.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 178.128.217.145 Url with incomplete Content-Type - header - missing charset B https://www.harbaharummart.com/ 49.50.8.232 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. 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. N https://www.harbaharummart.com/ 49.50.8.232 Error - Certificate isn't trusted, RemoteCertificateNameMismatch O Old connection: Tls.1.0 is deprecated, Tls.1.2 should be supported O Old connection: RSA Key Exchange is unsecure. Use Diffie-Hellman or Elliptic Curve Diffi-Hellmann Key Exchange to support Forward Secrecy O Old connection: SHA1 as Hash Algorithm is deprecated. Switch to SHA256 or SHA384. If your certificate has SHA256, first check your domain via ssllabs.com and update weak Cipher Suites. Forward Secrecy support is required. The part "Cipher Suites" should have a preference. First Cipher Suite with SHA instead of SHA256 or higher - that's the problem, change that. If that doesn't help, check if there is an old Firewall / router or something else, that supports only SHA1. Update that component. V https://harbaharummart.com/ 178.128.217.145 connect failure - perhaps firewall 2. DNS- and NameServer - Checks 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.: dns1.masterwebnet.com (202.157.177.169): Delegation: dns1.masterwebnet.com,dns2.masterweb.net,dns3.masterweb.com,dns4.masterwebnet.com, Zone: dns1.masterweb.com,dns2.masterweb.net,dns3.masterwebnet.com,dns4.masterweb.net 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.: dns2.masterweb.net (45.64.1.209): Delegation: dns1.masterwebnet.com,dns2.masterweb.net,dns3.masterweb.com,dns4.masterwebnet.com, Zone: dns1.masterweb.com,dns2.masterweb.net,dns3.masterwebnet.com,dns4.masterweb.net 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.: dns3.masterweb.com (149.28.149.165): Delegation: dns1.masterwebnet.com,dns2.masterweb.net,dns3.masterweb.com,dns4.masterwebnet.com, Zone: dns1.masterweb.com,dns2.masterweb.net,dns3.masterwebnet.com,dns4.masterweb.net 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.: dns3.masterwebnet.com (149.28.149.165): Delegation: dns1.masterwebnet.com,dns2.masterweb.net,dns3.masterweb.com,dns4.masterwebnet.com, Zone: dns1.masterweb.com,dns2.masterweb.net,dns3.masterwebnet.com,dns4.masterweb.net 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.: dns4.masterweb.net (45.79.30.92): Delegation: dns1.masterwebnet.com,dns2.masterweb.net,dns3.masterweb.com,dns4.masterwebnet.com, Zone: dns1.masterweb.com,dns2.masterweb.net,dns3.masterwebnet.com,dns4.masterweb.net 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.: dns4.masterwebnet.com (45.79.30.92): Delegation: dns1.masterwebnet.com,dns2.masterweb.net,dns3.masterweb.com,dns4.masterwebnet.com, Zone: dns1.masterweb.com,dns2.masterweb.net,dns3.masterwebnet.com,dns4.masterweb.net A Info: Nameserver mit different domain names found. May be a problem with DNS-Updates A Good: Nameserver supports TCP connections: 7 good Nameserver A Good: Nameserver supports Echo Capitalization: 7 good Nameserver A Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 7 good Nameserver A Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 7 good Nameserver Nameserver doesn't pass all EDNS-Checks: dns1.masterweb.com: 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. 3. Content- and Performance-critical Checks http://www.harbaharummart.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 49.50.8.232 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. A Good: Every https result with status 200 supports GZip. https://www.harbaharummart.com/ 49.50.8.232 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.harbaharummart.com/ 49.50.8.232 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.harbaharummart.com/ 49.50.8.232 Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2. Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 1 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, 1 complete. A Good: Some checked attribute values are enclosed in quotation marks (" or ').: 7 Html-Elements checked, 1 without problems. I Wrong: Attribute values found, not enclosed in quotation marks (" or ').: 6 Html-Elements with attributes and missing enclosed quotation marks found. 6 wrong attributes. A Good: All img-elements have a valid alt-attribute.: 1 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 Info: Different Server-Headers found A Duration: 130543 milliseconds, 130.543 seconds