| 1. General Results, most used to calculate the result |
| A | name "edgeko.duckdns.org" is domain, public suffix is ".duckdns.org", top-level-domain is ".org", top-level-domain-type is "generic", tld-manager is "Public Interest Registry (PIR)", num .org-domains preloaded: 8524 (complete: 245733)
|
| A | Good: All ip addresses are public addresses
|
| Warning: Only one ip address found: www.edgeko.duckdns.org 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: www.edgeko.duckdns.org has no ipv6 address.
|
| 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: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):5 complete Content-Type - header (7 urls)
|
| http://edgeko.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 24.1.97.186
|
| Url with incomplete Content-Type - header - missing charset
|
| http://www.edgeko.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 24.1.97.186
|
| Url with incomplete Content-Type - header - missing charset
|
| B | https://edgeko.duckdns.org/ 24.1.97.186
|
| Missing HSTS-Header
|
| B | https://www.edgeko.duckdns.org/ 24.1.97.186
|
| Missing HSTS-Header
|
| C | Error - no preferred version www or non-www. Select one version as preferred version, then add a redirect https + not-preferred version to https + preferred version. Perhaps in your port 443 vHost something like "RewriteEngine on" + "RewriteCond %{SERVER_NAME} = example.com" + "ReWriteRule ^ https://www.example.com%{REQUEST_URI} [END,QSA,R=permanent]" (three rows, without the "). That should create a redirect https + example.com ⇒ https + www.example.com. Or switch both values to use the non-www version as your preferred version.
|
| C | Error - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
|
| H | Fatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. 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.
|
| N | https://edgeko.duckdns.org/ 24.1.97.186
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://www.edgeko.duckdns.org/ 24.1.97.186
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://24.1.97.186/ 24.1.97.186
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| O | www.edgeko.duckdns.org / 24.1.97.186 / 443
|
| Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 6 Cipher Suites without Forward Secrecy found
|
| X | Fatal error: Nameserver doesn't support TCP connection: ns1.duckdns.org: Timeout
|
| X | Fatal error: Nameserver doesn't support TCP connection: ns2.duckdns.org: Timeout
|
| X | Fatal error: Nameserver doesn't support TCP connection: ns3.duckdns.org: Timeout
|
| X | Fatal error: Nameserver doesn't support TCP connection: ns3.duckdns.org / 35.183.157.249: Timeout
|
| X | Fatal error: Nameserver doesn't support TCP connection: ns4.duckdns.org: Timeout
|
| X | Fatal error: Nameserver doesn't support TCP connection: ns5.duckdns.org: Timeout
|
| X | Fatal error: Nameserver doesn't support TCP connection: ns6.duckdns.org: Timeout
|
| X | Fatal error: Nameserver doesn't support TCP connection: ns7.duckdns.org: Timeout
|
| X | Fatal error: Nameserver doesn't support TCP connection: ns8.duckdns.org: Timeout
|
| X | Fatal error: Nameserver doesn't support TCP connection: ns8.duckdns.org / 15.223.106.16: Timeout
|
| X | Fatal error: Nameserver doesn't support TCP connection: ns9.duckdns.org: Timeout
|
| 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 www.edgeko.duckdns.org, 1 ip addresses, 1 different http results.
|
| 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.edgeko.duckdns.org
|
| 2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05) |
| F | edgeko.duckdns.org 24.1.97.186
| Content-Security-Policy
| Critical: Missing Header:
|
| F | edgeko.duckdns.org 24.1.97.186
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | edgeko.duckdns.org 24.1.97.186
| Referrer-Policy
| Critical: Missing Header:
|
| F | edgeko.duckdns.org 24.1.97.186
| Permissions-Policy
| Critical: Missing Header:
|
| B | edgeko.duckdns.org 24.1.97.186
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | edgeko.duckdns.org 24.1.97.186
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | edgeko.duckdns.org 24.1.97.186
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| F | www.edgeko.duckdns.org 24.1.97.186
| Content-Security-Policy
| Critical: Missing Header:
|
| F | www.edgeko.duckdns.org 24.1.97.186
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | www.edgeko.duckdns.org 24.1.97.186
| Referrer-Policy
| Critical: Missing Header:
|
| F | www.edgeko.duckdns.org 24.1.97.186
| Permissions-Policy
| Critical: Missing Header:
|
| B | www.edgeko.duckdns.org 24.1.97.186
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | www.edgeko.duckdns.org 24.1.97.186
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | www.edgeko.duckdns.org 24.1.97.186
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| 3. DNS- and NameServer - Checks |
| A |
|
| A |
|
| A | Info:: 9 different Name Servers found: ns1.duckdns.org, ns2.duckdns.org, ns3.duckdns.org, ns4.duckdns.org, ns5.duckdns.org, ns6.duckdns.org, ns7.duckdns.org, ns8.duckdns.org, ns9.duckdns.org, 9 Name Servers included in Delegation: ns1.duckdns.org, ns2.duckdns.org, ns3.duckdns.org, ns4.duckdns.org, ns5.duckdns.org, ns6.duckdns.org, ns7.duckdns.org, ns8.duckdns.org, ns9.duckdns.org, 0 Name Servers included in 1 Zone definitions: , 0 Name Servers listed in SOA.Primary: .
|
| A | Good: All Name Server Domain Names have a Public Suffix.
|
| Error: Name Server Domain Names with Public Suffix and without ip address found.: 7 Name Servers without ipv4 and ipv6: 7
|
|
|
| A | Info: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 15., 35., 2 different subnets (first two Bytes): 15.223., 35.183., 2 different subnets (first three Bytes): 15.223.106., 35.183.157.
|
| A | Excellent: Every Name Server IPv4-address starts with an unique Byte.
|
| X | Nameserver Timeout checking Echo Capitalization: ns1.duckdns.org
|
| X | Nameserver Timeout checking Echo Capitalization: ns2.duckdns.org
|
| X | Nameserver Timeout checking Echo Capitalization: ns3.duckdns.org
|
| X | Nameserver Timeout checking Echo Capitalization: ns3.duckdns.org / 35.183.157.249
|
| X | Nameserver Timeout checking Echo Capitalization: ns4.duckdns.org
|
| X | Nameserver Timeout checking Echo Capitalization: ns5.duckdns.org
|
| X | Nameserver Timeout checking Echo Capitalization: ns6.duckdns.org
|
| X | Nameserver Timeout checking Echo Capitalization: ns7.duckdns.org
|
| X | Nameserver Timeout checking Echo Capitalization: ns8.duckdns.org
|
| X | Nameserver Timeout checking Echo Capitalization: ns8.duckdns.org / 15.223.106.16
|
| X | Nameserver Timeout checking Echo Capitalization: ns9.duckdns.org
|
| X | Nameserver Timeout checking EDNS512: ns1.duckdns.org
|
| X | Nameserver Timeout checking EDNS512: ns2.duckdns.org
|
| X | Nameserver Timeout checking EDNS512: ns3.duckdns.org
|
| X | Nameserver Timeout checking EDNS512: ns3.duckdns.org / 35.183.157.249
|
| X | Nameserver Timeout checking EDNS512: ns4.duckdns.org
|
| X | Nameserver Timeout checking EDNS512: ns5.duckdns.org
|
| X | Nameserver Timeout checking EDNS512: ns6.duckdns.org
|
| X | Nameserver Timeout checking EDNS512: ns7.duckdns.org
|
| X | Nameserver Timeout checking EDNS512: ns8.duckdns.org
|
| X | Nameserver Timeout checking EDNS512: ns8.duckdns.org / 15.223.106.16
|
| X | Nameserver Timeout checking EDNS512: ns9.duckdns.org
|
| Nameserver doesn't pass all EDNS-Checks: ns1.duckdns.org: 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: ns1.duckdns.org: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: ns2.duckdns.org: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: ok. COOKIE: fatal timeout. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns2.duckdns.org: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: ns3.duckdns.org: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: ns3.duckdns.org / 35.183.157.249: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: ns4.duckdns.org: OP100: ok. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: ns4.duckdns.org: OP100: fatal timeout. FLAGS: fatal timeout. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns5.duckdns.org: OP100: fatal timeout. FLAGS: fatal timeout. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns5.duckdns.org: 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: ns6.duckdns.org: 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: ns6.duckdns.org: OP100: ok. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: ns7.duckdns.org: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: ok. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: ns7.duckdns.org: 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: ns8.duckdns.org: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: ns8.duckdns.org / 15.223.106.16: OP100: ok. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: ns9.duckdns.org: OP100: fatal timeout. FLAGS: ok. V1: fatal timeout. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns9.duckdns.org: OP100: fatal timeout. FLAGS: ok. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: ok. CLIENTSUBNET: fatal timeout.
|
| 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 | 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
|
| A | Duration: 1477644 milliseconds, 1477.644 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)