| 1. General Results, most used to calculate the result |
| A | name "smartworking.unione.valdera.pi.it" is subdomain, public suffix is "pi.it", top-level-domain-type is "country-code", Country is Italy, tld-manager is "IIT - CNR"
|
| A | Good: All ip addresses are public addresses
|
| 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: every https has a Strict Transport Security Header
|
| A | Good: HSTS has includeSubdomains - directive
|
| 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):1 complete Content-Type - header (2 urls)
|
| https://smartworking.unione.valdera.pi.it/ 159.213.141.90
|
| Url with incomplete Content-Type - header - missing charset
|
| A | http://smartworking.unione.valdera.pi.it/ 159.213.141.90
| https://smartworking.unione.valdera.pi.it/
| Correct redirect http - https with the same domain name
|
| B | Warning: HSTS max-age is too short - minimum 31536000 = 365 days required, 15768000 seconds = 182 days found
|
| N | smartworking.unione.valdera.pi.it:8443
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | 159.213.141.90:8443
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| X | Fatal error: Nameserver doesn't support TCP connection: ns.valderassociata.it: Timeout
|
| X | Fatal error: Nameserver doesn't support TCP connection: ns2.valderassociata.it: Timeout
|
| 2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05) |
| 3. DNS- and NameServer - Checks |
| X | Nameserver Timeout checking Echo Capitalization: ns.valderassociata.it
|
| X | Nameserver Timeout checking EDNS512: ns.valderassociata.it
|
|
|
|
|
| Nameserver doesn't pass all EDNS-Checks: ns.valderassociata.it: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: ns.valderassociata.it: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
|
| 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 | 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.
|
| https://smartworking.unione.valdera.pi.it/ 159.213.141.90
|
| 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://smartworking.unione.valdera.pi.it/ 159.213.141.90
|
| 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.
|
| Warning: CSS / JavaScript found without Compression. Compress these ressources, gzip, deflate, br are checked. 19 external CSS / JavaScript files without GZip found - 0 with GZip, 19 complete
|
| Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 3 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 16 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 19 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://smartworking.unione.valdera.pi.it/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| 2.750 seconds
| Warning: 404 needs more then one second
|
| A | Info: Different Server-Headers found
|
| A | Duration: 303987 milliseconds, 303.987 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)