| 1. General Results, most used to calculate the result |
| A | name "cloud.gut-haidehof.de" is subdomain, public suffix is "de", top-level-domain-type is "country-code", Country is Germany, tld-manager is "DENIC eG"
|
| 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: 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
|
| C | Error - no version with Http-Status 200
|
| E | http://cloud.gut-haidehof.de/ 91.35.199.24
| https://cloud.reshaped.ch/
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| H | Fatal error: No https - result with http-status 200, no encryption
|
| R | http://cloud.gut-haidehof.de/ 91.35.199.24
| https://cloud.reshaped.ch/
| Redirect to not existing domain
|
| R | https://cloud.gut-haidehof.de/ 91.35.199.24
| https://cloud.reshaped.ch/
| Redirect to not existing domain
|
| R | http://cloud.gut-haidehof.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 91.35.199.24
| https://cloud.reshaped.ch/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| Redirect to not existing domain
|
| 2. Header-Checks |
| 3. DNS- and NameServer - Checks |
| A | Good: Nameserver supports TCP connections: 2 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 2 good Nameserver
|
| X | Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: docks15.rzone.de
|
| X | Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: shades06.rzone.de
|
| Nameserver doesn't pass all EDNS-Checks: docks15.rzone.de: 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: shades06.rzone.de: 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: shades06.rzone.de: 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: shades06.rzone.de / 85.214.0.236: 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: shades06.rzone.de / 2a01:238:20b:43:6653::506: 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 |
| https://cloud.reshaped.ch/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Fatal: Check of /.well-known/acme-challenge/random-filename redirects to not-existing domain. Creating a Letsencrypt certificate via http-01 challenge can't work. 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
|
| http://cloud.gut-haidehof.de/ 91.35.199.24
|
| Warning: HSTS header sent via http has no effect
|
| A | Duration: 23580 milliseconds, 23.580 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)