| 1. General Results, most used to calculate the result |
| A | name "melochenator.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 | https://melochenator.com:80/ 52.3.37.37
| https://melochenator.com/login
| Correct redirect https to https
|
| A | https://melochenator.com/ 52.3.37.37
| https://melochenator.com/login
| Correct redirect https to https
|
| A | https://www.melochenator.com/ 52.3.37.37
| https://www.melochenator.com/login
| Correct redirect https to https
|
| A | https://www.melochenator.com:80/ 52.3.37.37
| https://www.melochenator.com/login
| Correct redirect https to https
|
| A | Good: destination is https
|
| 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):0 complete Content-Type - header (2 urls)
|
| https://melochenator.com/login
|
| Url with incomplete Content-Type - header - missing charset
|
| https://www.melochenator.com/login
|
| Url with incomplete Content-Type - header - missing charset
|
| B | https://melochenator.com/ 52.3.37.37
|
| Missing HSTS-Header
|
| B | https://melochenator.com:80/ 52.3.37.37
|
| Missing HSTS-Header
|
| B | https://melochenator.com/login
|
| Missing HSTS-Header
|
| B | https://www.melochenator.com:80/ 52.3.37.37
|
| Missing HSTS-Header
|
| B | https://www.melochenator.com/ 52.3.37.37
|
| Missing HSTS-Header
|
| B | https://www.melochenator.com/login
|
| Missing HSTS-Header
|
| B | https://melochenator.com/ 52.3.37.37
| PHPSESSID=jo0ub41r3e4l7i7amco2jogb63; Path=/; Domain=melochenator.com
| Cookie sent via https, but not marked as secure
|
| B | https://melochenator.com:80/ 52.3.37.37
| PHPSESSID=c5ejboo8fuuhjooq6lfj3luds1; Path=/; Domain=melochenator.com
| Cookie sent via https, but not marked as secure
|
| B | https://melochenator.com/login
| PHPSESSID=2tnbbtbt5mk8qg4ao1opjoc722; Path=/; Domain=melochenator.com
| Cookie sent via https, but not marked as secure
|
| B | https://www.melochenator.com/ 52.3.37.37
| PHPSESSID=qei8qgnu483vdge1hkf4e0eh62; Path=/; Domain=www.melochenator.com
| Cookie sent via https, but not marked as secure
|
| B | https://www.melochenator.com:80/ 52.3.37.37
| PHPSESSID=0g1m0lvs9lh5n3pvat1jlm3kd6; Path=/; Domain=www.melochenator.com
| Cookie sent via https, but not marked as secure
|
| B | https://www.melochenator.com/login
| PHPSESSID=dotfspp2c4gi3t2u8kl92n4ls0; Path=/; Domain=www.melochenator.com
| Cookie sent via https, but not marked as secure
|
| 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.
|
| M | http://melochenator.com/ 52.3.37.37
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | http://www.melochenator.com/ 52.3.37.37
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| N | https://www.melochenator.com/ 52.3.37.37
| https://www.melochenator.com/login
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://www.melochenator.com:80/ 52.3.37.37
| https://www.melochenator.com/login
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://www.melochenator.com/login
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| Q | https://melochenator.com:80/ 52.3.37.37
| https://melochenator.com/login
| Misconfiguration: https over port 80. Wrong port forwarding port 80 to port 443 or wrong vHost-definition
|
| Q | https://www.melochenator.com:80/ 52.3.37.37
| https://www.melochenator.com/login
| Misconfiguration: https over port 80. Wrong port forwarding port 80 to port 443 or wrong vHost-definition
|
| 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 |
| http://melochenator.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 52.3.37.37
|
| Fatal: Check of /.well-known/acme-challenge/random-filename has a http status between 400 and 499, but not 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://www.melochenator.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 52.3.37.37
|
| Fatal: Check of /.well-known/acme-challenge/random-filename has a http status between 400 and 499, but not 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge may not 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
|
| A | Duration: 81526 milliseconds, 81.526 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)