| 1. General Results, most used to calculate the result |
A | name "dev.special-lite.com" is subdomain, public suffix is "com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services"
|
A | Good: All ip addresses are public addresses
|
A | Good: No asked Authoritative Name Server had a timeout
|
A | Good: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):2 complete Content-Type - header (8 urls)
|
| http://dev.special-lite.com/ 3.16.107.165
|
| Url with incomplete Content-Type - header - missing charset
|
| http://dev.special-lite.com/ 2607:f1c0:1000:10a3:a1fb:3220:d458:c822
|
| Url with incomplete Content-Type - header - missing charset
|
| http://www.dev.special-lite.com/ 3.16.107.165
|
| Url with incomplete Content-Type - header - missing charset
|
| http://www.dev.special-lite.com/ 2607:f1c0:1000:10a3:a1fb:3220:d458:c822
|
| Url with incomplete Content-Type - header - missing charset
|
| https://dev.special-lite.com/ 3.16.107.165
|
| Url with incomplete Content-Type - header - missing charset
|
| https://www.dev.special-lite.com/ 3.16.107.165
|
| Url with incomplete Content-Type - header - missing charset
|
B | https://dev.special-lite.com/ 3.16.107.165
|
| Missing HSTS-Header
|
B | https://www.dev.special-lite.com/ 3.16.107.165
|
| 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.
|
K | https://dev.special-lite.com/ 3.16.107.165, Status 200
| https://dev.special-lite.com/ 2607:f1c0:1000:10a3:a1fb:3220:d458:c822, Status -10
| Configuration problem - different ip addresses with different status
|
K | https://www.dev.special-lite.com/ 3.16.107.165, Status 200
| https://www.dev.special-lite.com/ 2607:f1c0:1000:10a3:a1fb:3220:d458:c822, Status -10
| Configuration problem - different ip addresses with different status
|
K | http://dev.special-lite.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 3.16.107.165, Status 404
| http://dev.special-lite.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2607:f1c0:1000:10a3:a1fb:3220:d458:c822, Status 204
| Configuration problem - different ip addresses with different status
|
K | http://www.dev.special-lite.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 3.16.107.165, Status 404
| http://www.dev.special-lite.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2607:f1c0:1000:10a3:a1fb:3220:d458:c822, Status 204
| Configuration problem - different ip addresses with different status
|
N | https://dev.special-lite.com/ 3.16.107.165
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
N | https://www.dev.special-lite.com/ 3.16.107.165
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
P | https://dev.special-lite.com/ 2607:f1c0:1000:10a3:a1fb:3220:d458:c822
|
| Error creating a TLS-Connection: IANA TLS Alert No. 80, internal_error. An internal error unrelated to the peer or the correctness of the protocol (such as a memory allocation failure) makes it impossible to continue. SSL_ERROR_INTERNAL_ERROR_ALERT (Mozilla) / ERR_SSL_PROTOCOL_ERROR (Chrome)
|
P | https://www.dev.special-lite.com/ 2607:f1c0:1000:10a3:a1fb:3220:d458:c822
|
| Error creating a TLS-Connection: IANA TLS Alert No. 80, internal_error. An internal error unrelated to the peer or the correctness of the protocol (such as a memory allocation failure) makes it impossible to continue. SSL_ERROR_INTERNAL_ERROR_ALERT (Mozilla) / ERR_SSL_PROTOCOL_ERROR (Chrome)
|
| 2. Header-Checks |
| 3. DNS- and NameServer - Checks |
A | Good: Nameserver supports TCP connections: 1 good Nameserver
|
A | Good: Nameserver supports Echo Capitalization: 1 good Nameserver
|
A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver
|
A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 1 good Nameserver
|
| 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 |
| http://dev.special-lite.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2607:f1c0:1000:10a3:a1fb:3220:d458:c822
|
| Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 201, 202, 203 or 204. Creating a Letsencrypt certificate via http-01 challenge can't work. A http status 301-309 (Redirect to another domain or port 80 / 443) or a http status 404 - Not Found is expected, if the test file doesn't exist. Looks like the webserver isn't configured, perhaps it's an answer of your hoster. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://www.dev.special-lite.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2607:f1c0:1000:10a3:a1fb:3220:d458:c822
|
| Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 201, 202, 203 or 204. Creating a Letsencrypt certificate via http-01 challenge can't work. A http status 301-309 (Redirect to another domain or port 80 / 443) or a http status 404 - Not Found is expected, if the test file doesn't exist. Looks like the webserver isn't configured, perhaps it's an answer of your hoster. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://dev.special-lite.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2607:f1c0:1000:10a3:a1fb:3220:d458:c822, Status 204
| http://dev.special-lite.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 3.16.107.165, Status 404
| Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://www.dev.special-lite.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2607:f1c0:1000:10a3:a1fb:3220:d458:c822, Status 204
| http://www.dev.special-lite.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 3.16.107.165, Status 404
| Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
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 | Info: Different Server-Headers found
|
A | Duration: 40804 milliseconds, 40.804 seconds
|