| 1. General Results, most used to calculate the result |
| A | name "drei01.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: 8691 (complete: 216710)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: drei01.de has 2 different ip addresses (authoritative).
|
| A | Good: Minimal 2 ip addresses per domain name found: www.drei01.de has 2 different ip addresses (authoritative).
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: drei01.de has 1 ipv4, 1 ipv6 addresses
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: www.drei01.de has 1 ipv4, 1 ipv6 addresses
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | https://drei01.de/ 94.130.136.210
| https://drei01.de/de/
| Correct redirect https to https
|
| A | https://drei01.de/ 2a01:4f8:13b:332d::2
| https://drei01.de/de/
| Correct redirect https to https
|
| A | Good: destination is https
|
| A | Good - only one version with Http-Status 200
|
| A | Good: one preferred version: non-www is preferred
|
| A | Good: No cookie sent via http.
|
| A | Good: every https has a Strict Transport Security Header
|
| A | Good: HSTS max-age is long enough, 31536000 seconds = 365 days
|
| A | Good: HSTS has includeSubdomains - directive
|
| A | Good: HSTS has preload directive
|
| A | Excellent: Domain is in the Google-Preload-List
|
| A | Excellent: Domain is in the Mozilla/Firefox-Preload-List
|
| A | HSTS-Preload-Status: Preloaded. 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://drei01.de/ 94.130.136.210
| https://drei01.de/
| Correct redirect http - https with the same domain name
|
| A | http://drei01.de/ 2a01:4f8:13b:332d::2
| https://drei01.de/
| Correct redirect http - https with the same domain name
|
| A | http://www.drei01.de/ 94.130.136.210
| https://www.drei01.de/
| Correct redirect http - https with the same domain name
|
| A | http://www.drei01.de/ 2a01:4f8:13b:332d::2
| https://www.drei01.de/
| Correct redirect http - https with the same domain name
|
| N | https://94.130.136.210/ 94.130.136.210
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://[2a01:04f8:013b:332d:0000:0000:0000:0002]/ 2a01:4f8:13b:332d::2
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | www.drei01.de:25
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | www.drei01.de:25
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | drei01.de:25
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | drei01.de:25
|
| 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 drei01.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.drei01.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 different. So that domain requires Server Name Indication (SNI), so the server is able to select the correct certificate.: Domain drei01.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 different. So that domain requires Server Name Indication (SNI), so the server is able to select the correct certificate.: Domain www.drei01.de, 2 ip addresses.
|
| A | Good: _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Domainname: _mta-sts.drei01.de
|
| A | Good: _mta-sts TXT record is valid.
|
| A | Good: Subdomain mta-sts found: Subdomain-name: mta-sts.drei01.de, ip : 94.130.136.210
|
| A | Good: Subdomain mta-sts found: Subdomain-name: mta-sts.drei01.de, ip : 2a01:4f8:13b:332d::2
|
| A | Good: Certificate of subdomain is valid. mta-sts.drei01.de, ip : 94.130.136.210
|
| A | Good: Certificate of subdomain is valid. mta-sts.drei01.de, ip : 2a01:4f8:13b:332d::2
|
| A | Good: /.well-known/mta-sts.txt with http status 200 found. Complete path: https://mta-sts.drei01.de/.well-known/mta-sts.txt - ip : 94.130.136.210
|
| A | Good: /.well-known/mta-sts.txt with http status 200 found. Complete path: https://mta-sts.drei01.de/.well-known/mta-sts.txt - ip : 2a01:4f8:13b:332d::2
|
| A | Good: mta-sts.txt has the required names "version", "mode", "max_age". mta-sts.drei01.de, ip : 94.130.136.210
|
| A | Good: mta-sts.txt has the required names "version", "mode", "max_age". mta-sts.drei01.de, ip : 2a01:4f8:13b:332d::2
|
| A | Good: Minimal one mx definition found. mta-sts.drei01.de, ip : 94.130.136.210
|
| A | Good: Minimal one mx definition found. mta-sts.drei01.de, ip : 2a01:4f8:13b:332d::2
|
| A | Excellent: Complete and valid MTA-STS found!
|
| 2. Header-Checks |
| A | drei01.de
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
| A |
| Referrer-Policy
| Ok: Header without syntax errors found: strict-origin-when-cross-origin
|
| A |
| X-Frame-Options
| Ok: Header without syntax errors found: SAMEORIGIN
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. SAMEORIGIN. 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.
|
| A |
| X-Xss-Protection
| Ok: Header without syntax errors found: 1; mode=block
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. 1; mode=block
|
| F | drei01.de
| Content-Security-Policy
| Critical: Missing Header:
|
| F | drei01.de
| Permissions-Policy
| Critical: Missing Header:
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 11 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
|
| A | Info:: 11 Queries complete, 11 with IPv6, 0 with IPv4.
|
| A | Good: All DNS Queries done via IPv6.
|
| Ok (4 - 8):: An average of 3.7 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 3 different Name Servers found: ns1.first-ns.de, robotns2.second-ns.de, robotns3.second-ns.com, 3 Name Servers included in Delegation: ns1.first-ns.de, robotns2.second-ns.de, robotns3.second-ns.com, 3 Name Servers included in 1 Zone definitions: ns1.first-ns.de, robotns2.second-ns.de, robotns3.second-ns.com, 1 Name Servers listed in SOA.Primary: ns1.first-ns.de.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.first-ns.de.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.first-ns.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: ns1.first-ns.de, robotns2.second-ns.de, robotns3.second-ns.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: 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, 2 Top Level Domains: de, com
|
| A | Good: Name Servers with different domain names found.: 3 different Domains found
|
| Warning: All Name Servers from the same Country / IP location.: 3 Name Servers, 1 Countries: DE
|
| A | Info: Ipv4-Subnet-list: 3 Name Servers, 2 different subnets (first Byte): 193., 213., 3 different subnets (first two Bytes): 193.47., 213.133., 213.239., 3 different subnets (first three Bytes): 193.47.99., 213.133.105., 213.239.242.
|
| A | Good: Name Server IPv4-addresses from different subnet found:
|
| A | Info: IPv6-Subnet-list: 3 Name Servers with IPv6, 2 different subnets (first block): 2001:, 2a01:, 2 different subnets (first two blocks): 2001:067c:, 2a01:04f8:, 3 different subnets (first three blocks): 2001:067c:192c:, 2a01:04f8:0000:, 2a01:04f8:0d0a:, 3 different subnets (first four blocks): 2001:067c:192c:0000:, 2a01:04f8:0000:a101:, 2a01:04f8:0d0a:2004:
|
| A | Good: Name Server IPv6 addresses from different subnets found.
|
| A | Info: Nameserver mit different domain names found. May be a problem with DNS-Updates
|
| 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 |
| https://drei01.de/error/404.html
|
| Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| https://www.drei01.de/error/404.html
|
| Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| A | Good: Every https result with status 200 and greater 1024 Bytes is compressed (gzip, deflate, br checked).
|
| https://drei01.de/de/
|
| 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://94.130.136.210/ 94.130.136.210
|
| 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://[2a01:04f8:013b:332d:0000:0000:0000:0002]/ 2a01:4f8:13b:332d::2
|
| 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://94.130.136.210/ 94.130.136.210
|
| 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://[2a01:04f8:013b:332d:0000:0000:0000:0002]/ 2a01:4f8:13b:332d::2
|
| 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 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.
|
| A | Good: All CSS / JavaScript files are sent compressed (gzip, deflate, br checked). That reduces the content of the files. 2 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. 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.
|
| 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
|
| A | Duration: 545910 milliseconds, 545.910 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)