| 1. General Results, most used to calculate the result |
| A | name "tiekoetter.net" is domain, public suffix is ".net", top-level-domain is ".net", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .net-domains preloaded: 10583 (complete: 276475)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: tiekoetter.net has 3 different ip addresses (authoritative).
|
| A | Good: Minimal 2 ip addresses per domain name found: www.tiekoetter.net has 3 different ip addresses (authoritative).
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: tiekoetter.net has 1 ipv4, 2 ipv6 addresses
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: www.tiekoetter.net has 1 ipv4, 2 ipv6 addresses
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | Good: destination is https
|
| A | Good - only one version with Http-Status 200
|
| A | Good: one preferred version: 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):0 complete Content-Type - header (9 urls)
|
| https://www.tiekoetter.net/ 152.53.125.158
|
| Url with incomplete Content-Type - header - missing charset
|
| https://www.tiekoetter.net/ 2a0a:4cc0:c0:5013::1
|
| Url with incomplete Content-Type - header - missing charset
|
| https://www.tiekoetter.net/ 2a0c:9a40:8820:feed::1
|
| Url with incomplete Content-Type - header - missing charset
|
| https://www.tiekoetter.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Url with incomplete Content-Type - header - missing charset
|
| https://152.53.125.158/ 152.53.125.158
|
| Url with incomplete Content-Type - header - missing charset
|
| https://[2a0a:4cc0:00c0:5013:0000:0000:0000:0001]/ 2a0a:4cc0:c0:5013::1
|
| Url with incomplete Content-Type - header - missing charset
|
| https://[2a0c:9a40:8820:feed:0000:0000:0000:0001]/ 2a0c:9a40:8820:feed::1
|
| Url with incomplete Content-Type - header - missing charset
|
| https://mta-sts.tiekoetter.net/.well-known/mta-sts.txt 152.53.125.158
|
| Url with incomplete Content-Type - header - missing charset
|
| https://mta-sts.tiekoetter.net/.well-known/mta-sts.txt 2a0a:4cc0:c0:5013::1
|
| Url with incomplete Content-Type - header - missing charset
|
| A | http://www.tiekoetter.net/ 152.53.125.158
| https://www.tiekoetter.net/
| Correct redirect http - https with the same domain name
|
| A | http://www.tiekoetter.net/ 2a0a:4cc0:c0:5013::1
| https://www.tiekoetter.net/
| Correct redirect http - https with the same domain name
|
| A | http://www.tiekoetter.net/ 2a0c:9a40:8820:feed::1
| https://www.tiekoetter.net/
| Correct redirect http - https with the same domain name
|
| B | https://tiekoetter.net/ 152.53.125.158
|
| Missing HSTS-Header
|
| B | https://tiekoetter.net/ 2a0a:4cc0:c0:5013::1
|
| Missing HSTS-Header
|
| B | https://tiekoetter.net/ 2a0c:9a40:8820:feed::1
|
| Missing HSTS-Header
|
| B | https://www.tiekoetter.net/ 152.53.125.158
|
| Missing HSTS-Header
|
| B | https://www.tiekoetter.net/ 2a0a:4cc0:c0:5013::1
|
| Missing HSTS-Header
|
| B | https://www.tiekoetter.net/ 2a0c:9a40:8820:feed::1
|
| Missing HSTS-Header
|
| B | https://www.tiekoetter.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Missing HSTS-Header
|
| E | http://tiekoetter.net/ 152.53.125.158
| https://www.tiekoetter.net/
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| E | http://tiekoetter.net/ 2a0a:4cc0:c0:5013::1
| https://www.tiekoetter.net/
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| E | http://tiekoetter.net/ 2a0c:9a40:8820:feed::1
| https://www.tiekoetter.net/
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| N | https://152.53.125.158/ 152.53.125.158
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://[2a0a:4cc0:00c0:5013:0000:0000:0000:0001]/ 2a0a:4cc0:c0:5013::1
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://[2a0c:9a40:8820:feed:0000:0000:0000:0001]/ 2a0c:9a40:8820:feed::1
|
| 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 tiekoetter.net, 3 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.tiekoetter.net, 3 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 tiekoetter.net, 3 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.tiekoetter.net, 3 ip addresses.
|
| A | Good: _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Domainname: _mta-sts.tiekoetter.net
|
| A | Good: _mta-sts TXT record is valid.
|
| A | Good: Subdomain mta-sts found: Subdomain-name: mta-sts.tiekoetter.net, ip : 152.53.125.158
|
| A | Good: Subdomain mta-sts found: Subdomain-name: mta-sts.tiekoetter.net, ip : 2a0a:4cc0:c0:5013::1
|
| A | Good: Certificate of subdomain is valid. mta-sts.tiekoetter.net, ip : 152.53.125.158
|
| A | Good: Certificate of subdomain is valid. mta-sts.tiekoetter.net, ip : 2a0a:4cc0:c0:5013::1
|
| A | Good: /.well-known/mta-sts.txt with http status 200 found. Complete path: https://mta-sts.tiekoetter.net/.well-known/mta-sts.txt - ip : 152.53.125.158
|
| A | Good: /.well-known/mta-sts.txt with http status 200 found. Complete path: https://mta-sts.tiekoetter.net/.well-known/mta-sts.txt - ip : 2a0a:4cc0:c0:5013::1
|
| A | Good: mta-sts.txt has the required names "version", "mode", "max_age". mta-sts.tiekoetter.net, ip : 152.53.125.158
|
| A | Good: mta-sts.txt has the required names "version", "mode", "max_age". mta-sts.tiekoetter.net, ip : 2a0a:4cc0:c0:5013::1
|
| A | Good: Minimal one mx definition found. mta-sts.tiekoetter.net, ip : 152.53.125.158
|
| A | Good: Minimal one mx definition found. mta-sts.tiekoetter.net, ip : 2a0a:4cc0:c0:5013::1
|
| A | Excellent: Complete and valid MTA-STS found!
|
| 2. Header-Checks |
| A | www.tiekoetter.net 152.53.125.158
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
| 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
|
| A | www.tiekoetter.net 2a0a:4cc0:c0:5013::1
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
| 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
|
| A | www.tiekoetter.net 2a0c:9a40:8820:feed::1
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
| 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 | www.tiekoetter.net 152.53.125.158
| Content-Security-Policy
| Critical: Missing Header:
|
| F | www.tiekoetter.net 152.53.125.158
| Referrer-Policy
| Critical: Missing Header:
|
| F | www.tiekoetter.net 152.53.125.158
| Permissions-Policy
| Critical: Missing Header:
|
| B | www.tiekoetter.net 152.53.125.158
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | www.tiekoetter.net 152.53.125.158
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | www.tiekoetter.net 152.53.125.158
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| F | www.tiekoetter.net 2a0a:4cc0:c0:5013::1
| Content-Security-Policy
| Critical: Missing Header:
|
| F | www.tiekoetter.net 2a0a:4cc0:c0:5013::1
| Referrer-Policy
| Critical: Missing Header:
|
| F | www.tiekoetter.net 2a0a:4cc0:c0:5013::1
| Permissions-Policy
| Critical: Missing Header:
|
| B | www.tiekoetter.net 2a0a:4cc0:c0:5013::1
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | www.tiekoetter.net 2a0a:4cc0:c0:5013::1
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | www.tiekoetter.net 2a0a:4cc0:c0:5013::1
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| F | www.tiekoetter.net 2a0c:9a40:8820:feed::1
| Content-Security-Policy
| Critical: Missing Header:
|
| F | www.tiekoetter.net 2a0c:9a40:8820:feed::1
| Referrer-Policy
| Critical: Missing Header:
|
| F | www.tiekoetter.net 2a0c:9a40:8820:feed::1
| Permissions-Policy
| Critical: Missing Header:
|
| B | www.tiekoetter.net 2a0c:9a40:8820:feed::1
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | www.tiekoetter.net 2a0c:9a40:8820:feed::1
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | www.tiekoetter.net 2a0c:9a40:8820:feed::1
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
|
| A | Info:: 2 Queries complete, 2 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.ns1.tiekoetter.net (2a03:4000:46:8ca::1, 45.83.107.43), ns2.tiekoetter.net (185.194.141.200, 2a03:4000:1c:d2c::2), ns3.tiekoetter.net (2a01:4f9:c012:68fb::1, 95.217.221.144), ns4.tiekoetter.net (2a03:b0c0:2:f0::35c:3001, 64.225.78.55)
|
| A | Good (1 - 3.0):: An average of 0.5 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 4 different Name Servers found: ns1.tiekoetter.net, ns2.tiekoetter.net, ns3.tiekoetter.net, ns4.tiekoetter.net, 4 Name Servers included in Delegation: ns1.tiekoetter.net, ns2.tiekoetter.net, ns3.tiekoetter.net, ns4.tiekoetter.net, 4 Name Servers included in 1 Zone definitions: ns1.tiekoetter.net, ns2.tiekoetter.net, ns3.tiekoetter.net, ns4.tiekoetter.net, 1 Name Servers listed in SOA.Primary: ns1.tiekoetter.net.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.tiekoetter.net.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.tiekoetter.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: ns1.tiekoetter.net, ns2.tiekoetter.net, ns3.tiekoetter.net, ns4.tiekoetter.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: 4 different Name Servers found
|
| A | Good: All name servers have ipv4- and ipv6-addresses.: 4 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.: 4 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: tiekoetter.net
|
| A | Good: Name servers with different Country locations found: 4 Name Servers, 3 Countries: DE, FI, NL
|
| A | Info: Ipv4-Subnet-list: 4 Name Servers, 4 different subnets (first Byte): 185., 45., 64., 95., 4 different subnets (first two Bytes): 185.194., 45.83., 64.225., 95.217., 4 different subnets (first three Bytes): 185.194.141., 45.83.107., 64.225.78., 95.217.221.
|
| A | Excellent: Every Name Server IPv4-address starts with an unique Byte.
|
| A | Info: IPv6-Subnet-list: 4 Name Servers with IPv6, 2 different subnets (first block): 2a01:, 2a03:, 3 different subnets (first two blocks): 2a01:04f9:, 2a03:4000:, 2a03:b0c0:, 4 different subnets (first three blocks): 2a01:04f9:c012:, 2a03:4000:001c:, 2a03:4000:0046:, 2a03:b0c0:0002:, 4 different subnets (first four blocks): 2a01:04f9:c012:68fb:, 2a03:4000:001c:0d2c:, 2a03:4000:0046:08ca:, 2a03:b0c0:0002:00f0:
|
| A | Good: Name Server IPv6 addresses from different subnets found.
|
| A | Good: Nameserver supports TCP connections: 8 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 8 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
|
| A | Good: All SOA have the same Serial Number
|
| A | Good: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates
|
| A | Good: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create wildcard-certificates
|
| 4. Content- and Performance-critical Checks |
| https://www.tiekoetter.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. 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://152.53.125.158/ 152.53.125.158
|
| 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://[2a0a:4cc0:00c0:5013:0000:0000:0000:0001]/ 2a0a:4cc0:c0:5013::1
|
| 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://[2a0c:9a40:8820:feed:0000:0000:0000:0001]/ 2a0c:9a40:8820:feed::1
|
| 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 | 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: 110060 milliseconds, 110.060 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)