| 1. General Results, most used to calculate the result |
| A | name "aw.net" is domain, public suffix is ".net", top-level-domain is ".net", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .net-domains preloaded: 6448 (complete: 151507)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: aw.net has 2 different ip addresses (authoritative).
|
| A | Good: Minimal 2 ip addresses per domain name found: www.aw.net has 2 different ip addresses (authoritative).
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: aw.net has 1 ipv4, 1 ipv6 addresses
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: www.aw.net has 1 ipv4, 1 ipv6 addresses
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | https://aw.net/ 185.228.136.144
|
| Good: Valid DANE - entry found: signed Data _443._tcp.aw.net: CertUsage 2 (DANE-TA, Trust anchor assertion), Selector 0 (Cert, Full certificate), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 25847d668eb4f04fdd40b12b6b0740c567da7d024308eb6c2c96fe41d9de218d confirms the Certificate with the same value
|
| A | https://aw.net/ 185.228.136.144
|
| Good: Valid DANE - entry found: signed Data _443._tcp.aw.net: CertUsage 2 (DANE-TA, Trust anchor assertion), Selector 0 (Cert, Full certificate), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 730c1bdcd85f57ce5dc0bba733e5f1ba5a925b2a771d640a26f7a454224dad3b confirms the Certificate with the same value
|
| A | https://aw.net/ 2a03:4000:23:8c::1
|
| Good: Valid DANE - entry found: signed Data _443._tcp.aw.net: CertUsage 2 (DANE-TA, Trust anchor assertion), Selector 0 (Cert, Full certificate), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 730c1bdcd85f57ce5dc0bba733e5f1ba5a925b2a771d640a26f7a454224dad3b confirms the Certificate with the same value
|
| A | https://aw.net/ 2a03:4000:23:8c::1
|
| Good: Valid DANE - entry found: signed Data _443._tcp.aw.net: CertUsage 2 (DANE-TA, Trust anchor assertion), Selector 0 (Cert, Full certificate), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 25847d668eb4f04fdd40b12b6b0740c567da7d024308eb6c2c96fe41d9de218d confirms the Certificate with the same value
|
| A | https://aw.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Good: Valid DANE - entry found: signed Data _443._tcp.aw.net: CertUsage 2 (DANE-TA, Trust anchor assertion), Selector 0 (Cert, Full certificate), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 730c1bdcd85f57ce5dc0bba733e5f1ba5a925b2a771d640a26f7a454224dad3b confirms the Certificate with the same value
|
| A | https://aw.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Good: Valid DANE - entry found: signed Data _443._tcp.aw.net: CertUsage 2 (DANE-TA, Trust anchor assertion), Selector 0 (Cert, Full certificate), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 25847d668eb4f04fdd40b12b6b0740c567da7d024308eb6c2c96fe41d9de218d confirms the Certificate with the same value
|
| A | https://185.228.136.144/ 185.228.136.144
|
| Good: Valid DANE - entry found: signed Data _443._tcp.aw.net: CertUsage 2 (DANE-TA, Trust anchor assertion), Selector 0 (Cert, Full certificate), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 25847d668eb4f04fdd40b12b6b0740c567da7d024308eb6c2c96fe41d9de218d confirms the Certificate with the same value
|
| A | https://185.228.136.144/ 185.228.136.144
|
| Good: Valid DANE - entry found: signed Data _443._tcp.aw.net: CertUsage 2 (DANE-TA, Trust anchor assertion), Selector 0 (Cert, Full certificate), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 730c1bdcd85f57ce5dc0bba733e5f1ba5a925b2a771d640a26f7a454224dad3b confirms the Certificate with the same value
|
| A | https://[2a03:4000:0023:008c:0000:0000:0000:0001]/ 2a03:4000:23:8c::1
|
| Good: Valid DANE - entry found: signed Data _443._tcp.aw.net: CertUsage 2 (DANE-TA, Trust anchor assertion), Selector 0 (Cert, Full certificate), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 730c1bdcd85f57ce5dc0bba733e5f1ba5a925b2a771d640a26f7a454224dad3b confirms the Certificate with the same value
|
| A | https://[2a03:4000:0023:008c:0000:0000:0000:0001]/ 2a03:4000:23:8c::1
|
| Good: Valid DANE - entry found: signed Data _443._tcp.aw.net: CertUsage 2 (DANE-TA, Trust anchor assertion), Selector 0 (Cert, Full certificate), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 25847d668eb4f04fdd40b12b6b0740c567da7d024308eb6c2c96fe41d9de218d confirms the Certificate with the same value
|
| 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.
|
| 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 includeSubdomains - directive
|
| A | Good: HSTS has preload directive
|
| A | Excellent: Domain is in the Google-Preload-List
|
| A | Excellent: Domain is in the Mozilla/Firefox-Preload-List
|
| A | HSTS-Preload-Status: Preloaded. 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):3 complete Content-Type - header (5 urls)
|
| https://185.228.136.144/ 185.228.136.144
|
| Url with incomplete Content-Type - header - missing charset
|
| https://[2a03:4000:0023:008c:0000:0000:0000:0001]/ 2a03:4000:23:8c::1
|
| Url with incomplete Content-Type - header - missing charset
|
| A | http://aw.net/ 185.228.136.144
| https://aw.net/
| Correct redirect http - https with the same domain name
|
| A | http://aw.net/ 2a03:4000:23:8c::1
| https://aw.net/
| Correct redirect http - https with the same domain name
|
| A | http://www.aw.net/ 185.228.136.144
| https://www.aw.net/
| Correct redirect http - https with the same domain name
|
| A | http://www.aw.net/ 2a03:4000:23:8c::1
| https://www.aw.net/
| Correct redirect http - https with the same domain name
|
| N | https://185.228.136.144/ 185.228.136.144
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://[2a03:4000:0023:008c:0000:0000:0000:0001]/ 2a03:4000:23:8c::1
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | 185.228.136.144:993
|
| 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 aw.net, 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.aw.net, 2 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 aw.net, 2 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 www.aw.net, 2 ip addresses.
|
| 2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05) |
| 3. DNS- and NameServer - Checks |
| A | Info:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
|
| A | Info:: 2 Queries complete, 2 with IPv6, 0 with IPv4.
|
| A | Good: All DNS Queries done via IPv6.
|
| 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.ns2.aw.net (188.68.45.194, 2a03:4000:23:8c::2), ns3.aw.net (23.160.193.164, 2602:fea7:c0:3::2)
|
| A | Good (1 - 3.0):: An average of 1.0 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 2 different Name Servers found: ns2.aw.net, ns3.aw.net, 2 Name Servers included in Delegation: ns2.aw.net, ns3.aw.net, 2 Name Servers included in 1 Zone definitions: ns2.aw.net, ns3.aw.net, 1 Name Servers listed in SOA.Primary: ns2.aw.net.
|
| A | Good: Only one SOA.Primary Name Server found.: ns2.aw.net.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns2.aw.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: ns2.aw.net, ns3.aw.net
|
| 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: All name servers have ipv4- and ipv6-addresses.: 2 different Name Servers found
|
| 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: net
|
| 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: aw.net
|
| 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): 188., 23., 2 different subnets (first two Bytes): 188.68., 23.160., 2 different subnets (first three Bytes): 188.68.45., 23.160.193.
|
| A | Excellent: Every Name Server IPv4-address starts with an unique Byte.
|
| A | Info: IPv6-Subnet-list: 2 Name Servers with IPv6, 2 different subnets (first block): 2602:, 2a03:, 2 different subnets (first two blocks): 2602:fea7:, 2a03:4000:, 2 different subnets (first three blocks): 2602:fea7:00c0:, 2a03:4000:0023:, 2 different subnets (first four blocks): 2602:fea7:00c0:0003:, 2a03:4000:0023:008c:
|
| A | Excellent: Every Name Server IPv6-address starts with an unique Hex-block
|
| 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
|
| Nameserver doesn't pass all EDNS-Checks: ns2.aw.net / 2a03:4000:23:8c::2: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: fatal timeout. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
|
| X | Fatal error: Nameservers with different SOA Serial Numbers
|
| A | Good: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates
|
| A | Good: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create wildcard-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.
|
| https://185.228.136.144/ 185.228.136.144
|
| 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://[2a03:4000:0023:008c:0000:0000:0000:0001]/ 2a03:4000:23:8c::1
|
| 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.
|
| A | Good: Every https result with status 200 has a minified Html-Content with a quota lower then 110 %.
|
| https://aw.net/ 185.228.136.144
|
| 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://aw.net/ 2a03:4000:23:8c::1
|
| 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://185.228.136.144/ 185.228.136.144
|
| 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://[2a03:4000:0023:008c:0000:0000:0000:0001]/ 2a03:4000:23:8c::1
|
| 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://185.228.136.144/ 185.228.136.144
|
| 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.: 6 script elements without defer/async.
|
| https://[2a03:4000:0023:008c:0000:0000:0000:0001]/ 2a03:4000:23:8c::1
|
| 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.: 6 script elements without defer/async.
|
| Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 14 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, 14 complete.
|
| Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 338 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, 338 complete.
|
| A | Good: All checked attribute values are enclosed in quotation marks (" or ').
|
| Wrong: img-elements without alt-attribute or empty alt-attribute found. The alt-attribute ("alternative") is required and should describe the img. So Screenreader and search engines are able to use these informations.: 342 img-elements without alt-attribute, 0 img-elements with empty alt-attribute 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
|
| https://aw.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| 3.326 seconds
| Warning: 404 needs more then one second
|
| A | Duration: 109514 milliseconds, 109.514 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)