| 1. General Results, most used to calculate the result |
| A | name "calendarioazul.com.br" is domain, public suffix is "com.br", top-level-domain-type is "country-code", Country is Brazil, tld-manager is "Comite Gestor da Internet no Brasil"
|
| 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
|
| A | Good: every https has a Strict Transport Security Header
|
| A | Good: HSTS max-age is long enough, 31536000 seconds = 365 days
|
| 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)
|
| A | http://calendarioazul.com.br/ 157.230.103.136
| https://calendarioazul.com.br/
| Correct redirect http - https with the same domain name
|
| A | http://calendarioazul.com.br/ 157.230.120.63
| https://calendarioazul.com.br/
| Correct redirect http - https with the same domain name
|
| A | http://www.calendarioazul.com.br/ 68.183.215.91
| https://www.calendarioazul.com.br/
| Correct redirect http - https with the same domain name
|
| A | http://www.calendarioazul.com.br/ 167.99.137.12
| https://www.calendarioazul.com.br/
| Correct redirect http - https with the same domain name
|
| M | https://157.230.103.136/ 157.230.103.136
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://157.230.120.63/ 157.230.120.63
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://68.183.215.91/ 68.183.215.91
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://167.99.137.12/ 167.99.137.12
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| N | https://157.230.103.136/ 157.230.103.136
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://157.230.120.63/ 157.230.120.63
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://68.183.215.91/ 68.183.215.91
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://167.99.137.12/ 167.99.137.12
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| 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.p07.nsone.net,dns2.p07.nsone.net,dns3.p07.nsone.net,dns4.p07.nsone.net
|
| 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 |
| https://www.calendarioazul.com.br/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html 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.calendarioazul.com.br/ 68.183.215.91
|
| 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.calendarioazul.com.br/ 167.99.137.12
|
| 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.calendarioazul.com.br/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| 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.calendarioazul.com.br/ 68.183.215.91
|
| 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.calendarioazul.com.br/ 167.99.137.12
|
| 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.calendarioazul.com.br/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| 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.
|
| A | Good: All CSS / JavaScript files are sent compressed (gzip, deflate, br checked). That reduces the content of the files. 9 external CSS / JavaScript files found
|
| 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, 9 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 9 complete.
|
| A | Good: All checked attribute values are enclosed in quotation marks (" or ').
|
| A | Info: No img element found, no alt attribute checked
|
| 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://157.230.103.136/ 157.230.103.136
| 2.363 seconds
| Warning: 404 needs more then one second
|
| https://157.230.120.63/ 157.230.120.63
| 2.370 seconds
| Warning: 404 needs more then one second
|
| https://68.183.215.91/ 68.183.215.91
| 2.403 seconds
| Warning: 404 needs more then one second
|
| https://167.99.137.12/ 167.99.137.12
| 2.370 seconds
| Warning: 404 needs more then one second
|
| A | Duration: 157046 milliseconds, 157.046 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)