| 1. General Results, most used to calculate the result |
| A | name "greentea.ml" is domain, public suffix is "ml", top-level-domain-type is "country-code", Country is Mali, tld-manager is "Agence des Technologies de l’Information et de la Communication"
|
| A | Good: All ip addresses are public 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, 63072000 seconds = 730 days
|
| A | Good: HSTS has includeSubdomains - directive
|
| A | Good: HSTS has preload directive
|
| 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):0 complete Content-Type - header (2 urls)
|
| https://greentea.ml/ 18.182.86.116
|
| Url with incomplete Content-Type - header - missing charset
|
| https://greentea.ml/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Url with incomplete Content-Type - header - missing charset
|
| A | http://greentea.ml/ 18.182.86.116
| https://greentea.ml/
| Correct redirect http - https with the same domain name
|
| N | greentea.ml:465
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | 18.182.86.116:465
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| X | Fatal error: Nameserver doesn't support TCP connection: a.ns.ml: Fatal error (0)
|
| X | Fatal error: Nameserver doesn't support TCP connection: b.ns.ml: Fatal error (0)
|
| X | Fatal error: Nameserver doesn't support TCP connection: c.ns.ml: Fatal error (0)
|
| X | Fatal error: Nameserver doesn't support TCP connection: d.ns.ml: Fatal error (0)
|
| 2. Header-Checks |
| 3. DNS- and NameServer - Checks |
| 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: ns0.dnsport.jp,ns1.dnsport.jp
|
| A | Good: Nameserver supports TCP connections: 2 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 2 good Nameserver
|
| X | Nameserver Timeout checking Echo Capitalization: b.ns.ml
|
| X | Nameserver Timeout checking Echo Capitalization: c.ns.ml
|
| X | Nameserver Timeout checking Echo Capitalization: d.ns.ml
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
|
| X | Nameserver Timeout checking EDNS512: c.ns.ml
|
| 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: a.ns.ml: OP100: ok. FLAGS: ok. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: ok (ams). COOKIE: ok. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: b.ns.ml: OP100: ok. FLAGS: ok. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: ok (ams). COOKIE: ok. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: c.ns.ml: OP100: fatal timeout. FLAGS: ok. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: ok (ams). COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: d.ns.ml: OP100: ok. FLAGS: ok. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: ok (ams). COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: ns0.dnsport.jp: 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 |
| 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: Every https result with status 200 and greater 1024 Bytes is compressed (gzip, deflate, br checked).
|
| https://greentea.ml/ 18.182.86.116
|
| 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: 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://greentea.ml/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| 5.390 seconds
| Warning: 404 needs more then one second
|
| A | Duration: 168337 milliseconds, 168.337 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)