| 1. General Results, most used to calculate the result |
| A | name "jshelter.org" is domain, public suffix is ".org", top-level-domain is ".org", top-level-domain-type is "generic", tld-manager is "Public Interest Registry (PIR)", num .org-domains preloaded: 9857 (complete: 263653)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: jshelter.org has 2 different ip addresses (authoritative).
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: jshelter.org 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: 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, 63072000 seconds = 730 days
|
| A | Good: HSTS has includeSubdomains - directive
|
| A | Good: HSTS has preload directive
|
| Warning: HSTS preload sent, but not in Preload-List. Never send a preload directive if you don't know what preload means. Check https://hstspreload.org/ to learn the basics about the Google-Preload list. If you send a preload directive, you should **immediately** add your domain to the HSTS preload list via https://hstspreload.org/ . If Google accepts the domain, so the status is "pending": Note that new entries are hardcoded into the Chrome source code and can take several months before they reach the stable version. So you will see this message some months. If you don't want that or if you don't understand "preload", but if you send a preload directive and if you have correct A-redirects, everybody can add your domain to that list. Then you may have problems, it's not easy to undo that. So if you don't want your domain preloaded, remove the preload directive.
|
| 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):2 complete Content-Type - header (5 urls)
|
| https://jshelter.org/ 209.51.188.122
|
| Url with incomplete Content-Type - header - missing charset
|
| https://jshelter.org/ 2001:470:142:5::122
|
| Url with incomplete Content-Type - header - missing charset
|
| https://[2001:0470:0142:0005:0000:0000:0000:0122]/ 2001:470:142:5::122
|
| Url with incomplete Content-Type - header - missing charset
|
| A | http://jshelter.org/ 209.51.188.122
| https://jshelter.org/
| Correct redirect http - https with the same domain name
|
| A | http://jshelter.org/ 2001:470:142:5::122
| https://jshelter.org/
| Correct redirect http - https with the same domain name
|
| M | https://209.51.188.122/ 209.51.188.122
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| N | https://209.51.188.122/ 209.51.188.122
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://[2001:0470:0142:0005:0000:0000:0000:0122]/ 2001:470:142:5::122
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| X | Fatal error: Nameserver doesn't support TCP connection: ns3.gnu.org / 185.199.142.2: Timeout
|
| 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 jshelter.org, 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.jshelter.org
|
| 2. Header-Checks |
| A | jshelter.org 209.51.188.122
| Content-Security-Policy
| Ok: Header without syntax errors found: default-src 'self'; script-src 'self' 'sha256-XcekRgC6IqZmWUfd21hma2Twizx9ceHoJ2nKkJkVMnQ=' 'sha256-cLerpyKredEFcNK76FKn4HOPzC4GCYoXuOphZAkJBRc=' 'sha256-lEHSCl3Bp9hezPDur2btOJ1k6m+ceT/bihJvy+bsUBQ=' 'unsafe-inline'; object-src 'none'; frame-ancestors 'none';
|
| A |
|
| Good: default-src directive only with 'none' or 'self', additional sources are blocked.
|
| A |
|
| Good: default-src without 'unsafe-inline' or 'unsave-eval'.
|
| E |
|
| Bad: No form-action directive found. Use one to limit the form - action - destinations. form-action is a navigation-directive, so default-src isn't used.
|
| A |
|
| Good: frame-ancestors directive found. That limits pages who are allowed to use this page in a frame / iframe / object / embed / applet. frame-ancestors is a navigation-directive, so default-src isn't used.
|
| E |
|
| Bad: No base-uri directive found. Use one to limit the URLs which can be used in a document's <base> element. Because it's a document directive, default-src isn't used, so an own directive is required.
|
| A |
|
| Good: object-src only with 'none' or 'self' found, no scheme, no other urls. That blocks object / embed / applet - elements.
|
| F |
|
| Critical: script-src with 'unsafe-inline' or 'unsafe-eval' and without a nonce found. That's dangerous, don't use it. If you really need one of these unsafe directives, add a nonce.
|
| A |
|
| Good: script-src without * and a scheme found.
|
| A |
|
| Good: script-src without data: schema found. Why is this important? The data: schema allows hidden code injection. Insert <script src='data:application/javascript;base64,YWxlcnQoJ1hTUycpOw=='></script> in your page and see what happens.
|
| A |
|
| Good: frame-src without data: defined or frame-src missing and the default-src used as fallback not allows the data: schema. That blocks hidden code injection. Insert <iframe src="data:text/html;charset=utf-8;base64,PCFET0NUWVBFIGh0bWw+PGh0bWw+PGJvZHk+PHA+YmVmb3JlPHNjcmlwdCB0eXBlPSJ0ZXh0L2phdmFzY3JpcHQiPmFsZXJ0KCdYU1MnKTwvc2NyaXB0PjxwPmFmdGVyPC9ib2R5PjwvaHRtbD4="></iframe> in your page and see what happens.
|
| A |
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
| A |
| Referrer-Policy
| Ok: Header without syntax errors found: no-referrer
|
| A |
| Permissions-Policy
| Ok: Header without syntax errors found: browsing-topics=(), interest-cohort=()
|
| 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 | jshelter.org 2001:470:142:5::122
| Content-Security-Policy
| Ok: Header without syntax errors found: default-src 'self'; script-src 'self' 'sha256-XcekRgC6IqZmWUfd21hma2Twizx9ceHoJ2nKkJkVMnQ=' 'sha256-cLerpyKredEFcNK76FKn4HOPzC4GCYoXuOphZAkJBRc=' 'sha256-lEHSCl3Bp9hezPDur2btOJ1k6m+ceT/bihJvy+bsUBQ=' 'unsafe-inline'; object-src 'none'; frame-ancestors 'none';
|
| A |
|
| Good: default-src directive only with 'none' or 'self', additional sources are blocked.
|
| A |
|
| Good: default-src without 'unsafe-inline' or 'unsave-eval'.
|
| E |
|
| Bad: No form-action directive found. Use one to limit the form - action - destinations. form-action is a navigation-directive, so default-src isn't used.
|
| A |
|
| Good: frame-ancestors directive found. That limits pages who are allowed to use this page in a frame / iframe / object / embed / applet. frame-ancestors is a navigation-directive, so default-src isn't used.
|
| E |
|
| Bad: No base-uri directive found. Use one to limit the URLs which can be used in a document's <base> element. Because it's a document directive, default-src isn't used, so an own directive is required.
|
| A |
|
| Good: object-src only with 'none' or 'self' found, no scheme, no other urls. That blocks object / embed / applet - elements.
|
| F |
|
| Critical: script-src with 'unsafe-inline' or 'unsafe-eval' and without a nonce found. That's dangerous, don't use it. If you really need one of these unsafe directives, add a nonce.
|
| A |
|
| Good: script-src without * and a scheme found.
|
| A |
|
| Good: script-src without data: schema found. Why is this important? The data: schema allows hidden code injection. Insert <script src='data:application/javascript;base64,YWxlcnQoJ1hTUycpOw=='></script> in your page and see what happens.
|
| A |
|
| Good: frame-src without data: defined or frame-src missing and the default-src used as fallback not allows the data: schema. That blocks hidden code injection. Insert <iframe src="data:text/html;charset=utf-8;base64,PCFET0NUWVBFIGh0bWw+PGh0bWw+PGJvZHk+PHA+YmVmb3JlPHNjcmlwdCB0eXBlPSJ0ZXh0L2phdmFzY3JpcHQiPmFsZXJ0KCdYU1MnKTwvc2NyaXB0PjxwPmFmdGVyPC9ib2R5PjwvaHRtbD4="></iframe> in your page and see what happens.
|
| A |
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
| A |
| Referrer-Policy
| Ok: Header without syntax errors found: no-referrer
|
| A |
| Permissions-Policy
| Ok: Header without syntax errors found: browsing-topics=(), interest-cohort=()
|
| 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.
|
| B | jshelter.org 209.51.188.122
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | jshelter.org 209.51.188.122
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | jshelter.org 209.51.188.122
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| B | jshelter.org 2001:470:142:5::122
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | jshelter.org 2001:470:142:5::122
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | jshelter.org 2001:470:142:5::122
| 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.gnu.org (192.99.37.66, 2607:5300:60:4c42::1), ns2.gnu.org (192.99.35.98, 2607:5300:60:4a62::1), ns3.gnu.org (219.117.250.214, 240b:10:f00:1b00::310), ns4.gnu.org (188.165.235.157, 2001:41d0:2:b69d::1)
|
| 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.gnu.org, ns2.gnu.org, ns3.gnu.org, ns4.gnu.org, 4 Name Servers included in Delegation: ns1.gnu.org, ns2.gnu.org, ns3.gnu.org, ns4.gnu.org, 4 Name Servers included in 2 Zone definitions: ns1.gnu.org, ns2.gnu.org, ns3.gnu.org, ns4.gnu.org, 1 Name Servers listed in SOA.Primary: ns1.gnu.org.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.gnu.org.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.gnu.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: 4 different Name Servers found
|
| A | Good: Some Name Servers have IPv6 addresses: 3 Name Servers with IPv6 found (1 Name Servers without IPv6)
|
| 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: org
|
| 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: gnu.org
|
| A | Good: Name servers with different Country locations found: 4 Name Servers, 3 Countries: CA, DE, FR
|
| A | Info: Ipv4-Subnet-list: 4 Name Servers, 3 different subnets (first Byte): 185., 188., 192., 3 different subnets (first two Bytes): 185.199., 188.165., 192.99., 4 different subnets (first three Bytes): 185.199.142., 188.165.235., 192.99.35., 192.99.37.
|
| 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:, 2607:, 2 different subnets (first two blocks): 2001:41d0:, 2607:5300:, 2 different subnets (first three blocks): 2001:41d0:0002:, 2607:5300:0060:, 3 different subnets (first four blocks): 2001:41d0:0002:b69d:, 2607:5300:0060:4a62:, 2607:5300:0060:4c42:
|
| A | Good: Name Server IPv6 addresses from different subnets found.
|
| X | Nameserver Timeout checking Echo Capitalization: ns3.gnu.org / 185.199.142.2
|
| X | Nameserver Timeout checking EDNS512: ns3.gnu.org / 185.199.142.2
|
| 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 and greater 1024 Bytes is compressed (gzip, deflate, br checked).
|
| https://jshelter.org/ 209.51.188.122
|
| 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://jshelter.org/ 2001:470:142:5::122
|
| 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://[2001:0470:0142:0005:0000:0000:0000:0122]/ 2001:470:142:5::122
|
| 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://jshelter.org/ 209.51.188.122
|
| 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://jshelter.org/ 2001:470:142:5::122
|
| 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://[2001:0470:0142:0005:0000:0000:0000:0122]/ 2001:470:142:5::122
|
| 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 | 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
|
| http://jshelter.org/ 209.51.188.122
|
| Warning: HSTS header sent via http has no effect
|
| http://jshelter.org/ 2001:470:142:5::122
|
| Warning: HSTS header sent via http has no effect
|
| https://jshelter.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| 3.967 seconds
| Warning: 404 needs more then one second
|
| A | Duration: 294243 milliseconds, 294.243 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)