| 1. General Results, most used to calculate the result |
| A | name "hostux.app" is domain, public suffix is ".app", top-level-domain is ".app", top-level-domain-type is "generic", tld-manager is "Charleston Road Registry Inc.", num .app-domains preloaded: 46 (complete: 271405)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: hostux.app has 2 different ip addresses (authoritative).
|
| A | Good: Minimal 2 ip addresses per domain name found: www.hostux.app has 2 different ip addresses (authoritative).
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: hostux.app has 1 ipv4, 1 ipv6 addresses
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: www.hostux.app has 1 ipv4, 1 ipv6 addresses
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | https://mail.hostux.app/
| https://mail.hostux.app/login
| Correct redirect https to https
|
| A | https://hostux.app/ 2001:41d0:203:783e::8725
| https://hostux.app/login
| Correct redirect https to https
|
| A | Good: destination is https
|
| A | Good: No cookie sent via http.
|
| A | Good: every cookie sent via https is marked as secure
|
| A | Good: Every cookie has a SameSite Attribute with a correct value Strict/Lax/None
|
| 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)
|
| A | https://www.hostux.app/ 2001:41d0:203:783e::8725
|
| Url with Content-Type - parse error: Header: application/octet-stream,text/plain, parse error: ,text/plain
|
| A | https://mta-sts.hostux.app/.well-known/mta-sts.txt 2001:41d0:203:783e::8725
|
| Url with Content-Type - parse error: Header: text/plain; charset=utf-8,text/plain, parse error: charset=utf-8,text/plain
|
| B | https://www.hostux.app/ 2001:41d0:203:783e::8725
|
| Missing HSTS-Header
|
| B | https://mail.hostux.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Missing HSTS-Header
|
| 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.
|
| E | http://hostux.app/ 2001:41d0:203:783e::8725
| https://mail.hostux.app/
| 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.hostux.app/ 2001:41d0:203:783e::8725
| https://*.hostux.app/
| 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.
|
| K | http://hostux.app/ 213.32.87.25, Status -14
| http://hostux.app/ 2001:41d0:203:783e::8725, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://www.hostux.app/ 213.32.87.25, Status -14
| http://www.hostux.app/ 2001:41d0:203:783e::8725, Status 301
| Configuration problem - different ip addresses with different status
|
| K | https://hostux.app/ 213.32.87.25, Status -14
| https://hostux.app/ 2001:41d0:203:783e::8725, Status 302
| Configuration problem - different ip addresses with different status
|
| K | http://hostux.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 213.32.87.25, Status -14
| http://hostux.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:41d0:203:783e::8725, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://www.hostux.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 213.32.87.25, Status -14
| http://www.hostux.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:41d0:203:783e::8725, Status 301
| Configuration problem - different ip addresses with different status
|
| K | https://www.hostux.app/ 213.32.87.25, Status -14
| https://www.hostux.app/ 2001:41d0:203:783e::8725, Status 200
| Configuration problem - different ip addresses with different status
|
| K | https://mta-sts.hostux.app/.well-known/mta-sts.txt 213.32.87.25, Status -14
| https://mta-sts.hostux.app/.well-known/mta-sts.txt 2001:41d0:203:783e::8725, Status 200
| Configuration problem - different ip addresses with different status
|
| N | https://www.hostux.app/ 2001:41d0:203:783e::8725
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://[2001:41d0:0203:783e:0000:0000:0000:8725]/ 2001:41d0:203:783e::8725
| https://%5B2001:41d0:203:783e::8725%5D/login
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | www.hostux.app:25
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://mta-sts.hostux.app/.well-known/mta-sts.txt 2001:41d0:203:783e::8725
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| O |
|
| R | http://www.hostux.app/ 2001:41d0:203:783e::8725
| https://*.hostux.app/
| Redirect to not existing domain
|
| R | http://www.hostux.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:41d0:203:783e::8725
| https://*.hostux.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| Redirect to not existing domain
|
| R | https://[2001:41d0:0203:783e:0000:0000:0000:8725]/ 2001:41d0:203:783e::8725
| https://%5B2001:41d0:203:783e::8725%5D/login
| Redirect to not existing domain
|
| Fatal: More then one ip address per domain name found, but checking all ip addresses different http status found.: Domain hostux.app, 2 ip addresses, 2 different http results.
|
| Fatal: More then one ip address per domain name found, but checking all ip addresses different http status found.: Domain www.hostux.app, 2 ip addresses, 2 different http results.
|
| A | Good: _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Domainname: _mta-sts.hostux.app
|
| A | Good: _mta-sts TXT record is valid.
|
| A | Good: Subdomain mta-sts found: Subdomain-name: mta-sts.hostux.app, ip : 213.32.87.25
|
| A | Good: Subdomain mta-sts found: Subdomain-name: mta-sts.hostux.app, ip : 2001:41d0:203:783e::8725
|
| A | Good: /.well-known/mta-sts.txt with http status 200 found. Complete path: https://mta-sts.hostux.app/.well-known/mta-sts.txt - ip : 2001:41d0:203:783e::8725
|
| A | Good: mta-sts.txt has the required names "version", "mode", "max_age". mta-sts.hostux.app, ip : 2001:41d0:203:783e::8725
|
| A | Good: Minimal one mx definition found. mta-sts.hostux.app, ip : 2001:41d0:203:783e::8725
|
| B | Bad: Valid _mta-sts TXT and ip address of the subdomain mta-sts found, but no connection possible. https://mta-sts.hostux.app/.well-known/mta-sts.txt, ip : 213.32.87.25
|
| B | Bad: Valid _mta-sts TXT found, but subdomain mta-sts with invalid certificate mta-sts.hostux.app, ip : 2001:41d0:203:783e::8725
|
| 2. Header-Checks |
| A | hostux.app
| Content-Security-Policy
| Ok: Header without syntax errors found: default-src 'self' passwd.hostux.net; script-src 'self' 'unsafe-inline' 'unsafe-eval' passwd.hostux.net; img-src 'self' data: passwd.hostux.net; style-src 'self' 'unsafe-inline' passwd.hostux.net; font-src 'self' passwd.hostux.net; object-src 'none';
|
| A |
|
| Good: default-src without 'unsafe-inline' or 'unsave-eval'. font-src
|
| E |
|
| Bad: No form-action directive found. Use one to limit the form - action - destinations. form-action is a navigation-directive, so default-src isn't used.
|
| E |
|
| Bad: No frame-ancestors directive found. Use one to limit the pages allowed to use this page in frame / iframe / object / embed / applet. frame-ancestors is a navigation-directive, so default-src isn't used.
|
| E |
|
| Bad: No base-uri directive found. Use one to limit the URLs which can be used in a document's <base> element. Because it's a document directive, default-src isn't used, so an own directive is required.
|
| A |
|
| Good: object-src only with 'none' or 'self' found, no scheme, no other urls. That blocks object / embed / applet - elements.
|
| F |
|
| Critical: script-src with 'unsafe-inline' or 'unsafe-eval' and without a nonce found. That's dangerous, don't use it. If you really need one of these unsafe directives, add a nonce.
|
| A |
|
| Good: script-src without * and a scheme found.
|
| A |
|
| Good: script-src without data: schema found. Why is this important? The data: schema allows hidden code injection. Insert <script src='data:application/javascript;base64,YWxlcnQoJ1hTUycpOw=='></script> in your page and see what happens.
|
| A |
|
| Good: frame-src without data: defined or frame-src missing and the default-src used as fallback not allows the data: schema. That blocks hidden code injection. Insert <iframe src="data:text/html;charset=utf-8;base64,PCFET0NUWVBFIGh0bWw+PGh0bWw+PGJvZHk+PHA+YmVmb3JlPHNjcmlwdCB0eXBlPSJ0ZXh0L2phdmFzY3JpcHQiPmFsZXJ0KCdYU1MnKTwvc2NyaXB0PjxwPmFmdGVyPC9ib2R5PjwvaHRtbD4="></iframe> in your page and see what happens.
|
| C |
|
| Info: default-src and some other fetch directives have the same list of values. Remove the other fetch directive, default-src is used as fallback. Directives to remove: font-src
|
| A |
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
| A |
| Referrer-Policy
| Ok: Header without syntax errors found: origin-when-cross-origin
|
| A |
| X-Frame-Options
| Ok: Header without syntax errors found: SAMEORIGIN
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. SAMEORIGIN. 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.
|
| A |
| Expect-CT
| Ok: Header without syntax errors found: enforce, max-age=604800
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. enforce, max-age=604800
|
| A |
| X-Xss-Protection
| Ok: Header without syntax errors found: 1; mode=block
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. 1; mode=block
|
| A | mail.hostux.app
| Content-Security-Policy
| Ok: Header without syntax errors found: default-src 'self' passwd.hostux.net; script-src 'self' 'unsafe-inline' 'unsafe-eval' passwd.hostux.net; img-src 'self' data: passwd.hostux.net; style-src 'self' 'unsafe-inline' passwd.hostux.net; font-src 'self' passwd.hostux.net; object-src 'none';
|
| A |
|
| Good: default-src without 'unsafe-inline' or 'unsave-eval'. font-src
|
| E |
|
| Bad: No form-action directive found. Use one to limit the form - action - destinations. form-action is a navigation-directive, so default-src isn't used.
|
| E |
|
| Bad: No frame-ancestors directive found. Use one to limit the pages allowed to use this page in frame / iframe / object / embed / applet. frame-ancestors is a navigation-directive, so default-src isn't used.
|
| E |
|
| Bad: No base-uri directive found. Use one to limit the URLs which can be used in a document's <base> element. Because it's a document directive, default-src isn't used, so an own directive is required.
|
| A |
|
| Good: object-src only with 'none' or 'self' found, no scheme, no other urls. That blocks object / embed / applet - elements.
|
| F |
|
| Critical: script-src with 'unsafe-inline' or 'unsafe-eval' and without a nonce found. That's dangerous, don't use it. If you really need one of these unsafe directives, add a nonce.
|
| A |
|
| Good: script-src without * and a scheme found.
|
| A |
|
| Good: script-src without data: schema found. Why is this important? The data: schema allows hidden code injection. Insert <script src='data:application/javascript;base64,YWxlcnQoJ1hTUycpOw=='></script> in your page and see what happens.
|
| A |
|
| Good: frame-src without data: defined or frame-src missing and the default-src used as fallback not allows the data: schema. That blocks hidden code injection. Insert <iframe src="data:text/html;charset=utf-8;base64,PCFET0NUWVBFIGh0bWw+PGh0bWw+PGJvZHk+PHA+YmVmb3JlPHNjcmlwdCB0eXBlPSJ0ZXh0L2phdmFzY3JpcHQiPmFsZXJ0KCdYU1MnKTwvc2NyaXB0PjxwPmFmdGVyPC9ib2R5PjwvaHRtbD4="></iframe> in your page and see what happens.
|
| C |
|
| Info: default-src and some other fetch directives have the same list of values. Remove the other fetch directive, default-src is used as fallback. Directives to remove: font-src
|
| A |
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
| A |
| Referrer-Policy
| Ok: Header without syntax errors found: origin-when-cross-origin
|
| A |
| X-Frame-Options
| Ok: Header without syntax errors found: SAMEORIGIN
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. SAMEORIGIN. 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.
|
| A |
| Expect-CT
| Ok: Header without syntax errors found: enforce, max-age=604800
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. enforce, max-age=604800
|
| A |
| X-Xss-Protection
| Ok: Header without syntax errors found: 1; mode=block
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. 1; mode=block
|
| F | hostux.app
| Permissions-Policy
| Critical: Missing Header:
|
| B | hostux.app
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | hostux.app
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | hostux.app
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| F | www.hostux.app 2001:41d0:203:783e::8725
| Content-Security-Policy
| Critical: Missing Header:
|
| F | www.hostux.app 2001:41d0:203:783e::8725
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | www.hostux.app 2001:41d0:203:783e::8725
| Referrer-Policy
| Critical: Missing Header:
|
| F | www.hostux.app 2001:41d0:203:783e::8725
| Permissions-Policy
| Critical: Missing Header:
|
| B | www.hostux.app 2001:41d0:203:783e::8725
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | www.hostux.app 2001:41d0:203:783e::8725
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | www.hostux.app 2001:41d0:203:783e::8725
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| F | mail.hostux.app
| Permissions-Policy
| Critical: Missing Header:
|
| B | mail.hostux.app
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | mail.hostux.app
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | mail.hostux.app
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 18 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
|
| A | Info:: 18 Queries complete, 18 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:: 4 different Name Servers found: ns1.gandi.net, ns-212-b.gandi.net, ns-224-c.gandi.net, ns-49-a.gandi.net, 3 Name Servers included in Delegation: ns-212-b.gandi.net, ns-224-c.gandi.net, ns-49-a.gandi.net, 3 Name Servers included in 1 Zone definitions: ns-212-b.gandi.net, ns-224-c.gandi.net, ns-49-a.gandi.net, 1 Name Servers listed in SOA.Primary: ns1.gandi.net.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.gandi.net.
|
| Error: SOA.Primary Name Server not included in the delegation set.: ns1.gandi.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: ns-212-b.gandi.net, ns-224-c.gandi.net, ns-49-a.gandi.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: 4 different Name Servers found
|
| A | Good: All name servers have ipv4- and ipv6-addresses.: 4 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.: 4 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: gandi.net
|
| Warning: All Name Servers from the same Country / IP location.: 4 Name Servers, 1 Countries: FR
|
| A | Info: Ipv4-Subnet-list: 4 Name Servers, 3 different subnets (first Byte): 173., 213., 217., 3 different subnets (first two Bytes): 173.246., 213.167., 217.70., 3 different subnets (first three Bytes): 173.246.100., 213.167.230., 217.70.187.
|
| A | Good: Name Server IPv4-addresses from different subnet found:
|
| A | Info: IPv6-Subnet-list: 4 Name Servers with IPv6, 2 different subnets (first block): 2001:, 2604:, 2 different subnets (first two blocks): 2001:4b98:, 2604:3400:, 3 different subnets (first three blocks): 2001:4b98:aaaa:, 2001:4b98:aaab:, 2604:3400:aaac:, 3 different subnets (first four blocks): 2001:4b98:aaaa:0000:, 2001:4b98:aaab:0000:, 2604:3400:aaac:0000:
|
| A | Good: Name Server IPv6 addresses from different subnets found.
|
| A | Good: Nameserver supports TCP connections: 8 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 8 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
|
| A | Good: All SOA have the same Serial Number
|
| A | Good: CAA entries found, creating certificate is limited: comodoca.com is allowed to create certificates
|
| 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: sectigo.com is allowed to create certificates
|
| A | Good: CAA entries found, creating certificate is limited: sectigo.com is allowed to create wildcard-certificates
|
| 4. Content- and Performance-critical Checks |
| http://hostux.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 213.32.87.25
|
| 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.hostux.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 213.32.87.25
|
| 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.
|
| https://*.hostux.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Fatal: Check of /.well-known/acme-challenge/random-filename redirects to not-existing domain. Creating a Letsencrypt certificate via http-01 challenge can't work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://hostux.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:41d0:203:783e::8725, Status 301
| http://hostux.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 213.32.87.25, 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.hostux.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:41d0:203:783e::8725, Status 301
| http://www.hostux.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 213.32.87.25, 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://hostux.app/login
|
| 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://mail.hostux.app/login
|
| Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
|
| A | Good: Every https connection via port 443 supports the http/2 protocol via ALPN.
|
| A | Info: No img element found, no alt attribute checked
|
| A | Good: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
|
| https://mail.hostux.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| 6.937 seconds
| Warning: 404 needs more then one second
|
| A | Info: Different Server-Headers found
|
| A | Duration: 960153 milliseconds, 960.153 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)