| 1. General Results, most used to calculate the result |
| A | name "postleet.com" is domain, 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: one preferred version: non-www is preferred
|
| A | Good: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):2 complete Content-Type - header (5 urls)
|
| http://postleet.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 91.134.128.45
|
| Url with incomplete Content-Type - header - missing charset
|
| http://postleet.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:41d0:202:100:91:134:128:45
|
| Url with incomplete Content-Type - header - missing charset
|
| http://www.postleet.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 91.134.128.45
|
| Url with incomplete Content-Type - header - missing charset
|
| B | https://postleet.com/ 91.134.128.45
|
| Missing HSTS-Header
|
| B | https://postleet.com/ 91.134.128.45
| PHPSESSID=778qro0i1b2lq5bdpch6mghrfl; Path=/; Domain=postleet.com; HttpOnly
| Cookie sent via https, but not marked as secure
|
| B | https://postleet.com/ 91.134.128.45
| ad-con=a%3A2%3A%7Bs%3A4%3A%26quot%3Bdate%26quot%3B%3Bs%3A10%3A%26quot%3B2019-05-08%26quot%3B%3Bs%3A3%3A%26quot%3Bads%26quot%3B%3Ba%3A0%3A%7B%7D%7D; Path=/; Domain=postleet.com; Expires=2029-05-05 17:00:51
| Cookie sent via https, but not marked as secure
|
| B | https://postleet.com/ 91.134.128.45
| _us=1557414051; Path=/; Domain=postleet.com; Expires=2029-05-05 17:00:51
| Cookie sent via https, but not marked as secure
|
| B | https://postleet.com/ 91.134.128.45
| mode=day; Path=/; Domain=postleet.com; Expires=2029-05-05 17:00:51
| Cookie sent via https, but not marked as secure
|
| B | https://postleet.com/ 91.134.128.45
| access=1; Path=/; Domain=postleet.com; Expires=2019-05-09 17:00:51
| Cookie sent via https, but not marked as secure
|
| B | https://postleet.com/ 91.134.128.45
| src=1; Path=/; Domain=postleet.com; Expires=2020-05-07 22:49:37
| Cookie sent via https, but not marked as secure
|
| 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.
|
| I | https://postleet.com/ 91.134.128.45
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
|
| K | http://postleet.com/ 91.134.128.45, Status 200
| http://postleet.com/ 2001:41d0:202:100:91:134:128:45, Status -14
| Configuration problem - different ip addresses with different status
|
| K | https://postleet.com/ 91.134.128.45, Status 200
| https://postleet.com/ 2001:41d0:202:100:91:134:128:45, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.postleet.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:41d0:202:100:91:134:128:45, Status -14
| http://www.postleet.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 91.134.128.45, Status 200
| Configuration problem - different ip addresses with different status
|
| 2. Header-Checks |
| 3. DNS- and NameServer - Checks |
| A | Good: Nameserver supports TCP connections: 4 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 4 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
|
| 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 | http://postleet.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 91.134.128.45
|
| Good: Acme-Check - Answer looks like a correct keyAuthorization - String: Filename + "." + base64url(Thumbprint(accountKey)). So creating a Letsencrypt certificate using that integrated solution should work. Don't use another client (like Certbot). Don't mix integrated solutions with own ACME-clients, that may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| A | http://postleet.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:41d0:202:100:91:134:128:45
|
| Good: Acme-Check - Answer looks like a correct keyAuthorization - String: Filename + "." + base64url(Thumbprint(accountKey)). So creating a Letsencrypt certificate using that integrated solution should work. Don't use another client (like Certbot). Don't mix integrated solutions with own ACME-clients, that may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| A | http://www.postleet.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 91.134.128.45
|
| Good: Acme-Check - Answer looks like a correct keyAuthorization - String: Filename + "." + base64url(Thumbprint(accountKey)). So creating a Letsencrypt certificate using that integrated solution should work. Don't use another client (like Certbot). Don't mix integrated solutions with own ACME-clients, that may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://www.postleet.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:41d0:202:100:91:134:128:45
|
| Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://www.postleet.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:41d0:202:100:91:134:128:45, Status -14
| http://www.postleet.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 91.134.128.45, Status 200
| 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 | Duration: 81450 milliseconds, 81.450 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)