| 1. General Results, most used to calculate the result |
| A | name "yxa.at" is domain, public suffix is "at", top-level-domain-type is "country-code", Country is Austria, tld-manager is "nic.at GmbH"
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: www.yxa.at has 2 different ip addresses (authoritative).
|
| A | Good: Minimal 2 ip addresses per domain name found: yxa.at has 2 different ip addresses (authoritative).
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: www.yxa.at has 1 ipv4, 1 ipv6 addresses
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: yxa.at has 1 ipv4, 1 ipv6 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: every https has a Strict Transport Security Header
|
| A | Good: HSTS max-age is long enough, 31536000 seconds = 365 days
|
| A | Good: HSTS has preload directive
|
| Warning: HSTS preload sent, but not in Preload-List. Never send a preload directive if you don't know what preload means. Check https://hstspreload.org/ to learn the basics about the Google-Preload list. If you send a preload directive, you should **immediately** add your domain to the HSTS preload list via https://hstspreload.org/ . If Google accepts the domain, so the status is "pending": Note that new entries are hardcoded into the Chrome source code and can take several months before they reach the stable version. So you will see this message some months. If you don't want that or if you don't understand "preload", but if you send a preload directive and if you have correct A-redirects, everybody can add your domain to that list. Then you may have problems, it's not easy to undo that. So if you don't want your domain preloaded, remove the preload 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):2 complete Content-Type - header (3 urls)
|
| https://yxa.at/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Url with incomplete Content-Type - header - missing charset
|
| A | http://yxa.at/ 88.198.19.81
| https://yxa.at/
| Correct redirect http - https with the same domain name
|
| A | http://yxa.at/ 2a01:4f8:222:2c03::4
| https://yxa.at/
| Correct redirect http - https with the same domain name
|
| A | http://www.yxa.at/ 88.198.19.81
| https://www.yxa.at/
| Correct redirect http - https with the same domain name
|
| A | http://www.yxa.at/ 2a01:4f8:222:2c03::4
| https://www.yxa.at/
| Correct redirect http - https with the same domain name
|
| N | https://88.198.19.81/ 88.198.19.81
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://[2a01:04f8:0222:2c03:0000:0000:0000:0004]/ 2a01:4f8:222:2c03::4
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | yxa.at:465
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | yxa.at:993
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | yxa.at:8080
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | www.yxa.at:465
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | www.yxa.at:993
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | www.yxa.at:8080
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | 88.198.19.81:465
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | 88.198.19.81:993
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | 88.198.19.81:8080
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| 2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05) |
| 3. DNS- and NameServer - Checks |
| 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: nsv0.nitrado.net,nsv2.nitrado.de
|
| A | Good: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
|
| Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 2 different Name Servers found
|
| 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
|
| A | Good: Name servers with different Country locations found: 2 Name Servers, 2 Countries: DE, US
|
| A | Info: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 194., 85., 2 different subnets (first two Bytes): 194.169., 85.190., 2 different subnets (first three Bytes): 194.169.211., 85.190.159.
|
| A | Excellent: Every Name Server IPv4-address starts with an unique Byte.
|
| A | Good: Nameserver supports TCP connections: 2 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 2 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
|
| 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.
|
| A | Good: Every https result with status 200 and greater 1024 Bytes is compressed (gzip, deflate, br checked).
|
| https://yxa.at/ 88.198.19.81
|
| 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://yxa.at/ 2a01:4f8:222:2c03::4
|
| 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://yxa.at/ 88.198.19.81
|
| 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://yxa.at/ 2a01:4f8:222:2c03::4
|
| 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 CSS / JavaScript files are sent compressed (gzip, deflate, br checked). That reduces the content of the files. 19 external CSS / JavaScript files found
|
| A | Good: All images with internal compression not compressed. Some Images (.png, .jpg, .jpeg, .webp, .gif) are already compressed, so an additional compression isn't helpful. 2 images (type image/png, image/jpg) found without additional GZip. Not required because these images are already compressed
|
| Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 9 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 6 with Cache-Control max-age too short (minimum 7 days), 4 with Cache-Control long enough, 19 complete.
|
| Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 4 image 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, 4 complete.
|
| A | Good: All checked attribute values are enclosed in quotation marks (" or ').
|
| A | Good: All img-elements have a valid alt-attribute.: 4 img-elements found.
|
| 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
|
| http://yxa.at/ 88.198.19.81
|
| Warning: HSTS header sent via http has no effect
|
| http://yxa.at/ 2a01:4f8:222:2c03::4
|
| Warning: HSTS header sent via http has no effect
|
| http://www.yxa.at/ 88.198.19.81
|
| Warning: HSTS header sent via http has no effect
|
| http://www.yxa.at/ 2a01:4f8:222:2c03::4
|
| Warning: HSTS header sent via http has no effect
|
| https://yxa.at/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| 3.280 seconds
| Warning: 404 needs more then one second
|
| A | Duration: 108260 milliseconds, 108.260 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)