1. General Results, most used to calculate the result A name "wiki.aakkal.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: 86299 (complete: 221801) A Good: All ip addresses are public addresses A Good: Minimal 2 ip addresses per domain name found: wiki.aakkal.com has 2 different ip addresses (authoritative). A Good: Ipv4 and Ipv6 addresses per domain name found: wiki.aakkal.com has 1 ipv4, 1 ipv6 addresses 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: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):1 complete Content-Type - header (7 urls) http://wiki.aakkal.com/ 2406:da1a:ea0:a900:27e4:4de2:c01d:f336 Url with incomplete Content-Type - header - missing charset https://wiki.aakkal.com/ 2406:da1a:ea0:a900:27e4:4de2:c01d:f336 Url with incomplete Content-Type - header - missing charset http://wiki.aakkal.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2406:da1a:ea0:a900:27e4:4de2:c01d:f336 Url with incomplete Content-Type - header - missing charset https://wiki.aakkal.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Url with incomplete Content-Type - header - missing charset https://3.6.47.120/ 3.6.47.120 Url with incomplete Content-Type - header - missing charset https://[2406:da1a:0ea0:a900:27e4:4de2:c01d:f336]/ 2406:da1a:ea0:a900:27e4:4de2:c01d:f336 Url with incomplete Content-Type - header - missing charset A http://wiki.aakkal.com/ 3.6.47.120 https://wiki.aakkal.com/ Correct redirect http - https with the same domain name B https://wiki.aakkal.com/ 3.6.47.120 Missing HSTS-Header B https://wiki.aakkal.com/ 2406:da1a:ea0:a900:27e4:4de2:c01d:f336 Missing HSTS-Header B https://wiki.aakkal.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Missing HSTS-Header 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://wiki.aakkal.com/ 3.6.47.120 Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part. K http://wiki.aakkal.com/ 3.6.47.120, Status 301 http://wiki.aakkal.com/ 2406:da1a:ea0:a900:27e4:4de2:c01d:f336, Status 200 Configuration problem - different ip addresses with different status K http://wiki.aakkal.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 3.6.47.120, Status 301 http://wiki.aakkal.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2406:da1a:ea0:a900:27e4:4de2:c01d:f336, Status 404 Configuration problem - different ip addresses with different status N https://3.6.47.120/ 3.6.47.120 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://[2406:da1a:0ea0:a900:27e4:4de2:c01d:f336]/ 2406:da1a:ea0:a900:27e4:4de2:c01d:f336 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 wiki.aakkal.com, 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 different. So that domain requires Server Name Indication (SNI), so the server is able to select the correct certificate.: Domain wiki.aakkal.com, 2 ip addresses. B No _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.wiki.aakkal.com 2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete) A wiki.aakkal.com 3.6.47.120 X-Content-Type-Options Ok: Header without syntax errors found: nosniff A X-Frame-Options Ok: Header without syntax errors found: DENY B Info: Header is deprecated. May not longer work in modern browsers. DENY. Better solution: Use a Content-Security-Policy Header with a frame-ancestors directive. DENY - use 'none', SAMEORIGIN - use 'self'. If you want to allow some domains to frame your page, add these urls. F wiki.aakkal.com 3.6.47.120 Content-Security-Policy Critical: Missing Header: F wiki.aakkal.com 3.6.47.120 Referrer-Policy Critical: Missing Header: F wiki.aakkal.com 3.6.47.120 Permissions-Policy Critical: Missing Header: F wiki.aakkal.com 2406:da1a:ea0:a900:27e4:4de2:c01d:f336 Content-Security-Policy Critical: Missing Header: F wiki.aakkal.com 2406:da1a:ea0:a900:27e4:4de2:c01d:f336 X-Content-Type-Options Critical: Missing Header: F wiki.aakkal.com 2406:da1a:ea0:a900:27e4:4de2:c01d:f336 Referrer-Policy Critical: Missing Header: F wiki.aakkal.com 2406:da1a:ea0:a900:27e4:4de2:c01d:f336 Permissions-Policy Critical: Missing Header: 3. DNS- and NameServer - Checks A Info:: 16 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers. A Info:: 16 Queries complete, 16 with IPv6, 0 with IPv4. A Good: All DNS Queries done via IPv6. Ok (4 - 8):: An average of 4.0 queries per domain name server required to find all ip addresses of all name servers. A Info:: 4 different Name Servers found: ns-1016.awsdns-63.net, ns-1291.awsdns-33.org, ns-1818.awsdns-35.co.uk, ns-64.awsdns-08.com, 4 Name Servers included in Delegation: ns-1016.awsdns-63.net, ns-1291.awsdns-33.org, ns-1818.awsdns-35.co.uk, ns-64.awsdns-08.com, 4 Name Servers included in 1 Zone definitions: ns-1016.awsdns-63.net, ns-1291.awsdns-33.org, ns-1818.awsdns-35.co.uk, ns-64.awsdns-08.com, 1 Name Servers listed in SOA.Primary: ns-1818.awsdns-35.co.uk. A Good: Only one SOA.Primary Name Server found.: ns-1818.awsdns-35.co.uk. A Good: SOA.Primary Name Server included in the delegation set.: ns-1818.awsdns-35.co.uk. 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-1016.awsdns-63.net, ns-1291.awsdns-33.org, ns-1818.awsdns-35.co.uk, ns-64.awsdns-08.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 Good: Minimal 2 different name servers (public suffix and public ip address) found: 4 different Name Servers found A Good: All name servers have ipv4- and ipv6-addresses.: 4 different Name Servers found A Good: Name servers with different Top Level Domains / Public Suffix List entries found: 4 Name Servers, 4 Top Level Domains: org, net, com, co.uk A Good: Name Servers with different domain names found.: 4 different Domains found A Good: Name servers with different Country locations found: 4 Name Servers, 3 Countries: GB, IE, US A Info: Ipv4-Subnet-list: 4 Name Servers, 1 different subnets (first Byte): 205., 1 different subnets (first two Bytes): 205.251., 4 different subnets (first three Bytes): 205.251.192., 205.251.195., 205.251.197., 205.251.199. A Good: Name Server IPv4-addresses from different subnet found: A Info: IPv6-Subnet-list: 4 Name Servers with IPv6, 1 different subnets (first block): 2600:, 1 different subnets (first two blocks): 2600:9000:, 4 different subnets (first three blocks): 2600:9000:5300:, 2600:9000:5303:, 2600:9000:5305:, 2600:9000:5307:, 4 different subnets (first four blocks): 2600:9000:5300:4000:, 2600:9000:5303:f800:, 2600:9000:5305:0b00:, 2600:9000:5307:1a00: 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-1818.awsdns-35.co.uk: 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. http://wiki.aakkal.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2406:da1a:ea0:a900:27e4:4de2:c01d:f336, Status 404 http://wiki.aakkal.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 3.6.47.120, Status 301 Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. A Good: Every https result with status 200 supports GZip. https://wiki.aakkal.com/ 3.6.47.120 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://wiki.aakkal.com/ 2406:da1a:ea0:a900:27e4:4de2:c01d:f336 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://3.6.47.120/ 3.6.47.120 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://[2406:da1a:0ea0:a900:27e4:4de2:c01d:f336]/ 2406:da1a:ea0:a900:27e4:4de2:c01d:f336 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://wiki.aakkal.com/ 3.6.47.120 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://wiki.aakkal.com/ 2406:da1a:ea0:a900:27e4:4de2:c01d:f336 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://3.6.47.120/ 3.6.47.120 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://[2406:da1a:0ea0:a900:27e4:4de2:c01d:f336]/ 2406:da1a:ea0:a900:27e4:4de2:c01d:f336 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://wiki.aakkal.com/ 3.6.47.120 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://wiki.aakkal.com/ 2406:da1a:ea0:a900:27e4:4de2:c01d:f336 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://3.6.47.120/ 3.6.47.120 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://[2406:da1a:0ea0:a900:27e4:4de2:c01d:f336]/ 2406:da1a:ea0:a900:27e4:4de2:c01d:f336 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. A Good: All script Elements (type text/javascript) and src-Attribute have a defer / async - Attribute. So loading and executing these JavaScripts doesn't block parsing and rendering the Html-Output. Warning: CSS / JavaScript found without GZip support. Send these ressources with GZip. 2 external CSS / JavaScript files without GZip found - 0 with GZip, 2 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. 3 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. 0 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 2 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 2 complete. Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 4 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, 4 complete. A Good: All checked attribute values are enclosed in quotation marks (" or '). 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 https://wiki.aakkal.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.077 seconds Warning: 404 needs more then one second A Duration: 325437 milliseconds, 325.437 seconds