| 1. General Results, most used to calculate the result |
| A | name "mars.raqua.net" is subdomain, public suffix is ".net", top-level-domain is ".net", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .net-domains preloaded: 5892 (complete: 131120)
|
| A | Good: All ip addresses are public addresses
|
| Warning: Only one ip address found: mars.raqua.net 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: mars.raqua.net has no ipv6 address.
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | DNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
|
| 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 | http://mars.raqua.net/ 92.52.40.226
| https://mars.raqua.net/
| Correct redirect http - https with the same domain name
|
| B | https://mars.raqua.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Missing HSTS-Header
|
| P | https://92.52.40.226/ 92.52.40.226
|
| Error creating a TLS-Connection: No more details available.
|
| X | Fatal error: Nameserver doesn't support TCP connection: ns2.websupport.sk / 2a00:4b40:1337:2::53: Timeout
|
| 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 mars.raqua.net, 1 ip addresses.
|
| 2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05) |
| 3. DNS- and NameServer - Checks |
| A | Info:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 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.websupport.sk (195.210.28.30), ns2.websupport.sk (195.210.29.64, 2a00:4b40:1337:2::53), ns3.websupport.sk (62.176.179.10)
|
| A | Good (1 - 3.0):: An average of 0.7 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 3 different Name Servers found: ns1.websupport.sk, ns2.websupport.sk, ns3.websupport.sk, 3 Name Servers included in Delegation: ns1.websupport.sk, ns2.websupport.sk, ns3.websupport.sk, 3 Name Servers included in 1 Zone definitions: ns1.websupport.sk, ns2.websupport.sk, ns3.websupport.sk, 1 Name Servers listed in SOA.Primary: ns1.websupport.sk.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.websupport.sk.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.websupport.sk.
|
| 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 | Info: Ipv4-Subnet-list: 3 Name Servers, 2 different subnets (first Byte): 195., 62., 2 different subnets (first two Bytes): 195.210., 62.176., 3 different subnets (first three Bytes): 195.210.28., 195.210.29., 62.176.179.
|
| A | Good: Name Server IPv4-addresses from different subnet found:
|
| A | Info: IPv6-Subnet-list: 1 Name Servers with IPv6, 1 different subnets (first block): 2a00:, 1 different subnets (first two blocks): 2a00:4b40:, 1 different subnets (first three blocks): 2a00:4b40:1337:, 1 different subnets (first four blocks): 2a00:4b40:1337:0002:
|
| Fatal: All Name Server IPv6 addresses from the same subnet.
|
| X | Nameserver Timeout checking Echo Capitalization: ns2.websupport.sk / 2a00:4b40:1337:2::53
|
| X | Nameserver Timeout checking EDNS512: ns2.websupport.sk / 2a00:4b40:1337:2::53
|
| Nameserver doesn't pass all EDNS-Checks: ns1.websupport.sk: 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: ns2.websupport.sk / 2a00:4b40:1337:2::53: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
|
| 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 |
| 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: 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 %.
|
| A | Good: Every https connection via port 443 supports the http/2 protocol via ALPN.
|
| A | Info: No img element found, no alt attribute checked
|
| A | Good: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
|
| https://mars.raqua.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| 4.497 seconds
| Warning: 404 needs more then one second
|
| A | Duration: 122820 milliseconds, 122.820 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)