|
|
| 1. General Results, most used to calculate the result |
| A | name "private.coffee" is domain, public suffix is ".coffee", top-level-domain is ".coffee", top-level-domain-type is "generic", tld-manager is "Binky Moon, LLC", num .coffee-domains preloaded: 32 (complete: 276475)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: private.coffee has 2 different ip addresses (authoritative).
|
| A | Good: Minimal 2 ip addresses per domain name found: www.private.coffee has 2 different ip addresses (authoritative).
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: private.coffee has 1 ipv4, 1 ipv6 addresses
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: www.private.coffee has 1 ipv4, 1 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: non-www is preferred
|
| A | Good: No cookie sent via http.
|
| A | Excellent: Domain is in the Google-Preload-List
|
| A | Excellent: Domain is in the Mozilla/Firefox-Preload-List
|
| A | Good: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
|
| A | http://private.coffee/ 195.20.104.17
| https://private.coffee/
| Correct redirect http - https with the same domain name
|
| A | http://private.coffee/ 2a0c:b641:d10:117::1
| https://private.coffee/
| Correct redirect http - https with the same domain name
|
| A | http://www.private.coffee/ 195.20.104.17
| https://www.private.coffee/
| Correct redirect http - https with the same domain name
|
| A | http://www.private.coffee/ 2a0c:b641:d10:117::1
| https://www.private.coffee/
| Correct redirect http - https with the same domain name
|
| B | https://private.coffee/ 195.20.104.17
|
| Missing HSTS-Header
|
| B | https://private.coffee/ 2a0c:b641:d10:117::1
|
| Missing HSTS-Header
|
| B | https://www.private.coffee/ 195.20.104.17
|
| Missing HSTS-Header
|
| B | https://www.private.coffee/ 2a0c:b641:d10:117::1
|
| Missing HSTS-Header
|
| 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 private.coffee, 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.private.coffee, 2 ip addresses.
|
| Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain private.coffee, 2 ip addresses.
|
| Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain www.private.coffee, 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.private.coffee
|
| 2. Header-Checks |
| A | private.coffee 195.20.104.17
| Referrer-Policy
| Ok: Header without syntax errors found: strict-origin-when-cross-origin
|
| A | private.coffee 2a0c:b641:d10:117::1
| Referrer-Policy
| Ok: Header without syntax errors found: strict-origin-when-cross-origin
|
| F | private.coffee 195.20.104.17
| Content-Security-Policy
| Critical: Missing Header:
|
| F | private.coffee 195.20.104.17
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | private.coffee 195.20.104.17
| Permissions-Policy
| Critical: Missing Header:
|
| B | private.coffee 195.20.104.17
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | private.coffee 195.20.104.17
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | private.coffee 195.20.104.17
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| F | private.coffee 2a0c:b641:d10:117::1
| Content-Security-Policy
| Critical: Missing Header:
|
| F | private.coffee 2a0c:b641:d10:117::1
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | private.coffee 2a0c:b641:d10:117::1
| Permissions-Policy
| Critical: Missing Header:
|
| B | private.coffee 2a0c:b641:d10:117::1
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | private.coffee 2a0c:b641:d10:117::1
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | private.coffee 2a0c:b641:d10:117::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 2 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.private.coffee (2a0d:f302:112:63b::1, 46.102.156.21), ns2.private.coffee (2a00:63c1:10:37::2, 37.252.191.37)
|
| A | Good (1 - 3.0):: An average of 1.0 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 2 different Name Servers found: ns1.private.coffee, ns2.private.coffee, 2 Name Servers included in Delegation: ns1.private.coffee, ns2.private.coffee, 2 Name Servers included in 1 Zone definitions: ns1.private.coffee, ns2.private.coffee, 1 Name Servers listed in SOA.Primary: ns1.private.coffee.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.private.coffee.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.private.coffee.
|
| 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.private.coffee, ns2.private.coffee
|
| 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: 2 different Name Servers found
|
| A | Good: All name servers have ipv4- and ipv6-addresses.: 2 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.: 2 Name Servers, 1 Top Level Domain: coffee
|
| 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: private.coffee
|
| Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: AT
|
| A | Info: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 37., 46., 2 different subnets (first two Bytes): 37.252., 46.102., 2 different subnets (first three Bytes): 37.252.191., 46.102.156.
|
| A | Excellent: Every Name Server IPv4-address starts with an unique Byte.
|
| A | Info: IPv6-Subnet-list: 2 Name Servers with IPv6, 2 different subnets (first block): 2a00:, 2a0d:, 2 different subnets (first two blocks): 2a00:63c1:, 2a0d:f302:, 2 different subnets (first three blocks): 2a00:63c1:0010:, 2a0d:f302:0112:, 2 different subnets (first four blocks): 2a00:63c1:0010:0037:, 2a0d:f302:0112:063b:
|
| A | Excellent: Every Name Server IPv6-address starts with an unique Hex-block
|
| A | Good: Nameserver supports TCP connections: 4 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 4 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 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 wildcard-certificates
|
| 4. Content- and Performance-critical Checks |
| http://private.coffee/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 195.20.104.17
|
| 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://private.coffee/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a0c:b641:d10:117::1
|
| 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.private.coffee/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 195.20.104.17
|
| 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.private.coffee/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a0c:b641:d10:117::1
|
| 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.
|
| https://private.coffee/ 195.20.104.17
|
| Warning: https result with status 200 and size greater then 1024 Bytes without Compression found. Add Compression support (gzip, deflate, br - these are checked) so the html content is compressed.
|
| https://private.coffee/ 2a0c:b641:d10:117::1
|
| Warning: https result with status 200 and size greater then 1024 Bytes without Compression found. Add Compression support (gzip, deflate, br - these are checked) so the html content is compressed.
|
| A | Good: No https + http status 200 with inline CSS / JavaScript found
|
| https://private.coffee/ 195.20.104.17
|
| 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://private.coffee/ 2a0c:b641:d10:117::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.
|
| https://private.coffee/ 195.20.104.17
|
| Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 1 script elements without defer/async.
|
| https://private.coffee/ 2a0c:b641:d10:117::1
|
| Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 1 script elements without defer/async.
|
| Warning: CSS / JavaScript found without Compression. Compress these ressources, gzip, deflate, br are checked. 8 external CSS / JavaScript files without Compression found - 0 with Compression, 8 complete
|
| 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, 10 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 10 complete.
|
| Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 0 image 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 ').
|
| Wrong: img-elements without alt-attribute or empty alt-attribute found. The alt-attribute ("alternative") is required and should describe the img. So Screenreader and search engines are able to use these informations.: 2 img-elements without alt-attribute, 0 img-elements with empty alt-attribute 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
|
| A | Duration: 320310 milliseconds, 320.310 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)