1. General Results, most used to calculate the result A name "pr.projectline.de" is subdomain, public suffix is ".de", top-level-domain is ".de", top-level-domain-type is "country-code", Country is Germany, tld-manager is "DENIC eG", num .de-domains preloaded: 7449 (complete: 175327) A Good: All ip addresses are public addresses A Good: Minimal 2 ip addresses per domain name found: pr.projectline.de has 2 different ip addresses (authoritative). 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: pr.projectline.de 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: No cookie sent via http. 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: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset) A http://pr.projectline.de/ 78.47.181.238 https://pr.projectline.de/ Correct redirect http - https with the same domain name B https://pr.projectline.de/ 78.47.181.238 Missing HSTS-Header B https://pr.projectline.de/ 78.47.181.240 Missing HSTS-Header B https://pr.projectline.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Missing HSTS-Header B https://pr.projectline.de/ 78.47.181.238 PHPSESSID=fin5jootrknjoje71k0tmi2llo; path=/ Cookie sent via https, but not marked as secure B https://pr.projectline.de/ 78.47.181.240 PHPSESSID=56bcado4hrvhiqh8b3k9ml5hgd; path=/ Cookie sent via https, but not marked as secure B https://78.47.181.238/ 78.47.181.238 PHPSESSID=brm4l054tmh3vpvegtko7ucvh9; path=/ Cookie sent via https, but not marked as secure B https://78.47.181.240/ 78.47.181.240 PHPSESSID=5s99fttl0ntopblvd25mpe4eur; path=/ Cookie sent via https, but not marked as secure B https://pr.projectline.de/ 78.47.181.238 PHPSESSID=fin5jootrknjoje71k0tmi2llo; path=/ Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://pr.projectline.de/ 78.47.181.240 PHPSESSID=56bcado4hrvhiqh8b3k9ml5hgd; path=/ Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://78.47.181.238/ 78.47.181.238 PHPSESSID=brm4l054tmh3vpvegtko7ucvh9; path=/ Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://78.47.181.240/ 78.47.181.240 PHPSESSID=5s99fttl0ntopblvd25mpe4eur; path=/ Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. 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. I https://pr.projectline.de/ 78.47.181.238 Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part. I https://pr.projectline.de/ 78.47.181.240 Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part. K http://pr.projectline.de/ 78.47.181.238, Status 301 http://pr.projectline.de/ 78.47.181.240, Status 200 Configuration problem - different ip addresses with different status K http://pr.projectline.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 78.47.181.238, Status 301 http://pr.projectline.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 78.47.181.240, Status 404 Configuration problem - different ip addresses with different status N https://78.47.181.238/ 78.47.181.238 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://78.47.181.240/ 78.47.181.240 Error - Certificate isn't trusted, RemoteCertificateNameMismatch A Good: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain pr.projectline.de, 2 ip addresses. 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 the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain pr.projectline.de, 2 ip addresses, 1 different http results. 2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete) 3. DNS- and NameServer - Checks A Info:: 6 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers. A Info:: 6 Queries complete, 6 with IPv6, 0 with IPv4. A Good: All DNS Queries done via IPv6. 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.ns.udag.de (192.174.68.8, 2001:67c:1bc::8), ns.udag.net (176.97.158.8, 2001:67c:10b8::8), ns.udag.org (176.97.158.91, 2001:67c:1bc::91) A Good (1 - 3.0):: An average of 2.0 queries per domain name server required to find all ip addresses of all name servers. A Info:: 3 different Name Servers found: ns.udag.de, ns.udag.net, ns.udag.org, 3 Name Servers included in Delegation: ns.udag.de, ns.udag.net, ns.udag.org, 3 Name Servers included in 1 Zone definitions: ns.udag.de, ns.udag.net, ns.udag.org, 1 Name Servers listed in SOA.Primary: ns.udag.de. A Good: Only one SOA.Primary Name Server found.: ns.udag.de. A Good: SOA.Primary Name Server included in the delegation set.: ns.udag.de. A Good: Consistency 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. Ordered list of name servers: ns.udag.de, ns.udag.net, ns.udag.org 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 Good: Minimal 2 different name servers (public suffix and public ip address) found: 3 different Name Servers found A Good: All name servers have ipv4- and ipv6-addresses.: 3 different Name Servers found A Good: Name servers with different Top Level Domains / Public Suffix List entries found: 3 Name Servers, 3 Top Level Domains: de, org, net A Good: Name Servers with different domain names found.: 3 different Domains found A Good: Name servers with different Country locations found: 3 Name Servers, 2 Countries: AT, CH A Info: Ipv4-Subnet-list: 3 Name Servers, 2 different subnets (first Byte): 176., 192., 2 different subnets (first two Bytes): 176.97., 192.174., 2 different subnets (first three Bytes): 176.97.158., 192.174.68. A Good: Name Server IPv4-addresses from different subnet found: A Info: IPv6-Subnet-list: 3 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:067c:, 2 different subnets (first three blocks): 2001:067c:01bc:, 2001:067c:10b8:, 2 different subnets (first four blocks): 2001:067c:01bc:0000:, 2001:067c:10b8:0000: A Good: Name Server IPv6 addresses from different subnets found. A Good: Nameserver supports TCP connections: 2 good Nameserver A Good: Nameserver supports Echo Capitalization: 2 good Nameserver A Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver A Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver Nameserver doesn't pass all EDNS-Checks: ns.udag.de: 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://pr.projectline.de/ 78.47.181.238 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://pr.projectline.de/ 78.47.181.240 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://78.47.181.238/ 78.47.181.238 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://78.47.181.240/ 78.47.181.240 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://pr.projectline.de/ 78.47.181.238 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://pr.projectline.de/ 78.47.181.240 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://78.47.181.238/ 78.47.181.238 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://78.47.181.240/ 78.47.181.240 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://pr.projectline.de/ 78.47.181.238 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://pr.projectline.de/ 78.47.181.240 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://78.47.181.238/ 78.47.181.238 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://78.47.181.240/ 78.47.181.240 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://pr.projectline.de/ 78.47.181.238 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.: 5 script elements without defer/async. https://pr.projectline.de/ 78.47.181.240 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.: 5 script elements without defer/async. https://78.47.181.238/ 78.47.181.238 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.: 5 script elements without defer/async. https://78.47.181.240/ 78.47.181.240 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.: 5 script elements without defer/async. Warning: CSS / JavaScript found without GZip support. Send these ressources with GZip. 8 external CSS / JavaScript files without GZip found - 4 with GZip, 12 complete A Good: All images with internal compression not sent via GZip. Images (.png, .jpg) are already compressed, so an additional GZip isn't helpful. 2 images (type image/png, image/jpg) found without additional GZip. Not required because these images are already compressed Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 16 external CSS / JavaScript files without Cache-Control-Header, 2 with Cache-Control, but no max-age, 6 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 24 complete. Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 12 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, 12 complete. A Good: All checked attribute values are enclosed in quotation marks (" or '). Wrong: img-elements without alt-attribute or empty alt-attribute found. The alt-attribute ("alternative") is required and should describe the img. So Screenreader and search engines are able to use these informations.: 12 img-elements without alt-attribute, 0 img-elements with empty alt-attribute 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 https://pr.projectline.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.077 seconds Warning: 404 needs more then one second A Duration: 328900 milliseconds, 328.900 seconds