1. General Results, most used to calculate the result A name "hdc.bergsmo.se" is subdomain, public suffix is ".se", top-level-domain is ".se", top-level-domain-type is "country-code", Country is Sweden, tld-manager is "The Internet Infrastructure Foundation", num .se-domains preloaded: 755 (complete: 175327) A Good: All ip addresses are public addresses A Good: Minimal 2 ip addresses per domain name found: www.hdc.bergsmo.se has 2 different ip addresses (authoritative). A Good: Ipv4 and Ipv6 addresses per domain name found: www.hdc.bergsmo.se has 1 ipv4, 1 ipv6 addresses Warning: Only one ip address found: hdc.bergsmo.se has only one ip address. Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: hdc.bergsmo.se has no ipv6 address. A Good: No asked Authoritative Name Server had a timeout A https://hdc.bergsmo.se:443/ https://hdc.bergsmo.se/login Correct redirect https to https A https://hdc.bergsmo.se/ 213.164.221.175 https://hdc.bergsmo.se/login Correct redirect https to https A Good: destination is https A Good - only one version with Http-Status 200 A Good: one preferred version: non-www is preferred A Good: No cookie sent via http. A Good: every cookie sent via https is marked as secure A Good: Every cookie has a SameSite Attribute with a correct value Strict/Lax/None HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List. A Good: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):7 complete Content-Type - header (8 urls) http://hdc.bergsmo.se/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 213.164.221.175 Url with incomplete Content-Type - header - missing charset B Warning: HSTS max-age is too short - minimum 31536000 = 365 days required, 15768000 seconds = 182 days found B https://www.hdc.bergsmo.se/ 77.111.240.33 Missing HSTS-Header B https://www.hdc.bergsmo.se/ 2a02:2350:5:108:80f8:dbb0:c810:5baf Missing HSTS-Header B https://hdc.bergsmo.se:443/ max-age=15768000; includeSubDomains; Critical: HSTS-Header has Parse-Errors. Empty entry, remove the semicolon at the end., Value of max-age is too small. Should be minimal one year = 31536000., Unknown directive found. Only max-age (with value), includeSubdomains or preload allowed. B https://hdc.bergsmo.se/ 213.164.221.175 max-age=15768000; includeSubDomains; Critical: HSTS-Header has Parse-Errors. Empty entry, remove the semicolon at the end., Value of max-age is too small. Should be minimal one year = 31536000., Unknown directive found. Only max-age (with value), includeSubdomains or preload allowed. B https://hdc.bergsmo.se/login max-age=15768000; includeSubDomains; Critical: HSTS-Header has Parse-Errors. Empty entry, remove the semicolon at the end., Value of max-age is too small. Should be minimal one year = 31536000., Unknown directive found. Only max-age (with value), includeSubdomains or preload allowed. B https://213.164.221.175/ 213.164.221.175 max-age=15768000; includeSubDomains; Critical: HSTS-Header has Parse-Errors. Empty entry, remove the semicolon at the end., Value of max-age is too small. Should be minimal one year = 31536000., Unknown directive found. Only max-age (with value), includeSubdomains or preload allowed. I https://hdc.bergsmo.se/login Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part. M https://213.164.221.175/ 213.164.221.175 Misconfiguration - main pages should never send http status 400 - 499 N https://hdc.bergsmo.se:443/ https://hdc.bergsmo.se/login Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors N https://hdc.bergsmo.se/ 213.164.221.175 https://hdc.bergsmo.se/login Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors N https://hdc.bergsmo.se/login Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors N https://www.hdc.bergsmo.se/ 77.111.240.33 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://www.hdc.bergsmo.se/ 2a02:2350:5:108:80f8:dbb0:c810:5baf Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://213.164.221.175/ 213.164.221.175 Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors P https://77.111.240.33/ 77.111.240.33 Error creating a TLS-Connection: No more details available. P https://[2a02:2350:0005:0108:80f8:dbb0:c810:5baf]/ 2a02:2350:5:108:80f8:dbb0:c810:5baf 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 www.hdc.bergsmo.se, 2 ip addresses. Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain hdc.bergsmo.se, 1 ip addresses, 1 different http results. 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.hdc.bergsmo.se, 2 ip addresses. 2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete) 3. DNS- and NameServer - Checks A Info:: 9 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers. A Info:: 9 Queries complete, 9 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:: 2 different Name Servers found: ns01.one.com, ns02.one.com, 2 Name Servers included in Delegation: ns01.one.com, ns02.one.com, 2 Name Servers included in 1 Zone definitions: ns01.one.com, ns02.one.com, 1 Name Servers listed in SOA.Primary: ns01.one.com. A Good: Only one SOA.Primary Name Server found.: ns01.one.com. A Good: SOA.Primary Name Server included in the delegation set.: ns01.one.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: ns01.one.com, ns02.one.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: 2 different Name Servers found Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 2 Name Servers, 1 Top Level Domain: 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: one.com Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: DK A A Info: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:067c:, 1 different subnets (first three blocks): 2001:067c:28cc:, 2 different subnets (first four blocks): 2001:067c:28cc:0000:, 2001:067c:28cc:0001: A Good: Name Server IPv6 addresses from different subnets found. A Good: Nameserver supports TCP connections: 1 good Nameserver A Good: Nameserver supports Echo Capitalization: 1 good Nameserver A Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver A Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 1 good Nameserver Nameserver doesn't pass all EDNS-Checks: catcher-in-the-rye.nic.se: 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. A Good: All SOA have the same Serial Number Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries. 4. Content- and Performance-critical Checks http://www.hdc.bergsmo.se/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.111.240.33 Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://www.hdc.bergsmo.se/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:2350:5:108:80f8:dbb0:c810:5baf Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. A Good: Every https result with status 200 supports GZip. A Good: No https + http status 200 with inline CSS / JavaScript found A Good: Every https result with status 200 has a minified Html-Content with a quota lower then 110 %. https://hdc.bergsmo.se/login Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2. A Good: All script Elements (type text/javascript) and src-Attribute have a defer / async - Attribute. So loading and executing these JavaScripts doesn't block parsing and rendering the Html-Output. Warning: CSS / JavaScript found without GZip support. Send these ressources with GZip. 2 external CSS / JavaScript files without GZip found - 14 with GZip, 16 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, 1 with Cache-Control, but no max-age, 1 with Cache-Control max-age too short (minimum 7 days), 14 with Cache-Control long enough, 16 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://hdc.bergsmo.se:443/ Strict-Transport-Security: max-age=15768000; includeSubDomains; Parse Error - Header can't be parsed https://hdc.bergsmo.se/ 213.164.221.175 Strict-Transport-Security: max-age=15768000; includeSubDomains; Parse Error - Header can't be parsed https://hdc.bergsmo.se/login Strict-Transport-Security: max-age=15768000; includeSubDomains; Parse Error - Header can't be parsed A Info: Different Server-Headers found A Duration: 117984 milliseconds, 117.984 seconds