| 1. General Results, most used to calculate the result |
| A | name "grabadiesel.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: destination is https
|
| A | Good - only one version with Http-Status 200
|
| A | Good: one preferred version: www is preferred
|
| 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: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
|
| B | https://www.centextruckandauto.com/
|
| Missing HSTS-Header
|
| D | http://grabadiesel.com/ 74.208.236.219
| http://centextruckandauto.com
| Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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.
|
| D | http://grabadiesel.com/ 2607:f1c0:100f:f000::276
| http://centextruckandauto.com
| Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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.
|
| D | http://www.grabadiesel.com/ 74.208.236.219
| http://centextruckandauto.com
| Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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.
|
| D | http://www.grabadiesel.com/ 2607:f1c0:100f:f000::276
| http://centextruckandauto.com
| Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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.
|
| E | http://centextruckandauto.com
| https://www.centextruckandauto.com/
| 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.
|
| P | https://grabadiesel.com/ 74.208.236.219
|
| 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://grabadiesel.com/ 2607:f1c0:100f:f000::276
|
| 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.grabadiesel.com/ 74.208.236.219
|
| 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.grabadiesel.com/ 2607:f1c0:100f:f000::276
|
| 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: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: ns1064.ui-dns.biz,ns1071.ui-dns.de,ns1090.ui-dns.org,ns1107.ui-dns.com
|
| A | Good: Nameserver supports TCP connections: 8 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 8 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 8 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://grabadiesel.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 74.208.236.219
|
| 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://grabadiesel.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2607:f1c0:100f:f000::276
|
| 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.grabadiesel.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 74.208.236.219
|
| 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.grabadiesel.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2607:f1c0:100f:f000::276
|
| 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.
|
| A | Good: Every https result with status 200 and greater 1024 Bytes is compressed (gzip, deflate, br checked).
|
| https://www.centextruckandauto.com/
|
| Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header.
|
| https://www.centextruckandauto.com/
|
| Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
|
| https://www.centextruckandauto.com/
|
| Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
|
| Warning: CSS / JavaScript found without Compression. Compress these ressources, gzip, deflate, br are checked. 4 external CSS / JavaScript files without GZip found - 3 with GZip, 7 complete
|
| A | Good: All images with internal compression not compressed. Some Images (.png, .jpg, .jpeg, .webp, .gif) are already compressed, so an additional compression isn't helpful. 2 images (type image/png, image/jpg) found without additional GZip. Not required because these images are already compressed
|
| Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 0 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 1 with Cache-Control max-age too short (minimum 7 days), 6 with Cache-Control long enough, 7 complete.
|
| Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 20 image files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 0 with Cache-Control max-age too short (minimum 7 days), 3 with Cache-Control long enough, 23 complete.
|
| A | Good: All checked attribute values are enclosed in quotation marks (" or ').
|
| A | Good: All img-elements have a valid alt-attribute.: 23 img-elements found.
|
| 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: 85533 milliseconds, 85.533 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)