| 1. General Results, most used to calculate the result |
| A | name "mtrx.anchel.nl" is subdomain, public suffix is "nl", top-level-domain-type is "country-code", Country is Netherlands (the), tld-manager is "SIDN (Stichting Internet Domeinregistratie Nederland)"
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: mtrx.anchel.nl has 2 different ip addresses (authoritative).
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: mtrx.anchel.nl has 1 ipv4, 1 ipv6 addresses
|
| 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: every https has a Strict Transport Security Header
|
| A | Good: HSTS max-age is long enough, 31536000 seconds = 365 days
|
| A | Good: HSTS has includeSubdomains - directive
|
| 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):0 complete Content-Type - header (5 urls)
|
| https://mtrx.anchel.nl/ 213.154.229.59
|
| Url with incomplete Content-Type - header - missing charset
|
| https://mtrx.anchel.nl/ 2001:7b8:3:47:213:154:229:59
|
| Url with incomplete Content-Type - header - missing charset
|
| https://mtrx.anchel.nl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Url with incomplete Content-Type - header - missing charset
|
| https://213.154.229.59/ 213.154.229.59
|
| Url with incomplete Content-Type - header - missing charset
|
| https://[2001:07b8:0003:0047:0213:0154:0229:0059]/ 2001:7b8:3:47:213:154:229:59
|
| Url with incomplete Content-Type - header - missing charset
|
| A | http://mtrx.anchel.nl/ 213.154.229.59
| https://mtrx.anchel.nl/
| Correct redirect http - https with the same domain name
|
| A | http://mtrx.anchel.nl/ 2001:7b8:3:47:213:154:229:59
| https://mtrx.anchel.nl/
| Correct redirect http - https with the same domain name
|
| M | https://213.154.229.59/ 213.154.229.59
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://[2001:07b8:0003:0047:0213:0154:0229:0059]/ 2001:7b8:3:47:213:154:229:59
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| N | https://213.154.229.59/ 213.154.229.59
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://[2001:07b8:0003:0047:0213:0154:0229:0059]/ 2001:7b8:3:47:213:154:229:59
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| 2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05) |
| 3. DNS- and NameServer - Checks |
| 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: nl, org
|
| A | Good: Name Servers with different domain names found.: 2 different Domains found
|
| Warning: All Name Servers from the same Country / IP location.: 3 Name Servers, 1 Countries: NL
|
| A | Info: Ipv4-Subnet-list: 3 Name Servers, 3 different subnets (first Byte): 213., 84., 2 different subnets (first two Bytes): 213.136., 84.241., 2 different subnets (first three Bytes): 213.136.12., 84.241.129.
|
| A | Good: Name Server IPv4-addresses from different subnet found:
|
| A | Info: IPv6-Subnet-list: 3 Name Servers with IPv6, 1 different subnets (first block): 2001:, 2 different subnets (first two blocks): 2001:07b8:, 2001:1690:, 2 different subnets (first three blocks): 2001:07b8:0003:, 2001:1690:0022:, 3 different subnets (first four blocks): 2001:07b8:0003:002c:, 2001:07b8:0003:002d:, 2001:1690:0022:0001:
|
| A | Good: Name Server IPv6 addresses from different subnets found.
|
| A | Good: Nameserver supports TCP connections: 2 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 2 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
|
| Nameserver doesn't pass all EDNS-Checks: nsauth1.bit.nl: 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
|
| A | Good: CAA entries found, creating certificate is limited: letsencrypt.org 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: 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 | 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://mtrx.anchel.nl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| 3.204 seconds
| Warning: 404 needs more then one second
|
| A | Duration: 76433 milliseconds, 76.433 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)