1. General Results, most used to calculate the result A name "vaan.eu.org" is domain, public suffix is ".eu.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: vaan.eu.org has 2 different ip addresses (authoritative). A Good: Minimal 2 ip addresses per domain name found: www.vaan.eu.org has 2 different ip addresses (authoritative). A Good: Ipv4 and Ipv6 addresses per domain name found: vaan.eu.org has 1 ipv4, 1 ipv6 addresses A Good: Ipv4 and Ipv6 addresses per domain name found: www.vaan.eu.org has 1 ipv4, 1 ipv6 addresses A Good: destination is https A Good - only one version with Http-Status 200 A Good: one preferred version: non-www is preferred 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 (4 urls) https://188.25.199.28/ 188.25.199.28 Url with incomplete Content-Type - header - missing charset http://vaan.eu.org/ 188.25.199.28 wc_session_ids[default]=7a4926569d164a072e07df60212dbe4451bc875d; expires=Sat, 18-Mar-2023 16:11:16 GMT; Max-Age=500; path=/; HttpOnly Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative. http://vaan.eu.org/ 188.25.199.28 wc_session_ids[all_forms]=54acd19b3a82e467403150dae217ab1d220610b8; expires=Sat, 18-Mar-2023 16:11:16 GMT; Max-Age=500; path=/; HttpOnly Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative. http://vaan.eu.org/ 188.25.199.28 wc_session_ids[multi][0]=ae44dde07cba666846a7b44a34ef618478676eda; expires=Sat, 18-Mar-2023 16:11:16 GMT; Max-Age=500; path=/ Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative. http://vaan.eu.org/ 188.25.199.28 wc_session_ids[multi][1]=25b7425346da426e202f1234dfff1a693185ac44; expires=Sat, 18-Mar-2023 16:11:16 GMT; Max-Age=500; path=/ Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative. http://vaan.eu.org/ 188.25.199.28 wc_session_ids[multi][2]=e01fcc5cf21ff9cb146bc30020f50e84085a1de5; expires=Sat, 18-Mar-2023 16:11:16 GMT; Max-Age=500; path=/ Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative. http://vaan.eu.org/ 188.25.199.28 wc_session_ids[multi][3]=5e5e39c4b55d641086e894dfe1828dae86de3b4c; expires=Sat, 18-Mar-2023 16:11:16 GMT; Max-Age=500; path=/ Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative. http://vaan.eu.org/ 188.25.199.28 wc_session_ids[multi][4]=94c8ea2c869f191be29338237b35fc5397b61d64; expires=Sat, 18-Mar-2023 16:11:16 GMT; Max-Age=500; path=/ Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative. http://www.vaan.eu.org/ 188.25.199.28 wc_session_ids[default]=b8704933765c5b3719d05a7113bfb73dd2629c30; expires=Sat, 18-Mar-2023 16:11:18 GMT; Max-Age=500; path=/; HttpOnly Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative. http://www.vaan.eu.org/ 188.25.199.28 wc_session_ids[all_forms]=645ae63df01346dcd0b0ed1a263d209bc0bff981; expires=Sat, 18-Mar-2023 16:11:18 GMT; Max-Age=500; path=/; HttpOnly Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative. http://www.vaan.eu.org/ 188.25.199.28 wc_session_ids[multi][0]=0544c624fdeafa28fd27227ffa188347bab0d6ea; expires=Sat, 18-Mar-2023 16:11:18 GMT; Max-Age=500; path=/ Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative. http://www.vaan.eu.org/ 188.25.199.28 wc_session_ids[multi][1]=10955cb58fe2ecdeae1e2b2e9fda469df42d3994; expires=Sat, 18-Mar-2023 16:11:18 GMT; Max-Age=500; path=/ Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative. http://www.vaan.eu.org/ 188.25.199.28 wc_session_ids[multi][2]=e7efd6919c7d48d7bd7c15cfb27a09bdee643805; expires=Sat, 18-Mar-2023 16:11:18 GMT; Max-Age=500; path=/ Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative. http://www.vaan.eu.org/ 188.25.199.28 wc_session_ids[multi][3]=50738fc6cc2065fa7be9e9f1ebcdd5638c011fb7; expires=Sat, 18-Mar-2023 16:11:18 GMT; Max-Age=500; path=/ Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative. http://www.vaan.eu.org/ 188.25.199.28 wc_session_ids[multi][4]=1e8a2f50dc3020a63d546fbb53c4c29391b4618d; expires=Sat, 18-Mar-2023 16:11:18 GMT; Max-Age=500; path=/ Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative. B https://www.vaan.eu.org/ 188.25.199.28 wc_session_ids[multi][0]=3f9e4d5aff379e9def0fba642a0e924b2a29f703; expires=Sat, 18-Mar-2023 16:11:25 GMT; Max-Age=500; path=/ Cookie sent via https, but not marked as secure B https://www.vaan.eu.org/ 188.25.199.28 wc_session_ids[multi][1]=68d23c3f6a5e5ee30974801058b1ef3f8500c66f; expires=Sat, 18-Mar-2023 16:11:25 GMT; Max-Age=500; path=/ Cookie sent via https, but not marked as secure B https://www.vaan.eu.org/ 188.25.199.28 wc_session_ids[multi][2]=0da934fa0c82fc12a515802e7865f70a058e1e19; expires=Sat, 18-Mar-2023 16:11:25 GMT; Max-Age=500; path=/ Cookie sent via https, but not marked as secure B https://www.vaan.eu.org/ 188.25.199.28 wc_session_ids[multi][3]=cbc23f0aa87a3440b00e8ddf2f0ca2b98496a937; expires=Sat, 18-Mar-2023 16:11:25 GMT; Max-Age=500; path=/ Cookie sent via https, but not marked as secure B https://www.vaan.eu.org/ 188.25.199.28 wc_session_ids[multi][4]=ba5984c430f1701f27e4d5e675416f122d182001; expires=Sat, 18-Mar-2023 16:11:25 GMT; Max-Age=500; path=/ Cookie sent via https, but not marked as secure B http://vaan.eu.org/ 188.25.199.28 wc_session_ids[default]=7a4926569d164a072e07df60212dbe4451bc875d; expires=Sat, 18-Mar-2023 16:11:16 GMT; Max-Age=500; path=/; HttpOnly Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B http://vaan.eu.org/ 188.25.199.28 wc_session_ids[all_forms]=54acd19b3a82e467403150dae217ab1d220610b8; expires=Sat, 18-Mar-2023 16:11:16 GMT; Max-Age=500; path=/; HttpOnly Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B http://vaan.eu.org/ 188.25.199.28 wc_session_ids[multi][0]=ae44dde07cba666846a7b44a34ef618478676eda; expires=Sat, 18-Mar-2023 16:11:16 GMT; Max-Age=500; path=/ Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B http://vaan.eu.org/ 188.25.199.28 wc_session_ids[multi][1]=25b7425346da426e202f1234dfff1a693185ac44; expires=Sat, 18-Mar-2023 16:11:16 GMT; Max-Age=500; path=/ Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B http://vaan.eu.org/ 188.25.199.28 wc_session_ids[multi][2]=e01fcc5cf21ff9cb146bc30020f50e84085a1de5; expires=Sat, 18-Mar-2023 16:11:16 GMT; Max-Age=500; path=/ Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B http://vaan.eu.org/ 188.25.199.28 wc_session_ids[multi][3]=5e5e39c4b55d641086e894dfe1828dae86de3b4c; expires=Sat, 18-Mar-2023 16:11:16 GMT; Max-Age=500; path=/ Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B http://vaan.eu.org/ 188.25.199.28 wc_session_ids[multi][4]=94c8ea2c869f191be29338237b35fc5397b61d64; expires=Sat, 18-Mar-2023 16:11:16 GMT; Max-Age=500; path=/ Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B http://www.vaan.eu.org/ 188.25.199.28 wc_session_ids[default]=b8704933765c5b3719d05a7113bfb73dd2629c30; expires=Sat, 18-Mar-2023 16:11:18 GMT; Max-Age=500; path=/; HttpOnly Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B http://www.vaan.eu.org/ 188.25.199.28 wc_session_ids[all_forms]=645ae63df01346dcd0b0ed1a263d209bc0bff981; expires=Sat, 18-Mar-2023 16:11:18 GMT; Max-Age=500; path=/; HttpOnly Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B http://www.vaan.eu.org/ 188.25.199.28 wc_session_ids[multi][0]=0544c624fdeafa28fd27227ffa188347bab0d6ea; expires=Sat, 18-Mar-2023 16:11:18 GMT; Max-Age=500; path=/ Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B http://www.vaan.eu.org/ 188.25.199.28 wc_session_ids[multi][1]=10955cb58fe2ecdeae1e2b2e9fda469df42d3994; expires=Sat, 18-Mar-2023 16:11:18 GMT; Max-Age=500; path=/ Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B http://www.vaan.eu.org/ 188.25.199.28 wc_session_ids[multi][2]=e7efd6919c7d48d7bd7c15cfb27a09bdee643805; expires=Sat, 18-Mar-2023 16:11:18 GMT; Max-Age=500; path=/ Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B http://www.vaan.eu.org/ 188.25.199.28 wc_session_ids[multi][3]=50738fc6cc2065fa7be9e9f1ebcdd5638c011fb7; expires=Sat, 18-Mar-2023 16:11:18 GMT; Max-Age=500; path=/ Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B http://www.vaan.eu.org/ 188.25.199.28 wc_session_ids[multi][4]=1e8a2f50dc3020a63d546fbb53c4c29391b4618d; expires=Sat, 18-Mar-2023 16:11:18 GMT; Max-Age=500; path=/ Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://www.vaan.eu.org/ 188.25.199.28 wc_session_ids[default]=3ce1dff9fa9cd80ccd7f0215196f45c60b11bf83; expires=Sat, 18-Mar-2023 16:11:25 GMT; Max-Age=500; path=/; secure; HttpOnly Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://www.vaan.eu.org/ 188.25.199.28 wc_session_ids[all_forms]=d04ac59286edfa7253f62348e8ef8719abb4ea38; expires=Sat, 18-Mar-2023 16:11:25 GMT; Max-Age=500; path=/; secure; HttpOnly Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://www.vaan.eu.org/ 188.25.199.28 wc_session_ids[multi][0]=3f9e4d5aff379e9def0fba642a0e924b2a29f703; expires=Sat, 18-Mar-2023 16:11:25 GMT; Max-Age=500; path=/ Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://www.vaan.eu.org/ 188.25.199.28 wc_session_ids[multi][1]=68d23c3f6a5e5ee30974801058b1ef3f8500c66f; expires=Sat, 18-Mar-2023 16:11:25 GMT; Max-Age=500; path=/ Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://www.vaan.eu.org/ 188.25.199.28 wc_session_ids[multi][2]=0da934fa0c82fc12a515802e7865f70a058e1e19; expires=Sat, 18-Mar-2023 16:11:25 GMT; Max-Age=500; path=/ Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://www.vaan.eu.org/ 188.25.199.28 wc_session_ids[multi][3]=cbc23f0aa87a3440b00e8ddf2f0ca2b98496a937; expires=Sat, 18-Mar-2023 16:11:25 GMT; Max-Age=500; path=/ Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://www.vaan.eu.org/ 188.25.199.28 wc_session_ids[multi][4]=ba5984c430f1701f27e4d5e675416f122d182001; expires=Sat, 18-Mar-2023 16:11:25 GMT; Max-Age=500; path=/ Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. K http://vaan.eu.org/ 188.25.199.28, Status 301 http://vaan.eu.org/ 2a02:2f00:b20a:2000::2, Status -2 Configuration problem - different ip addresses with different status K http://www.vaan.eu.org/ 188.25.199.28, Status 301 http://www.vaan.eu.org/ 2a02:2f00:b20a:2000::2, Status -2 Configuration problem - different ip addresses with different status K https://vaan.eu.org/ 188.25.199.28, Status 200 https://vaan.eu.org/ 2a02:2f00:b20a:2000::2, Status -2 Configuration problem - different ip addresses with different status K https://www.vaan.eu.org/ 188.25.199.28, Status 301 https://www.vaan.eu.org/ 2a02:2f00:b20a:2000::2, Status -2 Configuration problem - different ip addresses with different status K http://vaan.eu.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 188.25.199.28, Status 404 http://vaan.eu.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:2f00:b20a:2000::2, Status -2 Configuration problem - different ip addresses with different status K http://www.vaan.eu.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 188.25.199.28, Status 404 http://www.vaan.eu.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:2f00:b20a:2000::2, Status -2 Configuration problem - different ip addresses with different status N https://188.25.199.28/ 188.25.199.28 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N vaan.eu.org:8443 Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors N www.vaan.eu.org:8443 Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors V http://vaan.eu.org/ 2a02:2f00:b20a:2000::2 Connect failure - perhaps firewall V http://www.vaan.eu.org/ 2a02:2f00:b20a:2000::2 Connect failure - perhaps firewall V https://vaan.eu.org/ 2a02:2f00:b20a:2000::2 Connect failure - perhaps firewall V https://www.vaan.eu.org/ 2a02:2f00:b20a:2000::2 Connect failure - perhaps firewall V http://vaan.eu.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:2f00:b20a:2000::2 Connect failure - perhaps firewall V http://www.vaan.eu.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:2f00:b20a:2000::2 Connect failure - perhaps firewall V https://[2a02:2f00:b20a:2000:0000:0000:0000:0002]/ 2a02:2f00:b20a:2000::2 Connect failure - perhaps firewall X Fatal error: Nameserver isn't defined or has timeout X Fatal error: Nameserver doesn't support TCP connection: get.desec.io / 2a01:4f8:10a:1044:deec:642:ac10:80: Timeout 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 vaan.eu.org, 2 ip addresses. A Good: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain www.vaan.eu.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.vaan.eu.org 2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete) A vaan.eu.org 188.25.199.28 Content-Security-Policy Ok: Header without syntax errors found: upgrade-insecure-requests 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. 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. F Critical: No object-src and no default-src as fallback defined. So object / embed / applet can load every resource. That's fatal. F Critical: No script-src and no default-src as fallback defined. So scripts are unlimited. That's fatal. A X-Content-Type-Options Ok: Header without syntax errors found: nosniff A Referrer-Policy Ok: Header without syntax errors found: strict-origin-when-cross-origin A Permissions-Policy Ok: Header without syntax errors found: geolocation=self 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 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 3. DNS- and NameServer - Checks A Info:: 6 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers. A Info:: 6 Queries complete, 6 with IPv6, 0 with IPv4. A Good: All DNS Queries done via IPv6. A Good: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns2.desec.org (157.53.224.1, 2607:f740:e00a:deec::2), ns1.desec.io (2607:f740:e633:deec::2, 45.54.76.1) A Good (1 - 3.0):: An average of 2.0 queries per domain name server required to find all ip addresses of all name servers. A Info:: 3 different Name Servers found: get.desec.io, ns1.desec.io, ns2.desec.org, 2 Name Servers included in Delegation: ns1.desec.io, ns2.desec.org, 2 Name Servers included in 2 Zone definitions: ns1.desec.io, ns2.desec.org, 1 Name Servers listed in SOA.Primary: get.desec.io. A Good: Only one SOA.Primary Name Server found.: get.desec.io. Error: SOA.Primary Name Server not included in the delegation set.: get.desec.io. 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, 2 Top Level Domains: io, org A Good: Name Servers with different domain names found.: 2 different Domains found A Good: Name servers with different Country locations found: 3 Name Servers, 2 Countries: DE, US A Info: Ipv4-Subnet-list: 3 Name Servers, 3 different subnets (first Byte): 157., 45., 88., 3 different subnets (first two Bytes): 157.53., 45.54., 88.99., 3 different subnets (first three Bytes): 157.53.224., 45.54.76., 88.99.64. A Excellent: Every Name Server IPv4-address starts with an unique Byte. A Info: IPv6-Subnet-list: 3 Name Servers with IPv6, 2 different subnets (first block): 2607:, 2a01:, 2 different subnets (first two blocks): 2607:f740:, 2a01:04f8:, 3 different subnets (first three blocks): 2607:f740:e00a:, 2607:f740:e633:, 2a01:04f8:010a:, 3 different subnets (first four blocks): 2607:f740:e00a:deec:, 2607:f740:e633:deec:, 2a01:04f8:010a:1044: A Good: Name Server IPv6 addresses from different subnets found. X Nameserver Timeout checking EDNS512: gra.wolfhugel.eu / 2001:41d0:d:266d:1::5 Nameserver doesn't pass all EDNS-Checks: get.desec.io: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result. Nameserver doesn't pass all EDNS-Checks: get.desec.io / 88.99.64.5: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout. Nameserver doesn't pass all EDNS-Checks: get.desec.io / 2a01:4f8:10a:1044:deec:642:ac10:80: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout. Nameserver doesn't pass all EDNS-Checks: ns.eu.org: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result. Nameserver doesn't pass all EDNS-Checks: ns1.desec.io / 45.54.76.1: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (3803d7ce6f1f). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns1.desec.io / 2607:f740:e633:deec::2: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (3803d7ce6f1f). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns2.desec.org / 157.53.224.1: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (0eee616d37e9). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns2.desec.org / 2607:f740:e00a:deec::2: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (0eee616d37e9). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok. A Good: All SOA have the same Serial Number A Good: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates 4. Content- and Performance-critical Checks http://vaan.eu.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:2f00:b20a:2000::2 Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. 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.vaan.eu.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:2f00:b20a:2000::2 Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. 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://vaan.eu.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:2f00:b20a:2000::2, Status -2 http://vaan.eu.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 188.25.199.28, Status 404 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.vaan.eu.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:2f00:b20a:2000::2, Status -2 http://www.vaan.eu.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 188.25.199.28, Status 404 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 supports GZip. https://vaan.eu.org/ 188.25.199.28 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://188.25.199.28/ 188.25.199.28 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://vaan.eu.org/ 188.25.199.28 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://188.25.199.28/ 188.25.199.28 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 Good: Some script Elements (type text/javascript) with a src-Attribute have a defer / async - Attribute. So loading and executing these JavaScripts doesn't block parsing and rendering the Html-Output. https://vaan.eu.org/ 188.25.199.28 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.: 3 script elements without defer/async. A Good: All CSS / JavaScript files are sent with GZip. That reduces the content of the files. 9 external CSS / JavaScript files found Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 8 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 1 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 9 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 http://vaan.eu.org/ 188.25.199.28 Warning: HSTS header sent via http has no effect http://www.vaan.eu.org/ 188.25.199.28 Warning: HSTS header sent via http has no effect A Duration: 1008523 milliseconds, 1008.523 seconds