| 1. General Results, most used to calculate the result |
| A | name "tobiaskaufmann.at" is domain, public suffix is ".at", top-level-domain is ".at", top-level-domain-type is "country-code", Country is Austria, tld-manager is "nic.at GmbH", num .at-domains preloaded: 573 (complete: 129392)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: tobiaskaufmann.at has 2 different ip addresses (authoritative).
|
| A | Good: Minimal 2 ip addresses per domain name found: www.tobiaskaufmann.at has 2 different ip addresses (authoritative).
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: tobiaskaufmann.at has 1 ipv4, 1 ipv6 addresses
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: www.tobiaskaufmann.at has 1 ipv4, 1 ipv6 addresses
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| 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 (11 urls)
|
| http://tobiaskaufmann.at/ 37.252.188.60
|
| Url with incomplete Content-Type - header - missing charset
|
| http://tobiaskaufmann.at/ 2a01:aee0:0:10::11
|
| Url with incomplete Content-Type - header - missing charset
|
| http://www.tobiaskaufmann.at/ 37.252.188.60
|
| Url with incomplete Content-Type - header - missing charset
|
| http://www.tobiaskaufmann.at/ 2a01:aee0:0:10::11
|
| Url with incomplete Content-Type - header - missing charset
|
| https://tobiaskaufmann.at/ 2a01:aee0:0:10::11
|
| Url with incomplete Content-Type - header - missing charset
|
| https://www.tobiaskaufmann.at/ 2a01:aee0:0:10::11
|
| Url with incomplete Content-Type - header - missing charset
|
| http://tobiaskaufmann.at/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 37.252.188.60
|
| Url with incomplete Content-Type - header - missing charset
|
| http://tobiaskaufmann.at/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:aee0:0:10::11
|
| Url with incomplete Content-Type - header - missing charset
|
| http://www.tobiaskaufmann.at/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 37.252.188.60
|
| Url with incomplete Content-Type - header - missing charset
|
| http://www.tobiaskaufmann.at/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:aee0:0:10::11
|
| Url with incomplete Content-Type - header - missing charset
|
| https://[2a01:aee0:0000:0010:0000:0000:0000:0011]/ 2a01:aee0:0:10::11
|
| Url with incomplete Content-Type - header - missing charset
|
| B | Warning: HSTS max-age is too short - minimum 31536000 = 365 days required, 15768000 seconds = 182 days found
|
| C | Error - no preferred version www or non-www. Select one version as preferred version, then add a redirect https + not-preferred version to https + preferred version. Perhaps in your port 443 vHost something like "RewriteEngine on" + "RewriteCond %{SERVER_NAME} = example.com" + "ReWriteRule ^ https://www.example.com%{REQUEST_URI} [END,QSA,R=permanent]" (three rows, without the "). That should create a redirect https + example.com ⇒ https + www.example.com. Or switch both values to use the non-www version as your preferred version.
|
| C | Error - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
|
| H | Fatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.
|
| I | https://tobiaskaufmann.at/ 2a01:aee0:0:10::11
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
|
| I | https://www.tobiaskaufmann.at/ 2a01:aee0:0:10::11
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
|
| I | https://[2a01:aee0:0000:0010:0000:0000:0000:0011]/ 2a01:aee0:0:10::11
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
|
| I | http://tobiaskaufmann.at/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 37.252.188.60
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Not used to calculate the result because it's a http - check. But listed so you should fix it.
|
| I | http://tobiaskaufmann.at/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:aee0:0:10::11
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Not used to calculate the result because it's a http - check. But listed so you should fix it.
|
| I | http://www.tobiaskaufmann.at/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 37.252.188.60
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Not used to calculate the result because it's a http - check. But listed so you should fix it.
|
| I | http://www.tobiaskaufmann.at/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:aee0:0:10::11
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Not used to calculate the result because it's a http - check. But listed so you should fix it.
|
| K | https://tobiaskaufmann.at/ 37.252.188.60, Status -2
| https://tobiaskaufmann.at/ 2a01:aee0:0:10::11, Status 200
| Configuration problem - different ip addresses with different status
|
| K | https://www.tobiaskaufmann.at/ 37.252.188.60, Status -2
| https://www.tobiaskaufmann.at/ 2a01:aee0:0:10::11, Status 200
| Configuration problem - different ip addresses with different status
|
| K | http://tobiaskaufmann.at/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 37.252.188.60, Status 200
| http://tobiaskaufmann.at/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:aee0:0:10::11, Status 404
| Configuration problem - different ip addresses with different status
|
| K | http://www.tobiaskaufmann.at/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 37.252.188.60, Status 200
| http://www.tobiaskaufmann.at/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:aee0:0:10::11, Status 404
| Configuration problem - different ip addresses with different status
|
| N | https://tobiaskaufmann.at/ 2a01:aee0:0:10::11
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://www.tobiaskaufmann.at/ 2a01:aee0:0:10::11
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://[2a01:aee0:0000:0010:0000:0000:0000:0011]/ 2a01:aee0:0:10::11
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| V | https://tobiaskaufmann.at/ 37.252.188.60
|
| Connect failure - perhaps firewall
|
| V | https://www.tobiaskaufmann.at/ 37.252.188.60
|
| Connect failure - perhaps firewall
|
| V | https://37.252.188.60/ 37.252.188.60
|
| Connect failure - perhaps firewall
|
| 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 tobiaskaufmann.at, 2 ip addresses.
|
| 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 www.tobiaskaufmann.at, 2 ip addresses.
|
| 2. Header-Checks |
| 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, 9 with IPv6, 0 with IPv4.
|
| A | Good: All DNS Queries done via IPv6.
|
| 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.easyname.eu, ns2.easyname.eu, 2 Name Servers included in Delegation: ns1.easyname.eu, ns2.easyname.eu, 2 Name Servers included in 1 Zone definitions: ns1.easyname.eu, ns2.easyname.eu, 1 Name Servers listed in SOA.Primary: ns1.easyname.eu.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.easyname.eu.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.easyname.eu.
|
| 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.easyname.eu, ns2.easyname.eu
|
| 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)
|
| Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 2 Name Servers, 1 Top Level Domain: eu
|
| Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: easyname.eu
|
| Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: AT
|
| A | Info: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 77., 1 different subnets (first two Bytes): 77.244., 2 different subnets (first three Bytes): 77.244.243., 77.244.244.
|
| A | Good: Name Server IPv4-addresses from different subnet found:
|
| A | Info: IPv6-Subnet-list: 1 Name Servers with IPv6, 1 different subnets (first block): 2a02:, 1 different subnets (first two blocks): 2a02:01b8:, 1 different subnets (first three blocks): 2a02:01b8:ea59:, 1 different subnets (first four blocks): 2a02:01b8:ea59:0000:
|
| Fatal: All Name Server IPv6 addresses from the same subnet.
|
| A | Good: Nameserver supports TCP connections: 3 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 3 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 3 good Nameserver
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 3 good Nameserver
|
| Nameserver doesn't pass all EDNS-Checks: dns.nic.at: 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://tobiaskaufmann.at/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 37.252.188.60
|
| 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.
|
| http://www.tobiaskaufmann.at/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 37.252.188.60
|
| 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.
|
| http://tobiaskaufmann.at/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:aee0:0:10::11, Status 404
| http://tobiaskaufmann.at/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 37.252.188.60, Status 200
| 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.
|
| http://www.tobiaskaufmann.at/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:aee0:0:10::11, Status 404
| http://www.tobiaskaufmann.at/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 37.252.188.60, Status 200
| 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: Every https result with status 200 and greater 1024 Bytes is compressed (gzip, deflate, br checked).
|
| https://tobiaskaufmann.at/ 2a01:aee0:0:10::11
|
| 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://www.tobiaskaufmann.at/ 2a01:aee0:0:10::11
|
| 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://[2a01:aee0:0000:0010:0000:0000:0000:0011]/ 2a01:aee0:0:10::11
|
| 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://tobiaskaufmann.at/ 2a01:aee0:0:10::11
|
| 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://www.tobiaskaufmann.at/ 2a01:aee0:0:10::11
|
| 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://[2a01:aee0:0000:0010:0000:0000:0000:0011]/ 2a01:aee0:0:10::11
|
| 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.
|
| http://tobiaskaufmann.at/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 37.252.188.60
|
| 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.: 7 script elements without defer/async.
|
| http://www.tobiaskaufmann.at/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 37.252.188.60
|
| 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.: 7 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. 4 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. 18 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 4 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 22 complete.
|
| A | Good: All images are sent with a long Cache-Control header (minimum 7 days). So the browser can reuse these files, no download is required. 5 image files with long Cache-Control max-age found
|
| A | Good: All checked attribute values are enclosed in quotation marks (" or ').
|
| A | Good: All img-elements have a valid alt-attribute.: 5 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
|
| A | Info: Different Server-Headers found
|
| A | Duration: 99763 milliseconds, 99.763 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)