| 1. General Results, most used to calculate the result |
| A | name "onlyvideo.kozow.com" is domain, public suffix is ".kozow.com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 108094 (complete: 276475)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: onlyvideo.kozow.com has 2 different ip addresses (authoritative).
|
| A | Good: Minimal 2 ip addresses per domain name found: www.onlyvideo.kozow.com has 2 different ip addresses (authoritative).
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: onlyvideo.kozow.com has 1 ipv4, 1 ipv6 addresses
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: www.onlyvideo.kozow.com has 1 ipv4, 1 ipv6 addresses
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| 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: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
|
| D | http://localapp.kozow.com/
| http://zoo.kozow.com/
| Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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.
|
| D | http://onlyvideo.kozow.com/ 162.216.242.206
| http://localapp.kozow.com/
| Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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.
|
| D | http://onlyvideo.kozow.com/ 2602:ff23:0:8888::206
| http://localapp.kozow.com/
| Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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.
|
| D | http://www.onlyvideo.kozow.com/ 162.216.242.206
| http://localapp.kozow.com/
| Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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.
|
| D | http://www.onlyvideo.kozow.com/ 2602:ff23:0:8888::206
| http://localapp.kozow.com/
| Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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.
|
| H | Fatal error: No https - result with http-status 200, no encryption
|
| 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 onlyvideo.kozow.com, 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.onlyvideo.kozow.com, 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 onlyvideo.kozow.com, 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.onlyvideo.kozow.com, 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.onlyvideo.kozow.com
|
| 2. Header-Checks |
| U |
|
| No https result with http status 2** or 4** (standard-check) found, no header checked.
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 6 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.ns0.dynu.com (66.85.159.14), ns1.dynu.com (72.51.58.2), ns3.dynu.com (162.251.164.146, 2605:9f80:4000:214::2), ns4.dynu.com (108.181.159.122, 2604:6600:2000:39::2), ns5.dynu.com (216.105.169.98, 2605:9f80:c000:404::2), ns6.dynu.com (173.0.55.138, 2607:f8f8:631:8612::2)
|
| A | Good (1 - 3.0):: An average of 0.3 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 6 different Name Servers found: ns0.dynu.com, ns1.dynu.com, ns3.dynu.com, ns4.dynu.com, ns5.dynu.com, ns6.dynu.com, 6 Name Servers included in Delegation: ns0.dynu.com, ns1.dynu.com, ns3.dynu.com, ns4.dynu.com, ns5.dynu.com, ns6.dynu.com, 6 Name Servers included in 1 Zone definitions: ns0.dynu.com, ns1.dynu.com, ns3.dynu.com, ns4.dynu.com, ns5.dynu.com, ns6.dynu.com, 1 Name Servers listed in SOA.Primary: ns1.dynu.com.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.dynu.com.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.dynu.com.
|
| 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: ns0.dynu.com, ns1.dynu.com, ns3.dynu.com, ns4.dynu.com, ns5.dynu.com, ns6.dynu.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: 6 different Name Servers found
|
| A | Good: Some Name Servers have IPv6 addresses: 4 Name Servers with IPv6 found (2 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.: 6 Name Servers, 1 Top Level Domain: com
|
| 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: dynu.com
|
| Warning: All Name Servers from the same Country / IP location.: 6 Name Servers, 1 Countries: US
|
| A | Info: Ipv4-Subnet-list: 6 Name Servers, 6 different subnets (first Byte): 108., 162., 173., 216., 66., 72., 6 different subnets (first two Bytes): 108.181., 162.251., 173.0., 216.105., 66.85., 72.51., 6 different subnets (first three Bytes): 108.181.159., 162.251.164., 173.0.55., 216.105.169., 66.85.159., 72.51.58.
|
| A | Excellent: Every Name Server IPv4-address starts with an unique Byte.
|
| A | Info: IPv6-Subnet-list: 4 Name Servers with IPv6, 3 different subnets (first block): 2604:, 2605:, 2607:, 3 different subnets (first two blocks): 2604:6600:, 2605:9f80:, 2607:f8f8:, 4 different subnets (first three blocks): 2604:6600:2000:, 2605:9f80:4000:, 2605:9f80:c000:, 2607:f8f8:0631:, 4 different subnets (first four blocks): 2604:6600:2000:0039:, 2605:9f80:4000:0214:, 2605:9f80:c000:0404:, 2607:f8f8:0631:8612:
|
| A | Good: Name Server IPv6 addresses from different subnets found.
|
| A | Good: Nameserver supports TCP connections: 1 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 1 good Nameserver
|
| X | Nameserver Timeout checking Echo Capitalization: ns0.dynu.com / 66.85.159.14
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 1 good Nameserver
|
| Nameserver doesn't pass all EDNS-Checks: ns0.dynu.com / 66.85.159.14: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
|
| 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 | http://onlyvideo.kozow.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 162.216.242.206
|
| Good: Acme-Check - Answer looks like a correct keyAuthorization - String: Filename + "." + base64url(Thumbprint(accountKey)). So creating a Letsencrypt certificate using that integrated solution should work. Don't use another client (like Certbot). Don't mix integrated solutions with own ACME-clients, that may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| A | http://onlyvideo.kozow.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2602:ff23:0:8888::206
|
| Good: Acme-Check - Answer looks like a correct keyAuthorization - String: Filename + "." + base64url(Thumbprint(accountKey)). So creating a Letsencrypt certificate using that integrated solution should work. Don't use another client (like Certbot). Don't mix integrated solutions with own ACME-clients, that may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| A | http://www.onlyvideo.kozow.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 162.216.242.206
|
| Good: Acme-Check - Answer looks like a correct keyAuthorization - String: Filename + "." + base64url(Thumbprint(accountKey)). So creating a Letsencrypt certificate using that integrated solution should work. Don't use another client (like Certbot). Don't mix integrated solutions with own ACME-clients, that may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| A | http://www.onlyvideo.kozow.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2602:ff23:0:8888::206
|
| Good: Acme-Check - Answer looks like a correct keyAuthorization - String: Filename + "." + base64url(Thumbprint(accountKey)). So creating a Letsencrypt certificate using that integrated solution should work. Don't use another client (like Certbot). Don't mix integrated solutions with own ACME-clients, that may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| 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: 289653 milliseconds, 289.653 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)