| 1. General Results, most used to calculate the result |
| A | name "chollosparabodas.es" is domain, public suffix is "es", top-level-domain-type is "country-code", Country is Spain, tld-manager is "Red.es"
|
| A | Good: All ip addresses are public addresses
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | https://www.chollosparabodas.es/ 172.217.19.211
| https://www.chollosparabodas.es/p/inicio.html?m=1
| Correct redirect https to https
|
| A | https://www.chollosparabodas.es/ 216.58.207.51
| https://www.chollosparabodas.es/p/inicio.html?m=1
| Correct redirect https to https
|
| A | https://www.chollosparabodas.es/ 2a00:1450:400e:808::2013
| https://www.chollosparabodas.es/p/inicio.html?m=1
| Correct redirect https to https
|
| 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: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):2 complete Content-Type - header (4 urls)
|
| http://chollosparabodas.es/ 185.125.78.41
|
| Url with incomplete Content-Type - header - missing charset
|
| http://chollosparabodas.es/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.125.78.41
|
| Url with incomplete Content-Type - header - missing charset
|
| A | http://www.chollosparabodas.es/ 172.217.19.211
| https://www.chollosparabodas.es/
| Correct redirect http - https with the same domain name
|
| A | http://www.chollosparabodas.es/ 216.58.207.51
| https://www.chollosparabodas.es/
| Correct redirect http - https with the same domain name
|
| A | http://www.chollosparabodas.es/ 2a00:1450:400e:808::2013
| https://www.chollosparabodas.es/
| Correct redirect http - https with the same domain name
|
| B | https://chollosparabodas.es/ 185.125.78.41
|
| Missing HSTS-Header
|
| B | https://chollosparabodas.es/ 216.239.32.21
|
| Missing HSTS-Header
|
| B | https://chollosparabodas.es/ 216.239.34.21
|
| Missing HSTS-Header
|
| B | https://chollosparabodas.es/ 216.239.36.21
|
| Missing HSTS-Header
|
| B | https://chollosparabodas.es/ 216.239.38.21
|
| Missing HSTS-Header
|
| B | https://www.chollosparabodas.es/ 172.217.19.211
|
| Missing HSTS-Header
|
| B | https://www.chollosparabodas.es/ 216.58.207.51
|
| Missing HSTS-Header
|
| B | https://www.chollosparabodas.es/ 2a00:1450:400e:808::2013
|
| Missing HSTS-Header
|
| B | https://www.chollosparabodas.es/p/inicio.html?m=1
|
| Missing HSTS-Header
|
| B | https://chollosparabodas.es/ 185.125.78.41
| PHPSESSID=jftkd5shhq47i4epfupptr95p3; Path=/; Domain=chollosparabodas.es
| 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.
|
| D | http://chollosparabodas.es/ 216.239.32.21
| http://www.chollosparabodas.es/
| 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://chollosparabodas.es/ 216.239.34.21
| http://www.chollosparabodas.es/
| 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://chollosparabodas.es/ 216.239.36.21
| http://www.chollosparabodas.es/
| 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://chollosparabodas.es/ 216.239.38.21
| http://www.chollosparabodas.es/
| 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://chollosparabodas.es/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 216.239.32.21
| http://www.chollosparabodas.es/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| 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://chollosparabodas.es/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 216.239.34.21
| http://www.chollosparabodas.es/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| 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://chollosparabodas.es/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 216.239.36.21
| http://www.chollosparabodas.es/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| 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://chollosparabodas.es/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 216.239.38.21
| http://www.chollosparabodas.es/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| 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.
|
| 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://www.chollosparabodas.es/p/inicio.html?m=1
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
|
| I | https://www.chollosparabodas.es/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
|
| K | http://chollosparabodas.es/ 185.125.78.41, Status 200
| http://chollosparabodas.es/ 216.239.32.21, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://chollosparabodas.es/ 185.125.78.41, Status 200
| http://chollosparabodas.es/ 216.239.34.21, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://chollosparabodas.es/ 185.125.78.41, Status 200
| http://chollosparabodas.es/ 216.239.36.21, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://chollosparabodas.es/ 185.125.78.41, Status 200
| http://chollosparabodas.es/ 216.239.38.21, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://chollosparabodas.es/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.125.78.41, Status 404
| http://chollosparabodas.es/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 216.239.32.21, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://chollosparabodas.es/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.125.78.41, Status 404
| http://chollosparabodas.es/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 216.239.34.21, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://chollosparabodas.es/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.125.78.41, Status 404
| http://chollosparabodas.es/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 216.239.36.21, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://chollosparabodas.es/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.125.78.41, Status 404
| http://chollosparabodas.es/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 216.239.38.21, Status 301
| Configuration problem - different ip addresses with different status
|
| N | https://chollosparabodas.es/ 185.125.78.41
| https://tutoriales.nu/
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | 185.125.78.41:465
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | 185.125.78.41:2083
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | 185.125.78.41:2087
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | 185.125.78.41:2096
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| R | https://chollosparabodas.es/ 185.125.78.41
| https://tutoriales.nu/
| Redirect to not existing domain
|
| X | Fatal error: Nameserver doesn't support TCP connection: g.nic.es: Fatal error (-14). Details: Unable to read data from the transport connection: Eine vorhandene Verbindung wurde vom Remotehost geschlossen. - Eine vorhandene Verbindung wurde vom Remotehost geschlossen
|
| 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: dns1.canaldominios.com,dns2.canaldominios.com,dns3.canaldominios.com,dns4.canaldominios.com
|
| A | Good: Nameserver supports TCP connections: 4 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 4 good Nameserver
|
| X | Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: dns1.canaldominios.com
|
| X | Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: dns2.canaldominios.com
|
| X | Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: dns3.canaldominios.com
|
| X | Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: dns4.canaldominios.com
|
| Nameserver doesn't pass all EDNS-Checks: dns1.canaldominios.com / 82.194.64.50: 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: dns2.canaldominios.com / 82.194.64.51: 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: dns3.canaldominios.com / 82.194.64.50: 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: dns4.canaldominios.com / 82.194.64.51: 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: ns-es.nic.fr: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (dns.fra.nic.fr). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
|
| A | Good: All SOA have the same Serial Number
|
| A | Good: CAA entries found, creating certificate is limited: pki.goog is allowed to create certificates
|
| 4. Content- and Performance-critical Checks |
| A | Good: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. 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.chollosparabodas.es/p/inicio.html?m=1
|
| 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.chollosparabodas.es/p/inicio.html?m=1
|
| 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.
|
| A | Good: Every https connection via port 443 supports the http/2 protocol via ALPN.
|
| Warning: CSS / JavaScript found without Compression. Compress these ressources, gzip, deflate, br are checked. 4 external CSS / JavaScript files without GZip found - 21 with GZip, 25 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. 18 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, 13 with Cache-Control max-age too short (minimum 7 days), 12 with Cache-Control long enough, 25 complete.
|
| Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 0 image files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 17 with Cache-Control max-age too short (minimum 7 days), 4 with Cache-Control long enough, 21 complete.
|
| A | Good: All checked attribute values are enclosed in quotation marks (" or ').
|
| A | Good: Some img-elements have a valid alt-attribute.: 21 img-elements found, 18 img-elements with correct alt-attributes (defined, not an empty value).
|
| Wrong: img-elements without alt-attribute or empty alt-attribute found. The alt-attribute ("alternative") is required and should describe the img. So Screenreader and search engines are able to use these informations.: 3 img-elements without alt-attribute, 0 img-elements with empty alt-attribute 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
|
| https://www.chollosparabodas.es/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| 2.614 seconds
| Warning: 404 needs more then one second
|
| A | Info: Different Server-Headers found
|
| A | Duration: 179120 milliseconds, 179.120 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)