| 1. General Results, most used to calculate the result |
| A | name "dashboard.status3.it" is subdomain, public suffix is ".it", top-level-domain is ".it", top-level-domain-type is "country-code", Country is Italy, tld-manager is "IIT - CNR", num .it-domains preloaded: 2389 (complete: 276475)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: dashboard.status3.it has 2 different ip addresses (authoritative).
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: dashboard.status3.it 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.
|
| 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):0 complete Content-Type - header (2 urls)
|
| https://dashboard.status3.it/ 85.215.129.99
|
| Url with incomplete Content-Type - header - missing charset
|
| https://85.215.129.99/ 85.215.129.99
|
| Url with incomplete Content-Type - header - missing charset
|
| A | http://dashboard.status3.it/ 85.215.129.99
| https://dashboard.status3.it/
| Correct redirect http - https with the same domain name
|
| B | https://dashboard.status3.it/ 85.215.129.99
|
| Missing HSTS-Header
|
| I | https://dashboard.status3.it/ 85.215.129.99
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
|
| K | http://dashboard.status3.it/ 85.215.129.99, Status 301
| http://dashboard.status3.it/ 2a01:239:27c:7000::1, Status -14
| Configuration problem - different ip addresses with different status
|
| K | https://dashboard.status3.it/ 85.215.129.99, Status 200
| https://dashboard.status3.it/ 2a01:239:27c:7000::1, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://dashboard.status3.it/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 85.215.129.99, Status 301
| http://dashboard.status3.it/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:239:27c:7000::1, Status -14
| Configuration problem - different ip addresses with different status
|
| N | https://85.215.129.99/ 85.215.129.99
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| X | Fatal error: Nameserver doesn't support TCP connection: a.dns.it: 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 dashboard.status3.it, 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.dashboard.status3.it
|
| 2. Header-Checks |
| F | dashboard.status3.it 85.215.129.99
| Content-Security-Policy
| Critical: Missing Header:
|
| F | dashboard.status3.it 85.215.129.99
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | dashboard.status3.it 85.215.129.99
| Referrer-Policy
| Critical: Missing Header:
|
| F | dashboard.status3.it 85.215.129.99
| Permissions-Policy
| Critical: Missing Header:
|
| B | dashboard.status3.it 85.215.129.99
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | dashboard.status3.it 85.215.129.99
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | dashboard.status3.it 85.215.129.99
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 9 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
|
| A | Info:: 9 Queries complete, 7 with IPv6, 2 with IPv4.
|
| Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses.
|
| 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.ns3.xtremeweb.de (130.185.108.193, 2a01:4a0:2002:2198:130:185:108:193)
|
| Ok (4 - 8):: An average of 4.5 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 2 different Name Servers found: ns1.it-smart.net, ns3.xtremeweb.de, 2 Name Servers included in Delegation: ns1.it-smart.net, ns3.xtremeweb.de, 2 Name Servers included in 1 Zone definitions: ns1.it-smart.net, ns3.xtremeweb.de, 1 Name Servers listed in SOA.Primary: ns1.it-smart.net.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.it-smart.net.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.it-smart.net.
|
| 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.it-smart.net, ns3.xtremeweb.de
|
| 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: Some Name Servers have IPv6 addresses: 1 Name Servers with IPv6 found (1 Name Servers without IPv6)
|
| A | Good: Name servers with different Top Level Domains / Public Suffix List entries found: 2 Name Servers, 2 Top Level Domains: de, net
|
| A | Good: Name Servers with different domain names found.: 2 different Domains found
|
| Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: DE
|
| A | Info: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 130., 149., 2 different subnets (first two Bytes): 130.185., 149.154., 2 different subnets (first three Bytes): 130.185.108., 149.154.159.
|
| A | Excellent: Every Name Server IPv4-address starts with an unique Byte.
|
| A | Info: IPv6-Subnet-list: 1 Name Servers with IPv6, 1 different subnets (first block): 2a01:, 1 different subnets (first two blocks): 2a01:04a0:, 1 different subnets (first three blocks): 2a01:04a0:2002:, 1 different subnets (first four blocks): 2a01:04a0:2002:2198:
|
| Fatal: All Name Server IPv6 addresses from the same subnet.
|
| A | Good: Nameserver supports TCP connections: 1 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 1 good Nameserver
|
| 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: ns1.it-smart.net: 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
|
| 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 |
| http://dashboard.status3.it/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:239:27c:7000::1
|
| Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. 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://dashboard.status3.it/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. 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://dashboard.status3.it/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:239:27c:7000::1, Status -14
| http://dashboard.status3.it/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 85.215.129.99, Status 301
| Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| A | Good: No https + http status 200 with inline CSS / JavaScript found
|
| https://dashboard.status3.it/ 85.215.129.99
|
| 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://85.215.129.99/ 85.215.129.99
|
| 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://dashboard.status3.it/ 85.215.129.99
|
| 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://85.215.129.99/ 85.215.129.99
|
| 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://dashboard.status3.it/ 85.215.129.99
|
| 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://85.215.129.99/ 85.215.129.99
|
| 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. 2 external CSS / JavaScript files without Compression found - 0 with Compression, 2 complete
|
| Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 2 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 0 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
|
| A | Duration: 140470 milliseconds, 140.470 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)