| 1. General Results, most used to calculate the result |
| A | name "illigs.de" is domain, 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: 9989 (complete: 251685)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: illigs.de has 2 different ip addresses (authoritative).
|
| A | Good: Minimal 2 ip addresses per domain name found: www.illigs.de has 2 different ip addresses (authoritative).
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: illigs.de has 1 ipv4, 1 ipv6 addresses
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: www.illigs.de has 1 ipv4, 1 ipv6 addresses
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | Good: destination is https
|
| 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):0 complete Content-Type - header (5 urls)
|
| https://illigs.de/ 202.61.233.90
|
| Url with incomplete Content-Type - header - missing charset
|
| https://www.illigs.de/ 202.61.233.90
|
| Url with incomplete Content-Type - header - missing charset
|
| https://illigs.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Url with incomplete Content-Type - header - missing charset
|
| https://www.illigs.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Url with incomplete Content-Type - header - missing charset
|
| https://202.61.233.90/ 202.61.233.90
|
| Url with incomplete Content-Type - header - missing charset
|
| A | http://illigs.de/ 202.61.233.90
| https://illigs.de/
| Correct redirect http - https with the same domain name
|
| A | http://www.illigs.de/ 202.61.233.90
| https://www.illigs.de/
| Correct redirect http - https with the same domain name
|
| B | https://illigs.de/ 202.61.233.90
|
| Missing HSTS-Header
|
| B | https://www.illigs.de/ 202.61.233.90
|
| Missing HSTS-Header
|
| B | https://illigs.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Missing HSTS-Header
|
| B | https://www.illigs.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Missing HSTS-Header
|
| 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.
|
| K | http://illigs.de/ 202.61.233.90, Status 301
| http://illigs.de/ 2a03:4000:61:9eeb::20:9502, Status -102
| Configuration problem - different ip addresses with different status
|
| K | http://www.illigs.de/ 202.61.233.90, Status 301
| http://www.illigs.de/ 2a03:4000:61:9eeb::20:9502, Status -102
| Configuration problem - different ip addresses with different status
|
| K | https://illigs.de/ 202.61.233.90, Status 200
| https://illigs.de/ 2a03:4000:61:9eeb::20:9502, Status -102
| Configuration problem - different ip addresses with different status
|
| K | https://www.illigs.de/ 202.61.233.90, Status 200
| https://www.illigs.de/ 2a03:4000:61:9eeb::20:9502, Status -102
| Configuration problem - different ip addresses with different status
|
| K | http://illigs.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 202.61.233.90, Status 301
| http://illigs.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a03:4000:61:9eeb::20:9502, Status -102
| Configuration problem - different ip addresses with different status
|
| K | http://www.illigs.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 202.61.233.90, Status 301
| http://www.illigs.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a03:4000:61:9eeb::20:9502, Status -102
| Configuration problem - different ip addresses with different status
|
| N | https://illigs.de/ 202.61.233.90
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://www.illigs.de/ 202.61.233.90
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://illigs.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://www.illigs.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://202.61.233.90/ 202.61.233.90
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | illigs.de:8443
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | illigs.de:8443
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | www.illigs.de:8443
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | www.illigs.de:8443
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| O | illigs.de / 202.61.233.90 / 443
|
| Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 16 Cipher Suites without Forward Secrecy found
|
| O | illigs.de / 202.61.233.90 / 8443
|
| Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 16 Cipher Suites without Forward Secrecy found
|
| O | illigs.de / 2a03:4000:61:9eeb::20:9502 / 8443
|
| Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 16 Cipher Suites without Forward Secrecy found
|
| O | www.illigs.de / 202.61.233.90 / 443
|
| Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 16 Cipher Suites without Forward Secrecy found
|
| O | www.illigs.de / 202.61.233.90 / 8443
|
| Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 16 Cipher Suites without Forward Secrecy found
|
| O | www.illigs.de / 2a03:4000:61:9eeb::20:9502 / 8443
|
| Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 16 Cipher Suites without Forward Secrecy found
|
| V | http://illigs.de/ 2a03:4000:61:9eeb::20:9502
|
| Connect failure - perhaps firewall
|
| V | http://www.illigs.de/ 2a03:4000:61:9eeb::20:9502
|
| Connect failure - perhaps firewall
|
| V | https://illigs.de/ 2a03:4000:61:9eeb::20:9502
|
| Connect failure - perhaps firewall
|
| V | https://www.illigs.de/ 2a03:4000:61:9eeb::20:9502
|
| Connect failure - perhaps firewall
|
| V | http://illigs.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a03:4000:61:9eeb::20:9502
|
| Connect failure - perhaps firewall
|
| V | http://www.illigs.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a03:4000:61:9eeb::20:9502
|
| Connect failure - perhaps firewall
|
| V | https://[2a03:4000:0061:9eeb:0000:0000:0020:9502]/ 2a03:4000:61:9eeb::20:9502
|
| Connect failure - perhaps firewall
|
| 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 illigs.de, 2 ip addresses.
|
| 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 www.illigs.de, 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.illigs.de
|
| 2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05) |
| F | illigs.de 202.61.233.90
| Content-Security-Policy
| Critical: Missing Header:
|
| F | illigs.de 202.61.233.90
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | illigs.de 202.61.233.90
| Referrer-Policy
| Critical: Missing Header:
|
| F | illigs.de 202.61.233.90
| Permissions-Policy
| Critical: Missing Header:
|
| B | illigs.de 202.61.233.90
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | illigs.de 202.61.233.90
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | illigs.de 202.61.233.90
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| F | www.illigs.de 202.61.233.90
| Content-Security-Policy
| Critical: Missing Header:
|
| F | www.illigs.de 202.61.233.90
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | www.illigs.de 202.61.233.90
| Referrer-Policy
| Critical: Missing Header:
|
| F | www.illigs.de 202.61.233.90
| Permissions-Policy
| Critical: Missing Header:
|
| B | www.illigs.de 202.61.233.90
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | www.illigs.de 202.61.233.90
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | www.illigs.de 202.61.233.90
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 12 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
|
| A | Info:: 12 Queries complete, 12 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:: 3 different Name Servers found: root-dns.netcup.net, second-dns.netcup.net, third-dns.netcup.net, 3 Name Servers included in Delegation: root-dns.netcup.net, second-dns.netcup.net, third-dns.netcup.net, 3 Name Servers included in 1 Zone definitions: root-dns.netcup.net, second-dns.netcup.net, third-dns.netcup.net, 1 Name Servers listed in SOA.Primary: root-dns.netcup.net.
|
| A | Good: Only one SOA.Primary Name Server found.: root-dns.netcup.net.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: root-dns.netcup.net.
|
| 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: root-dns.netcup.net, second-dns.netcup.net, third-dns.netcup.net
|
| 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
|
| Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 3 Name Servers, 1 Top Level Domain: net
|
| Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: netcup.net
|
| Warning: All Name Servers from the same Country / IP location.: 3 Name Servers, 1 Countries: DE
|
| A | Info: Ipv4-Subnet-list: 3 Name Servers, 3 different subnets (first Byte): 188., 37., 46., 3 different subnets (first two Bytes): 188.68., 37.221., 46.38., 3 different subnets (first three Bytes): 188.68.63., 37.221.199., 46.38.225.
|
| A | Excellent: Every Name Server IPv4-address starts with an unique Byte.
|
| A | Info: IPv6-Subnet-list: 3 Name Servers with IPv6, 1 different subnets (first block): 2a03:, 2 different subnets (first two blocks): 2a03:4000:, 2a03:4001:, 3 different subnets (first three blocks): 2a03:4000:0000:, 2a03:4000:0002:, 2a03:4001:0000:, 3 different subnets (first four blocks): 2a03:4000:0000:0001:, 2a03:4000:0002:024b:, 2a03:4001:0000:0106:
|
| A | Good: Name Server IPv6 addresses from different subnets 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
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 6 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://illigs.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a03:4000:61:9eeb::20:9502
|
| Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. 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.illigs.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a03:4000:61:9eeb::20:9502
|
| Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. 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://illigs.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a03:4000:61:9eeb::20:9502, Status -102
| http://illigs.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 202.61.233.90, 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.
|
| http://www.illigs.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a03:4000:61:9eeb::20:9502, Status -102
| http://www.illigs.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 202.61.233.90, 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.
|
| https://illigs.de/ 202.61.233.90
|
| 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.illigs.de/ 202.61.233.90
|
| 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://202.61.233.90/ 202.61.233.90
|
| 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://illigs.de/ 202.61.233.90
|
| 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.illigs.de/ 202.61.233.90
|
| 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://202.61.233.90/ 202.61.233.90
|
| 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.
|
| A | Good: Every https connection via port 443 supports the http/2 protocol via ALPN.
|
| A | Good: All checked attribute values are enclosed in quotation marks (" or ').
|
| A | Info: No img element found, no alt attribute checked
|
| 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://illigs.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| 10.957 seconds
| Warning: 404 needs more then one second
|
| https://www.illigs.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| 10.930 seconds
| Warning: 404 needs more then one second
|
| A | Duration: 866817 milliseconds, 866.817 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)