1. General Results, most used to calculate the result A name "domusproperties.org" is domain, public suffix is ".org", top-level-domain is ".org", top-level-domain-type is "generic", tld-manager is "Public Interest Registry (PIR)", num .org-domains preloaded: 7468 (complete: 220007) A Good: All ip addresses are public addresses A Good: Minimal 2 ip addresses per domain name found: domusproperties.org has 8 different ip addresses (authoritative). A Good: Minimal 2 ip addresses per domain name found: www.domusproperties.org has 2 different ip addresses (authoritative). A Good: Ipv4 and Ipv6 addresses per domain name found: domusproperties.org has 4 ipv4, 4 ipv6 addresses A Good: Ipv4 and Ipv6 addresses per domain name found: www.domusproperties.org has 1 ipv4, 1 ipv6 addresses A Good: No asked Authoritative Name Server had a timeout A Good: destination is https A Good - only one version with Http-Status 200 A Good: one preferred version: www is preferred A Good: No cookie sent via http. HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List. A Good: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset) A http://www.domusproperties.org/ 142.250.185.211 https://www.domusproperties.org/ Correct redirect http - https with the same domain name A http://www.domusproperties.org/ 142.250.185.243 https://www.domusproperties.org/ Correct redirect http - https with the same domain name A http://www.domusproperties.org/ 2a00:1450:4001:812::2013 https://www.domusproperties.org/ Correct redirect http - https with the same domain name B https://domusproperties.org/ 216.239.32.21 Missing HSTS-Header B https://domusproperties.org/ 216.239.34.21 Missing HSTS-Header B https://domusproperties.org/ 216.239.36.21 Missing HSTS-Header B https://domusproperties.org/ 216.239.38.21 Missing HSTS-Header B https://domusproperties.org/ 2001:4860:4802:32::15 Missing HSTS-Header B https://domusproperties.org/ 2001:4860:4802:34::15 Missing HSTS-Header B https://domusproperties.org/ 2001:4860:4802:36::15 Missing HSTS-Header B https://domusproperties.org/ 2001:4860:4802:38::15 Missing HSTS-Header B https://www.domusproperties.org/ 142.250.185.211 Missing HSTS-Header B https://www.domusproperties.org/ 142.250.185.243 Missing HSTS-Header B https://www.domusproperties.org/ 2a00:1450:4001:812::2013 Missing HSTS-Header B https://www.domusproperties.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Missing HSTS-Header D http://domusproperties.org/ 216.239.32.21 http://www.domusproperties.org/ Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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. D http://domusproperties.org/ 216.239.34.21 http://www.domusproperties.org/ Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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. D http://domusproperties.org/ 216.239.36.21 http://www.domusproperties.org/ Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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. D http://domusproperties.org/ 216.239.38.21 http://www.domusproperties.org/ Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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. D http://domusproperties.org/ 2001:4860:4802:32::15 http://www.domusproperties.org/ Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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. D http://domusproperties.org/ 2001:4860:4802:34::15 http://www.domusproperties.org/ Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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. D http://domusproperties.org/ 2001:4860:4802:36::15 http://www.domusproperties.org/ Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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. D http://domusproperties.org/ 2001:4860:4802:38::15 http://www.domusproperties.org/ Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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. D http://domusproperties.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 216.239.32.21 http://www.domusproperties.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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. D http://domusproperties.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 216.239.34.21 http://www.domusproperties.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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. D http://domusproperties.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 216.239.36.21 http://www.domusproperties.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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. D http://domusproperties.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 216.239.38.21 http://www.domusproperties.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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. D http://domusproperties.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:4860:4802:32::15 http://www.domusproperties.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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. D http://domusproperties.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:4860:4802:34::15 http://www.domusproperties.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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. D http://domusproperties.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:4860:4802:36::15 http://www.domusproperties.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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. D http://domusproperties.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:4860:4802:38::15 http://www.domusproperties.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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://www.domusproperties.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part. P https://216.239.32.21/ 216.239.32.21 Error creating a TLS-Connection: No more details available. P https://216.239.34.21/ 216.239.34.21 Error creating a TLS-Connection: No more details available. P https://216.239.36.21/ 216.239.36.21 Error creating a TLS-Connection: No more details available. P https://216.239.38.21/ 216.239.38.21 Error creating a TLS-Connection: No more details available. P https://[2001:4860:4802:0032:0000:0000:0000:0015]/ 2001:4860:4802:32::15 Error creating a TLS-Connection: No more details available. P https://[2001:4860:4802:0034:0000:0000:0000:0015]/ 2001:4860:4802:34::15 Error creating a TLS-Connection: No more details available. P https://[2001:4860:4802:0036:0000:0000:0000:0015]/ 2001:4860:4802:36::15 Error creating a TLS-Connection: No more details available. P https://[2001:4860:4802:0038:0000:0000:0000:0015]/ 2001:4860:4802:38::15 Error creating a TLS-Connection: No more details available. P https://142.250.185.211/ 142.250.185.211 Error creating a TLS-Connection: No more details available. P https://142.250.185.243/ 142.250.185.243 Error creating a TLS-Connection: No more details available. P https://[2a00:1450:4001:0812:0000:0000:0000:2013]/ 2a00:1450:4001:812::2013 Error creating a TLS-Connection: No more details available. 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 domusproperties.org, 8 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.domusproperties.org, 2 ip addresses. Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain domusproperties.org, 8 ip addresses. Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain www.domusproperties.org, 2 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.domusproperties.org 2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete) A www.domusproperties.org 142.250.185.211 Content-Security-Policy Ok: Header without syntax errors found: base-uri 'self';object-src 'none';report-uri /_/view/cspreport;script-src 'nonce-pLekkxPmg3KR3EyD8j-3eQ' 'unsafe-inline' 'unsafe-eval';worker-src 'self';frame-ancestors https://google-admin.corp.google.com/ B Info: Header-Element is deprecated. report-uri /_/view/cspreport F Bad: Missing default-src directive. A default-src directive is used if one of the specialized fetch directives (child-src, connect-src, font-src, frame-src, img-src, manifest-src, media-src, object-src, prefetch-src, script-src, style-src, worker-src) isn't defined. Missing default-src, all sources are allowed, that's bad. A default-src with 'none' or 'self' blocks that. 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. A Good: frame-ancestors directive found. That limits pages who are allowed to use this page in a frame / iframe / object / embed / applet. frame-ancestors is a navigation-directive, so default-src isn't used. A Good: base-uri directive found. That limits 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. C Critical: script-src with 'unsafe-inline' or 'unsafe-eval' and with a nonce found. Ok, better with the nonce, but not really good. Don't use 'unsafe' - declarations. 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 Ok: Nonce found. A X-Content-Type-Options Ok: Header without syntax errors found: nosniff A Referrer-Policy Ok: Header without syntax errors found: origin A X-Frame-Options Ok: Header without syntax errors found: DENY B Info: Header is deprecated. May not longer work in modern browsers. 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. A X-Xss-Protection Ok: Header without syntax errors found: 0 B Info: Header is deprecated. May not longer work in modern browsers. 0 A www.domusproperties.org 142.250.185.243 Content-Security-Policy Ok: Header without syntax errors found: base-uri 'self';object-src 'none';report-uri /_/view/cspreport;script-src 'nonce-j2PWicXpSCizN6IRGw5CKQ' 'unsafe-inline' 'unsafe-eval';worker-src 'self';frame-ancestors https://google-admin.corp.google.com/ B Info: Header-Element is deprecated. report-uri /_/view/cspreport F Bad: Missing default-src directive. A default-src directive is used if one of the specialized fetch directives (child-src, connect-src, font-src, frame-src, img-src, manifest-src, media-src, object-src, prefetch-src, script-src, style-src, worker-src) isn't defined. Missing default-src, all sources are allowed, that's bad. A default-src with 'none' or 'self' blocks that. 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. A Good: frame-ancestors directive found. That limits pages who are allowed to use this page in a frame / iframe / object / embed / applet. frame-ancestors is a navigation-directive, so default-src isn't used. A Good: base-uri directive found. That limits 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. C Critical: script-src with 'unsafe-inline' or 'unsafe-eval' and with a nonce found. Ok, better with the nonce, but not really good. Don't use 'unsafe' - declarations. 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 Ok: Nonce found. A X-Content-Type-Options Ok: Header without syntax errors found: nosniff A Referrer-Policy Ok: Header without syntax errors found: origin A X-Frame-Options Ok: Header without syntax errors found: DENY B Info: Header is deprecated. May not longer work in modern browsers. 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. A X-Xss-Protection Ok: Header without syntax errors found: 0 B Info: Header is deprecated. May not longer work in modern browsers. 0 A www.domusproperties.org 2a00:1450:4001:812::2013 Content-Security-Policy Ok: Header without syntax errors found: base-uri 'self';object-src 'none';report-uri /_/view/cspreport;script-src 'nonce-Ez-ga8fKRLXHz3DEJKcfmw' 'unsafe-inline' 'unsafe-eval';worker-src 'self';frame-ancestors https://google-admin.corp.google.com/ B Info: Header-Element is deprecated. report-uri /_/view/cspreport F Bad: Missing default-src directive. A default-src directive is used if one of the specialized fetch directives (child-src, connect-src, font-src, frame-src, img-src, manifest-src, media-src, object-src, prefetch-src, script-src, style-src, worker-src) isn't defined. Missing default-src, all sources are allowed, that's bad. A default-src with 'none' or 'self' blocks that. 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. A Good: frame-ancestors directive found. That limits pages who are allowed to use this page in a frame / iframe / object / embed / applet. frame-ancestors is a navigation-directive, so default-src isn't used. A Good: base-uri directive found. That limits 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. C Critical: script-src with 'unsafe-inline' or 'unsafe-eval' and with a nonce found. Ok, better with the nonce, but not really good. Don't use 'unsafe' - declarations. 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 Ok: Nonce found. A X-Content-Type-Options Ok: Header without syntax errors found: nosniff A Referrer-Policy Ok: Header without syntax errors found: origin A X-Frame-Options Ok: Header without syntax errors found: DENY B Info: Header is deprecated. May not longer work in modern browsers. 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. A X-Xss-Protection Ok: Header without syntax errors found: 0 B Info: Header is deprecated. May not longer work in modern browsers. 0 F www.domusproperties.org 142.250.185.211 Permissions-Policy Critical: Missing Header: F www.domusproperties.org 142.250.185.243 Permissions-Policy Critical: Missing Header: F www.domusproperties.org 2a00:1450:4001:812::2013 Permissions-Policy Critical: Missing Header: A Good: Different combinations of domain names and ip addresses checked, Content-Security-Policy - Header with a nonce declaration sent: Every combination domain + ip with an own, unique nonce. 3. DNS- and NameServer - Checks A Info:: 13 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers. A Info:: 13 Queries complete, 13 with IPv6, 0 with IPv4. A Good: All DNS Queries done via IPv6. Ok (4 - 8):: An average of 3.3 queries per domain name server required to find all ip addresses of all name servers. A Info:: 4 different Name Servers found: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com, 4 Name Servers included in Delegation: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com, 4 Name Servers included in 1 Zone definitions: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com, 1 Name Servers listed in SOA.Primary: ns-cloud-a1.googledomains.com. A Good: Only one SOA.Primary Name Server found.: ns-cloud-a1.googledomains.com. A Good: SOA.Primary Name Server included in the delegation set.: ns-cloud-a1.googledomains.com. 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-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com 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: com 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: googledomains.com A Good: Name servers with different Country locations found: 4 Name Servers, 2 Countries: CA, US A Info: Ipv4-Subnet-list: 4 Name Servers, 1 different subnets (first Byte): 216., 1 different subnets (first two Bytes): 216.239., 4 different subnets (first three Bytes): 216.239.32., 216.239.34., 216.239.36., 216.239.38. A Good: Name Server IPv4-addresses from different subnet found: A Info: IPv6-Subnet-list: 4 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:4860:, 1 different subnets (first three blocks): 2001:4860:4802:, 4 different subnets (first four blocks): 2001:4860:4802:0032:, 2001:4860:4802:0034:, 2001:4860:4802:0036:, 2001:4860:4802:0038: 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: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 8 good Nameserver A Good: All SOA have the same Serial Number A Good: CAA entries found, creating certificate is limited: pki.goog is allowed to create 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. A Good: Every https result with status 200 supports GZip. https://www.domusproperties.org/ 142.250.185.211 Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header. https://www.domusproperties.org/ 142.250.185.243 Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header. https://www.domusproperties.org/ 2a00:1450:4001:812::2013 Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header. https://www.domusproperties.org/ 142.250.185.211 Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space. https://www.domusproperties.org/ 142.250.185.243 Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space. https://www.domusproperties.org/ 2a00:1450:4001:812::2013 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. https://www.domusproperties.org/ 142.250.185.211 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.: 2 script elements without defer/async. https://www.domusproperties.org/ 142.250.185.243 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.: 2 script elements without defer/async. https://www.domusproperties.org/ 2a00:1450:4001:812::2013 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.: 2 script elements without defer/async. https://www.domusproperties.org/.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.: 2 script elements without defer/async. Warning: CSS / JavaScript found without GZip support. Send these ressources with GZip. 4 external CSS / JavaScript files without GZip found - 16 with GZip, 20 complete Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 0 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 12 with Cache-Control max-age too short (minimum 7 days), 8 with Cache-Control long enough, 20 complete. A Good: All checked attribute values are enclosed in quotation marks (" or '). 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://www.domusproperties.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.154 seconds Warning: 404 needs more then one second A Info: Different Server-Headers found A Duration: 217503 milliseconds, 217.503 seconds