1. General Results, most used to calculate the result A name "market.diana-enterprise.com" is subdomain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 63591 (complete: 175327) A Good: All ip addresses are public addresses Warning: Only one ip address found: market.diana-enterprise.com has only one ip address. Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: market.diana-enterprise.com has no ipv6 address. A Good: No asked Authoritative Name Server had a timeout A DNS: "Name Error" means: No www-dns-entry defined. This isn't a problem A Good: one preferred version: non-www is preferred A Good: every cookie sent via https is marked as secure A Good: Every cookie has a SameSite Attribute with a correct value Strict/Lax/None 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):3 complete Content-Type - header (4 urls) http://market.diana-enterprise.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.133.60.229 Url with incomplete Content-Type - header - missing charset B https://market.diana-enterprise.com/ 18.133.60.229 Missing HSTS-Header http://market.diana-enterprise.com/ 18.133.60.229 ceid=438cdd0052741886c34a38bec606c676; path=/; domain=market.diana-enterprise.com; secure; SameSite=Lax Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative. 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://market.diana-enterprise.com/ 18.133.60.229 Error - Certificate isn't trusted, RemoteCertificateChainErrors N https://18.133.60.229/ 18.133.60.229 Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors N market.diana-enterprise.com:465 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N market.diana-enterprise.com:2083 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N market.diana-enterprise.com:2087 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N market.diana-enterprise.com:2096 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N 18.133.60.229:465 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N 18.133.60.229:2083 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N 18.133.60.229:2087 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N 18.133.60.229:2096 Error - Certificate isn't trusted, RemoteCertificateNameMismatch Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are different. So that domain requires Server Name Indication (SNI), so the server is able to select the correct certificate.: Domain market.diana-enterprise.com, 1 ip addresses. 2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete) 3. DNS- and NameServer - Checks A Info:: 11 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 6 Name Servers. A Info:: 11 Queries complete, 5 with IPv6, 6 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. A Good: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns1.onlydomains.com (75.2.6.34), ns2.onlydomains.com (75.2.85.37), ns3.onlydomains.com (99.83.188.20) A Good (1 - 3.0):: An average of 1.8 queries per domain name server required to find all ip addresses of all name servers. A Info:: 6 different Name Servers found: ns1.hostingww.com, ns1.onlydomains.com, ns2.hostingww.com, ns2.onlydomains.com, ns3.hostingww.com, ns3.onlydomains.com, 3 Name Servers included in Delegation: ns1.onlydomains.com, ns2.onlydomains.com, ns3.onlydomains.com, 3 Name Servers included in 1 Zone definitions: ns1.hostingww.com, ns2.hostingww.com, ns3.hostingww.com, 1 Name Servers listed in SOA.Primary: ns1.hostingww.com. A Good: Only one SOA.Primary Name Server found.: ns1.hostingww.com. Error: SOA.Primary Name Server not included in the delegation set.: ns1.hostingww.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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns1.hostingww.com (75.2.6.34): Delegation: ns1.onlydomains.com, ns2.onlydomains.com, ns3.onlydomains.com, Zone: ns1.hostingww.com, ns2.hostingww.com, ns3.hostingww.com. Name Servers defined in Delegation, missing in Zone: ns1.onlydomains.com, ns2.onlydomains.com, ns3.onlydomains.com.Name Servers defined in Zone, missing in Delegation: ns1.hostingww.com, ns2.hostingww.com, ns3.hostingww.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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns1.onlydomains.com (75.2.6.34): Delegation: ns1.onlydomains.com, ns2.onlydomains.com, ns3.onlydomains.com, Zone: ns1.hostingww.com, ns2.hostingww.com, ns3.hostingww.com. Name Servers defined in Delegation, missing in Zone: ns1.onlydomains.com, ns2.onlydomains.com, ns3.onlydomains.com.Name Servers defined in Zone, missing in Delegation: ns1.hostingww.com, ns2.hostingww.com, ns3.hostingww.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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns2.hostingww.com (75.2.85.37): Delegation: ns1.onlydomains.com, ns2.onlydomains.com, ns3.onlydomains.com, Zone: ns1.hostingww.com, ns2.hostingww.com, ns3.hostingww.com. Name Servers defined in Delegation, missing in Zone: ns1.onlydomains.com, ns2.onlydomains.com, ns3.onlydomains.com.Name Servers defined in Zone, missing in Delegation: ns1.hostingww.com, ns2.hostingww.com, ns3.hostingww.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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns2.onlydomains.com (75.2.85.37): Delegation: ns1.onlydomains.com, ns2.onlydomains.com, ns3.onlydomains.com, Zone: ns1.hostingww.com, ns2.hostingww.com, ns3.hostingww.com. Name Servers defined in Delegation, missing in Zone: ns1.onlydomains.com, ns2.onlydomains.com, ns3.onlydomains.com.Name Servers defined in Zone, missing in Delegation: ns1.hostingww.com, ns2.hostingww.com, ns3.hostingww.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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns3.hostingww.com (99.83.188.20): Delegation: ns1.onlydomains.com, ns2.onlydomains.com, ns3.onlydomains.com, Zone: ns1.hostingww.com, ns2.hostingww.com, ns3.hostingww.com. Name Servers defined in Delegation, missing in Zone: ns1.onlydomains.com, ns2.onlydomains.com, ns3.onlydomains.com.Name Servers defined in Zone, missing in Delegation: ns1.hostingww.com, ns2.hostingww.com, ns3.hostingww.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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns3.onlydomains.com (99.83.188.20): Delegation: ns1.onlydomains.com, ns2.onlydomains.com, ns3.onlydomains.com, Zone: ns1.hostingww.com, ns2.hostingww.com, ns3.hostingww.com. Name Servers defined in Delegation, missing in Zone: ns1.onlydomains.com, ns2.onlydomains.com, ns3.onlydomains.com.Name Servers defined in Zone, missing in Delegation: ns1.hostingww.com, ns2.hostingww.com, ns3.hostingww.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 Info: Ipv4-Subnet-list: 6 Name Servers, 2 different subnets (first Byte): 75., 99., 2 different subnets (first two Bytes): 75.2., 99.83., 3 different subnets (first three Bytes): 75.2.6., 75.2.85., 99.83.188. A Good: Name Server IPv4-addresses from different subnet found: A Good: Nameserver supports TCP connections: 6 good Nameserver A Good: Nameserver supports Echo Capitalization: 6 good Nameserver A Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 6 good Nameserver Nameserver doesn't pass all EDNS-Checks: ns1.hostingww.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. Nameserver doesn't pass all EDNS-Checks: ns1.hostingww.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. 4. Content- and Performance-critical Checks A Good: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. A Good: Every https result with status 200 supports GZip. https://market.diana-enterprise.com/ 18.133.60.229 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://18.133.60.229/ 18.133.60.229 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. A Good: Every https result with status 200 has a minified Html-Content with a quota lower then 110 %. https://market.diana-enterprise.com/ 18.133.60.229 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. https://18.133.60.229/ 18.133.60.229 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. https://market.diana-enterprise.com/ 18.133.60.229 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.: 3 script elements without defer/async. https://18.133.60.229/ 18.133.60.229 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.: 2 script elements without defer/async. A Good: All CSS / JavaScript files are sent with GZip. That reduces the content of the files. 5 external CSS / JavaScript files found Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 3 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 0 with Cache-Control max-age too short (minimum 7 days), 5 with Cache-Control long enough, 8 complete. Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 8 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, 8 complete. A Good: All checked attribute values are enclosed in quotation marks (" or '). A Good: All img-elements have a valid alt-attribute.: 8 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 Duration: 114677 milliseconds, 114.677 seconds