| 1. General Results, most used to calculate the result |
| A | name "my.yubico.com" is subdomain, public suffix is ".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: 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 | Good: HSTS has preload directive
|
| A | Excellent: Main Domain is in the Google-Preload-List
|
| A | Excellent: Main 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: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):2 complete Content-Type - header (3 urls)
|
| https://34.138.135.146/ 34.138.135.146
|
| Url with incomplete Content-Type - header - missing charset
|
| A | http://my.yubico.com/ 34.138.135.146
| https://my.yubico.com/
| Correct redirect http - https with the same domain name
|
| M | https://34.138.135.146/ 34.138.135.146
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| N | https://34.138.135.146/ 34.138.135.146
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| X | Fatal error: Nameserver doesn't support TCP connection: ns-cloud-e1.googledomains.com: NXDOMAIN
|
| 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.my.yubico.com
|
| 2. Header-Checks |
| A | my.yubico.com 34.138.135.146
| Content-Security-Policy
| Ok: Header without syntax errors found: default-src 'none'; script-src 'unsafe-inline';
|
| 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.
|
| E |
|
| Bad: No frame-ancestors directive found. Use one to limit the pages allowed to use this page in 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: No object-src found, but the default-src used as fallback is defined and restricted.
|
| 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 |
| 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 | my.yubico.com 34.138.135.146
| Referrer-Policy
| Critical: Missing Header:
|
| F | my.yubico.com 34.138.135.146
| Permissions-Policy
| Critical: Missing Header:
|
| B | my.yubico.com 34.138.135.146
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | my.yubico.com 34.138.135.146
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | my.yubico.com 34.138.135.146
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 15 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
|
| A | Info:: 15 Queries complete, 15 with IPv6, 0 with IPv4.
|
| A | Good: All DNS Queries done via IPv6.
|
| Ok (4 - 8):: An average of 3.8 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 4 different Name Servers found: ns-1322.awsdns-37.org, ns-689.awsdns-22.net, ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, 4 Name Servers included in Delegation: ns-1322.awsdns-37.org, ns-689.awsdns-22.net, ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, 4 Name Servers included in 1 Zone definitions: ns-1322.awsdns-37.org, ns-689.awsdns-22.net, ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, 2 Name Servers listed in SOA.Primary: ns-1322.awsdns-37.org, ns-cloud-e1.googledomains.com.
|
| Error: Different SOA.Primary Name Servers found, different SOA Definitions.: ns-1322.awsdns-37.org,ns-cloud-e1.googledomains.com.
|
| Error: SOA.Primary Name Server not included in the delegation set.: ns-1322.awsdns-37.org,ns-cloud-e1.googledomains.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 | Info: Ipv4-Subnet-list: 4 Name Servers, 2 different subnets (first Byte): 205., 216., 2 different subnets (first two Bytes): 205.251., 216.239., 4 different subnets (first three Bytes): 205.251.194., 205.251.197., 216.239.32., 216.239.34.
|
| A | Good: Name Server IPv4-addresses from different subnet found:
|
| A | Info: IPv6-Subnet-list: 4 Name Servers with IPv6, 2 different subnets (first block): 2001:, 2600:, 2 different subnets (first two blocks): 2001:4860:, 2600:9000:, 3 different subnets (first three blocks): 2001:4860:4802:, 2600:9000:5302:, 2600:9000:5305:, 4 different subnets (first four blocks): 2001:4860:4802:0032:, 2001:4860:4802:0034:, 2600:9000:5302:b100:, 2600:9000:5305:2a00:
|
| A | Good: Name Server IPv6 addresses from different subnets found.
|
| A | Good: Nameserver supports TCP connections: 16 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 16 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 16 good Nameserver
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 16 good Nameserver
|
| A | Good: All SOA have the same Serial Number
|
| A | Good: CAA entries found, creating certificate is limited: no CAA is allowed to create certificates
|
| A | Good: CAA entries found, creating certificate is limited: amazon.com is allowed to create certificates
|
| A | Good: CAA entries found, creating certificate is limited: digicert.com is allowed to create certificates
|
| A | Good: CAA entries found, creating certificate is limited: globalsign.com is allowed to create certificates
|
| 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: pki.goog is allowed to create certificates
|
| A | Good: CAA entries found, creating certificate is limited: pki.goog is allowed to create wildcard-certificates
|
| 4. Content- and Performance-critical Checks |
| https://my.yubico.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| 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://my.yubico.com/ 34.138.135.146
|
| 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://my.yubico.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-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://my.yubico.com/ 34.138.135.146
|
| 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://my.yubico.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| 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 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: 277330 milliseconds, 277.330 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)