1. General Results, most used to calculate the result A name "mzansixxx.com" is domain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 89449 (complete: 231048) A Good: All ip addresses are public addresses Warning: Only one ip address found: mzansixxx.com has only one ip address. Warning: Only one ip address found: www.mzansixxx.com 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: mzansixxx.com has no ipv6 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: www.mzansixxx.com has no ipv6 address. A Good: No asked Authoritative Name Server had a timeout A https://mzansixxx.com/ 54.67.42.145 https://mzansiporn.mobi 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. HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List. A Good: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset) B https://mzansixxx.com/ 54.67.42.145 Missing HSTS-Header B https://mzansiporn.mobi Missing HSTS-Header B https://www.mzansixxx.com/ 54.67.42.145 Missing HSTS-Header B https://mzansiporn.mobi AVS=l66sud011v31ctnnucgcigadpi; path=/ Cookie sent via https, but not marked as secure B https://mzansiporn.mobi AVS=l66sud011v31ctnnucgcigadpi; 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. E http://mzansixxx.com/ 54.67.42.145 https://mzansiporn.mobi 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.mzansixxx.com/ 54.67.42.145 https://mzansiporn.mobi 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. 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 mzansixxx.com, 1 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.mzansixxx.com, 1 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.mzansixxx.com 2. Header-Checks A mzansiporn.mobi report-to Ok: Header without syntax errors found: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=MxiXOtgARq2thLivaTju9YtWGpxK0hxlqDlYp6e4kdea0EECg8XxZhxZYeze52m1yagsWktcbqdXs85yUB8D9VeCMKCJ0%2BN8%2Bx94tHVMkDs0GLB%2Bhhh9FtTFgh0mODKK%2BUwJs1AxOMl%2BOJTSZIY%3D"}],"group":"cf-nel","max_age":604800} A Ok: Header without syntax errors found: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=MxiXOtgARq2thLivaTju9YtWGpxK0hxlqDlYp6e4kdea0EECg8XxZhxZYeze52m1yagsWktcbqdXs85yUB8D9VeCMKCJ0%2BN8%2Bx94tHVMkDs0GLB%2Bhhh9FtTFgh0mODKK%2BUwJs1AxOMl%2BOJTSZIY%3D"}],"group":"cf-nel","max_age":604800} F mzansiporn.mobi Content-Security-Policy Critical: Missing Header: F mzansiporn.mobi X-Content-Type-Options Critical: Missing Header: F mzansiporn.mobi Referrer-Policy Critical: Missing Header: F mzansiporn.mobi Permissions-Policy Critical: Missing Header: 3. DNS- and NameServer - Checks A Info:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers. A Info:: 2 Queries complete, 2 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.ns1.dyna-ns.net (162.159.26.92, 162.159.27.158), ns2.dyna-ns.net (162.159.24.5, 162.159.25.5) A Good (1 - 3.0):: An average of 1.0 queries per domain name server required to find all ip addresses of all name servers. A Info:: 2 different Name Servers found: ns1.dyna-ns.net, ns2.dyna-ns.net, 2 Name Servers included in Delegation: ns1.dyna-ns.net, ns2.dyna-ns.net, 2 Name Servers included in 1 Zone definitions: ns1.dyna-ns.net, ns2.dyna-ns.net, 1 Name Servers listed in SOA.Primary: ns1.dyna-ns.net. A Good: Only one SOA.Primary Name Server found.: ns1.dyna-ns.net. A Good: SOA.Primary Name Server included in the delegation set.: ns1.dyna-ns.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: ns1.dyna-ns.net, ns2.dyna-ns.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: 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: 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: dyna-ns.net A Good: Name servers with different Country locations found: 2 Name Servers, 2 Countries: CA, US A Info: Ipv4-Subnet-list: 4 Name Servers, 1 different subnets (first Byte): 162., 1 different subnets (first two Bytes): 162.159., 4 different subnets (first three Bytes): 162.159.24., 162.159.25., 162.159.26., 162.159.27. 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): 2400:, 1 different subnets (first two blocks): 2400:cb00:, 1 different subnets (first three blocks): 2400:cb00:2049:, 1 different subnets (first four blocks): 2400:cb00:2049:0001: Fatal: All Name Server IPv6 addresses from the same subnet. 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 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 Fatal: All checks of /.well-known/acme-challenge/random-filename have a redirect, destination doesn't have the random filename. 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. https://mzansiporn.mobi 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 A Duration: 286426 milliseconds, 286.426 seconds