| 1. General Results, most used to calculate the result |
| A | name "serverhunter.de" is domain, public suffix is ".de", top-level-domain is ".de", top-level-domain-type is "country-code", Country is Germany, tld-manager is "DENIC eG", num .de-domains preloaded: 11085 (complete: 276475)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: serverhunter.de has 6 different ip addresses (authoritative).
|
| A | Good: Minimal 2 ip addresses per domain name found: www.serverhunter.de has 6 different ip addresses (authoritative).
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: serverhunter.de has 3 ipv4, 3 ipv6 addresses
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: www.serverhunter.de has 3 ipv4, 3 ipv6 addresses
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | https://serverhunter.de/ 116.202.9.166
| https://pawhost.de/
| Correct redirect https to https
|
| A | https://serverhunter.de/ 116.202.21.136
| https://pawhost.de/
| Correct redirect https to https
|
| A | https://serverhunter.de/ 116.203.213.72
| https://pawhost.de/
| Correct redirect https to https
|
| A | https://serverhunter.de/ 2a01:4f8:c17:c19c::1
| https://pawhost.de/
| Correct redirect https to https
|
| A | https://serverhunter.de/ 2a01:4f8:c2c:abf5::1
| https://pawhost.de/
| Correct redirect https to https
|
| A | https://serverhunter.de/ 2a01:4f8:c010:3f9c::1
| https://pawhost.de/
| Correct redirect https to https
|
| 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 cookie has a SameSite Attribute with a correct value Strict/Lax/None
|
| 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: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
|
| B | https://serverhunter.de/ 116.202.9.166
|
| Missing HSTS-Header
|
| B | https://serverhunter.de/ 116.202.21.136
|
| Missing HSTS-Header
|
| B | https://serverhunter.de/ 116.203.213.72
|
| Missing HSTS-Header
|
| B | https://serverhunter.de/ 2a01:4f8:c17:c19c::1
|
| Missing HSTS-Header
|
| B | https://serverhunter.de/ 2a01:4f8:c2c:abf5::1
|
| Missing HSTS-Header
|
| B | https://serverhunter.de/ 2a01:4f8:c010:3f9c::1
|
| Missing HSTS-Header
|
| B | https://pawhost.de/
|
| Missing HSTS-Header
|
| B | https://www.serverhunter.de/ 116.202.9.166
|
| Missing HSTS-Header
|
| B | https://www.serverhunter.de/ 116.202.21.136
|
| Missing HSTS-Header
|
| B | https://www.serverhunter.de/ 116.203.213.72
|
| Missing HSTS-Header
|
| B | https://www.serverhunter.de/ 2a01:4f8:c17:c19c::1
|
| Missing HSTS-Header
|
| B | https://www.serverhunter.de/ 2a01:4f8:c2c:abf5::1
|
| Missing HSTS-Header
|
| B | https://www.serverhunter.de/ 2a01:4f8:c010:3f9c::1
|
| Missing HSTS-Header
|
| B | https://pawhost.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Missing HSTS-Header
|
| B | https://pawhost.de/
| i18n_redirected=de; Path=/; Expires=Mon, 19 Oct 2026 20:35:53 GMT; SameSite=Lax
| Cookie sent via https, but not marked as secure
|
| E | http://serverhunter.de/ 116.202.9.166
| https://pawhost.de/
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| E | http://serverhunter.de/ 116.202.21.136
| https://pawhost.de/
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| E | http://serverhunter.de/ 116.203.213.72
| https://pawhost.de/
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| E | http://serverhunter.de/ 2a01:4f8:c17:c19c::1
| https://pawhost.de/
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| E | http://serverhunter.de/ 2a01:4f8:c2c:abf5::1
| https://pawhost.de/
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| E | http://serverhunter.de/ 2a01:4f8:c010:3f9c::1
| https://pawhost.de/
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| E | http://www.serverhunter.de/ 116.202.9.166
| https://pawhost.de/
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| E | http://www.serverhunter.de/ 116.202.21.136
| https://pawhost.de/
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| E | http://www.serverhunter.de/ 116.203.213.72
| https://pawhost.de/
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| E | http://www.serverhunter.de/ 2a01:4f8:c17:c19c::1
| https://pawhost.de/
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| E | http://www.serverhunter.de/ 2a01:4f8:c2c:abf5::1
| https://pawhost.de/
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| E | http://www.serverhunter.de/ 2a01:4f8:c010:3f9c::1
| https://pawhost.de/
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| I | https://pawhost.de/
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
|
| K | http://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.202.21.136, Status -14
| http://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c010:3f9c::1, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.202.21.136, Status -14
| http://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c17:c19c::1, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.202.9.166, Status -14
| http://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c010:3f9c::1, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.202.9.166, Status -14
| http://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c17:c19c::1, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.202.9.166, Status -14
| http://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c2c:abf5::1, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.202.21.136, Status -14
| http://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c2c:abf5::1, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.203.213.72, Status -14
| http://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c010:3f9c::1, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.203.213.72, Status -14
| http://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c17:c19c::1, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.203.213.72, Status -14
| http://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c2c:abf5::1, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://www.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.202.21.136, Status -14
| http://www.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c010:3f9c::1, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://www.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.202.9.166, Status -14
| http://www.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c010:3f9c::1, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://www.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.202.9.166, Status -14
| http://www.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c17:c19c::1, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://www.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.202.21.136, Status -14
| http://www.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c17:c19c::1, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://www.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.202.21.136, Status -14
| http://www.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c2c:abf5::1, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://www.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.203.213.72, Status -14
| http://www.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c010:3f9c::1, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://www.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.203.213.72, Status -14
| http://www.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c17:c19c::1, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://www.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.203.213.72, Status -14
| http://www.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c2c:abf5::1, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://www.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.202.9.166, Status -14
| http://www.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c2c:abf5::1, Status 301
| Configuration problem - different ip addresses with different status
|
| M | https://[2a01:04f8:0c17:c19c:0000:0000:0000:0001]/ 2a01:4f8:c17:c19c::1
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://[2a01:04f8:0c2c:abf5:0000:0000:0000:0001]/ 2a01:4f8:c2c:abf5::1
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://[2a01:04f8:c010:3f9c:0000:0000:0000:0001]/ 2a01:4f8:c010:3f9c::1
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| N | https://[2a01:04f8:0c17:c19c:0000:0000:0000:0001]/ 2a01:4f8:c17:c19c::1
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://[2a01:04f8:0c2c:abf5:0000:0000:0000:0001]/ 2a01:4f8:c2c:abf5::1
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://[2a01:04f8:c010:3f9c:0000:0000:0000:0001]/ 2a01:4f8:c010:3f9c::1
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| 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 serverhunter.de, 6 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.serverhunter.de, 6 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.serverhunter.de
|
| 2. Header-Checks |
| F | pawhost.de
| X-Content-Type-Options
| Critical: Header with syntax errors found: nosniff,nosniff
|
| F |
|
| Critical: Duplicated values found. Looks like the page sends multiple headers with the same name. nosniff,nosniff
|
| F |
|
| Critical: Unknown token found. Standard-token with additional characters are not defined. nosniff,nosniff
|
| F |
|
| Critical: Unknown token found. Standard-token with additional characters are not defined. nosniff,nosniff
|
| A |
| X-Frame-Options
| Ok: Header without syntax errors found: SAMEORIGIN,DENY
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. SAMEORIGIN,DENY. Better solution: Use a Content-Security-Policy Header with a frame-ancestors directive. DENY - use 'none', SAMEORIGIN - use 'self'. If you want to allow some domains to frame your page, add these urls.
|
| F |
|
| Critical: Unknown token found. Standard-token with additional characters are not defined. SAMEORIGIN,DENY
|
| F |
|
| Critical: Unknown token found. Standard-token with additional characters are not defined. SAMEORIGIN,DENY
|
| F | pawhost.de
| Content-Security-Policy
| Critical: Missing Header:
|
| F | pawhost.de
| Referrer-Policy
| Critical: Missing Header:
|
| F | pawhost.de
| Permissions-Policy
| Critical: Missing Header:
|
| B | pawhost.de
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | pawhost.de
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | pawhost.de
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 16 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
|
| A | Info:: 16 Queries complete, 16 with IPv6, 0 with IPv4.
|
| A | Good: All DNS Queries done via IPv6.
|
| Ok (4 - 8):: An average of 5.3 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 3 different Name Servers found: ns1.domainoffensive.de, ns2.domainoffensive.eu, ns3.domainoffensive.net, 3 Name Servers included in Delegation: ns1.domainoffensive.de, ns2.domainoffensive.eu, ns3.domainoffensive.net, 3 Name Servers included in 1 Zone definitions: ns1.domainoffensive.de, ns2.domainoffensive.eu, ns3.domainoffensive.net, 1 Name Servers listed in SOA.Primary: ns1.domainoffensive.de.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.domainoffensive.de.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.domainoffensive.de.
|
| 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.domainoffensive.de, ns2.domainoffensive.eu, ns3.domainoffensive.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: 3 different Name Servers found
|
| A | Good: All name servers have ipv4- and ipv6-addresses.: 3 different Name Servers found
|
| A | Good: Name servers with different Top Level Domains / Public Suffix List entries found: 3 Name Servers, 3 Top Level Domains: eu, de, net
|
| A | Good: Name Servers with different domain names found.: 3 different Domains found
|
| Warning: All Name Servers from the same Country / IP location.: 3 Name Servers, 1 Countries: AT
|
| A | Info: Ipv4-Subnet-list: 3 Name Servers, 2 different subnets (first Byte): 176., 192., 2 different subnets (first two Bytes): 176.97., 192.174., 2 different subnets (first three Bytes): 176.97.158., 192.174.68.
|
| A | Good: Name Server IPv4-addresses from different subnet found:
|
| A | Info: IPv6-Subnet-list: 3 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:067c:, 2 different subnets (first three blocks): 2001:067c:01bc:, 2001:067c:10b8:, 2 different subnets (first four blocks): 2001:067c:01bc:0000:, 2001:067c:10b8:0000:
|
| A | Good: Name Server IPv6 addresses from different subnets found.
|
| A | Good: Nameserver supports TCP connections: 6 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 6 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 6 good Nameserver
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 6 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 |
| http://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.202.9.166
|
| 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://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.202.21.136
|
| 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://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.203.213.72
|
| 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://www.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.202.9.166
|
| 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://www.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.202.21.136
|
| 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://www.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.203.213.72
|
| 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://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c010:3f9c::1, Status 301
| http://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.202.21.136, Status -14
| 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://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c010:3f9c::1, Status 301
| http://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.202.9.166, Status -14
| 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://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c17:c19c::1, Status 301
| http://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.202.21.136, Status -14
| 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://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c17:c19c::1, Status 301
| http://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.202.9.166, Status -14
| 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://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c17:c19c::1, Status 301
| http://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.203.213.72, Status -14
| 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://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c010:3f9c::1, Status 301
| http://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.203.213.72, Status -14
| 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://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c2c:abf5::1, Status 301
| http://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.202.21.136, Status -14
| 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://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c2c:abf5::1, Status 301
| http://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.202.9.166, Status -14
| 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://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c2c:abf5::1, Status 301
| http://serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.203.213.72, Status -14
| 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.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c010:3f9c::1, Status 301
| http://www.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.202.21.136, Status -14
| 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.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c17:c19c::1, Status 301
| http://www.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.202.21.136, Status -14
| 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.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c17:c19c::1, Status 301
| http://www.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.202.9.166, Status -14
| 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.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c010:3f9c::1, Status 301
| http://www.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.202.9.166, Status -14
| 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.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c010:3f9c::1, Status 301
| http://www.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.203.213.72, Status -14
| 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.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c2c:abf5::1, Status 301
| http://www.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.202.21.136, Status -14
| 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.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c2c:abf5::1, Status 301
| http://www.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.202.9.166, Status -14
| 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.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c2c:abf5::1, Status 301
| http://www.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.203.213.72, Status -14
| 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.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:c17:c19c::1, Status 301
| http://www.serverhunter.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.203.213.72, Status -14
| 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://pawhost.de/
|
| 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://pawhost.de/
|
| 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://pawhost.de/
|
| 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://pawhost.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| 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.
|
| 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
|
| A | Good: All svg-Images greater 1024 Bytes without internal compression are compressed. Svg is an Xml-Application, so Compression reduces the size of the file. 3 images (type image/svg+xml, image/x-icon, image/vnd.microsoft.icon) found with compression.
|
| 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. 10 images (type image/png, image/jpg, image/jpeg, image/webp, image/gif) found without additional Compression. Not required because these images are already compressed
|
| A | Good: All CSS / JavaScript files are sent with a long Cache-Control header (minimum 7 days). So the browser can re-use these files, no download is required. 4 external CSS / JavaScript files with long Cache-Control max-age found
|
| 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), 13 with Cache-Control long enough, 17 complete.
|
| A | Good: All checked attribute values are enclosed in quotation marks (" or ').
|
| A | Good: All img-elements have a valid alt-attribute.: 8 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
|
| https://pawhost.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| 2.197 seconds
| Warning: 404 needs more then one second
|
| https://[2a01:04f8:0c17:c19c:0000:0000:0000:0001]/ 2a01:4f8:c17:c19c::1
| 2.104 seconds
| Warning: 404 needs more then one second
|
| https://[2a01:04f8:0c2c:abf5:0000:0000:0000:0001]/ 2a01:4f8:c2c:abf5::1
| 2.077 seconds
| Warning: 404 needs more then one second
|
| https://[2a01:04f8:c010:3f9c:0000:0000:0000:0001]/ 2a01:4f8:c010:3f9c::1
| 2.153 seconds
| Warning: 404 needs more then one second
|
| A | Duration: 213353 milliseconds, 213.353 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)