| 1. General Results, most used to calculate the result |
| A | name "dashboard.noggn.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: 94787 (complete: 245733)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: dashboard.noggn.com has 4 different ip addresses (authoritative).
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: dashboard.noggn.com has 2 ipv4, 2 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 | https://dashboard.noggn.com/ 3.72.140.173
| https://dashboard.noggn.com/web/app
| Correct redirect https to https
|
| A | https://dashboard.noggn.com/ 18.192.94.96
| https://dashboard.noggn.com/web/app
| Correct redirect https to https
|
| A | https://dashboard.noggn.com/ 52.58.254.253
| https://dashboard.noggn.com/web/app
| Correct redirect https to https
|
| A | https://dashboard.noggn.com/ 2a05:d014:58f:6200::64
| https://dashboard.noggn.com/web/app
| Correct redirect https to https
|
| A | https://dashboard.noggn.com/ 2a05:d014:58f:6202::64
| https://dashboard.noggn.com/web/app
| Correct redirect https to https
|
| 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.
|
| 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 | http://dashboard.noggn.com/ 3.72.140.173
| https://dashboard.noggn.com/
| Correct redirect http - https with the same domain name
|
| A | http://dashboard.noggn.com/ 18.192.94.96
| https://dashboard.noggn.com/
| Correct redirect http - https with the same domain name
|
| A | http://dashboard.noggn.com/ 52.58.254.253
| https://dashboard.noggn.com/
| Correct redirect http - https with the same domain name
|
| A | http://dashboard.noggn.com/ 2a05:d014:58f:6200::64
| https://dashboard.noggn.com/
| Correct redirect http - https with the same domain name
|
| A | http://dashboard.noggn.com/ 2a05:d014:58f:6202::64
| https://dashboard.noggn.com/
| Correct redirect http - https with the same domain name
|
| M | https://3.72.140.173/ 3.72.140.173
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://18.192.94.96/ 18.192.94.96
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://52.58.254.253/ 52.58.254.253
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://[2a05:d014:058f:6200:0000:0000:0000:0064]/ 2a05:d014:58f:6200::64
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://[2a05:d014:058f:6202:0000:0000:0000:0064]/ 2a05:d014:58f:6202::64
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| N | https://3.72.140.173/ 3.72.140.173
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://18.192.94.96/ 18.192.94.96
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://52.58.254.253/ 52.58.254.253
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://[2a05:d014:058f:6200:0000:0000:0000:0064]/ 2a05:d014:58f:6200::64
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://[2a05:d014:058f:6202:0000:0000:0000:0064]/ 2a05:d014:58f:6202::64
|
| 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 dashboard.noggn.com, 4 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 dashboard.noggn.com, 4 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.dashboard.noggn.com
|
| 2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05) |
| A | dashboard.noggn.com
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
| A |
| Referrer-Policy
| Ok: Header without syntax errors found: no-referrer
|
| A |
| X-Frame-Options
| Ok: Header without syntax errors found: DENY
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. DENY. 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 | dashboard.noggn.com
| Content-Security-Policy
| Critical: Missing Header:
|
| F | dashboard.noggn.com
| Permissions-Policy
| Critical: Missing Header:
|
| B | dashboard.noggn.com
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | dashboard.noggn.com
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | dashboard.noggn.com
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 26 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
|
| A | Info:: 26 Queries complete, 26 with IPv6, 0 with IPv4.
|
| A | Good: All DNS Queries done via IPv6.
|
| Bad (greater 8):: An average of 13.0 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 2 different Name Servers found: ns05.domaincontrol.com, ns06.domaincontrol.com, 2 Name Servers included in Delegation: ns05.domaincontrol.com, ns06.domaincontrol.com, 2 Name Servers included in 1 Zone definitions: ns05.domaincontrol.com, ns06.domaincontrol.com, 1 Name Servers listed in SOA.Primary: ns05.domaincontrol.com.
|
| A | Good: Only one SOA.Primary Name Server found.: ns05.domaincontrol.com.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns05.domaincontrol.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: 2 Name Servers, 2 different subnets (first Byte): 173., 97., 2 different subnets (first two Bytes): 173.201., 97.74., 2 different subnets (first three Bytes): 173.201.70., 97.74.102.
|
| A | Excellent: Every Name Server IPv4-address starts with an unique Byte.
|
| A | Info: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2603:, 1 different subnets (first two blocks): 2603:0005:, 2 different subnets (first three blocks): 2603:0005:2160:, 2603:0005:2260:, 2 different subnets (first four blocks): 2603:0005:2160:0000:, 2603:0005:2260:0000:
|
| A | Good: Name Server IPv6 addresses from different subnets found.
|
| 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
|
| Nameserver doesn't pass all EDNS-Checks: ns05.domaincontrol.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
|
| A | Good: All SOA have the same Serial Number
|
| A | Good: CAA entries found, creating certificate is limited: digicert.com is allowed to create certificates
|
| 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://dashboard.noggn.com/web/app
|
| 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://dashboard.noggn.com/web/app
|
| 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://dashboard.noggn.com/web/app
|
| 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.
|
| A | Good: All CSS / JavaScript files are sent compressed (gzip, deflate, br checked). That reduces the content of the files. 2 external CSS / JavaScript files found
|
| 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, 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 ').
|
| 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
|
| https://3.72.140.173/ 3.72.140.173
| 2.230 seconds
| Warning: 404 needs more then one second
|
| https://18.192.94.96/ 18.192.94.96
| 3.360 seconds
| Warning: 404 needs more then one second
|
| https://52.58.254.253/ 52.58.254.253
| 2.226 seconds
| Warning: 404 needs more then one second
|
| https://[2a05:d014:058f:6200:0000:0000:0000:0064]/ 2a05:d014:58f:6200::64
| 2.066 seconds
| Warning: 404 needs more then one second
|
| https://[2a05:d014:058f:6202:0000:0000:0000:0064]/ 2a05:d014:58f:6202::64
| 2.133 seconds
| Warning: 404 needs more then one second
|
| A | Duration: 340854 milliseconds, 340.854 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)