| 1. General Results, most used to calculate the result |
| A | name "mk.paranaweb.com.br" is subdomain, public suffix is ".com.br", top-level-domain is ".br", top-level-domain-type is "country-code", Country is Brazil, tld-manager is "Comite Gestor da Internet no Brasil", num .br-domains preloaded: 2925 (complete: 231048)
|
| A | Good: All ip addresses are public addresses
|
| Warning: Only one ip address found: mk.paranaweb.com.br has only one ip address.
|
| Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: mk.paranaweb.com.br has no ipv6 address.
|
| 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 - only one version with Http-Status 200
|
| A | Good: No cookie sent via http.
|
| 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):3 complete Content-Type - header (4 urls)
|
| http://mk.paranaweb.com.br/ 186.233.204.21
|
| Url with incomplete Content-Type - header - missing charset
|
| B | https://mk.paranaweb.com.br/ 186.233.204.21
|
| Missing HSTS-Header
|
| H | Fatal error: No https - result with http-status 200, no encryption
|
| 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.
|
| M | https://mk.paranaweb.com.br/ 186.233.204.21
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://186.233.204.21/ 186.233.204.21
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| N | https://mk.paranaweb.com.br/ 186.233.204.21
|
| Error - Certificate isn't trusted, RemoteCertificateChainErrors
|
| N | https://186.233.204.21/ 186.233.204.21
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| O | mk.paranaweb.com.br / 186.233.204.21 / 443
|
| Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 6 Cipher Suites without Forward Secrecy found
|
| X | Fatal error: Nameserver doesn't support TCP connection: ns2.paranaweb.com.br / 186.233.204.10: Timeout
|
| X | Fatal error: Nameserver doesn't support TCP connection: paranaweb.com.br / 186.233.204.24: Timeout
|
| Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain mk.paranaweb.com.br, 1 ip addresses, 1 different http results.
|
| B | No _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.mk.paranaweb.com.br
|
| 2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05) |
| F | mk.paranaweb.com.br 186.233.204.21
| Content-Security-Policy
| Critical: Missing Header:
|
| F | mk.paranaweb.com.br 186.233.204.21
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | mk.paranaweb.com.br 186.233.204.21
| Referrer-Policy
| Critical: Missing Header:
|
| F | mk.paranaweb.com.br 186.233.204.21
| Permissions-Policy
| Critical: Missing Header:
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 5 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
|
| A | Info:: 5 Queries complete, 3 with IPv6, 2 with IPv4.
|
| Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses.
|
| A | Good: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns1.paranaweb.com.br (186.233.204.9), ns1.paranaweb.com.br (186.233.204.9), ns2.paranaweb.com.br (186.233.204.10)
|
| A | Good (1 - 3.0):: An average of 1.7 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 3 different Name Servers found: ns1.paranaweb.com.br, ns2.paranaweb.com.br, paranaweb.com.br, 2 Name Servers included in Delegation: ns1.paranaweb.com.br, ns2.paranaweb.com.br, 3 Name Servers included in 2 Zone definitions: ns1.paranaweb.com.br, ns2.paranaweb.com.br, paranaweb.com.br, 1 Name Servers listed in SOA.Primary: ns1.paranaweb.com.br.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.paranaweb.com.br.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.paranaweb.com.br.
|
| X | Fatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns1.paranaweb.com.br (186.233.204.9): Delegation: ns1.paranaweb.com.br, ns2.paranaweb.com.br, Zone: ns1.paranaweb.com.br, ns2.paranaweb.com.br, paranaweb.com.br. Name Servers defined in Zone, missing in Delegation: paranaweb.com.br.
|
| A | Good: All Name Server Domain Names have a Public Suffix.
|
| A | Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
|
| A | Good: All Name Server ip addresses are public.
|
| A | Good: Minimal 2 different name servers (public suffix and public ip address) found: 3 different Name Servers found
|
| Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 3 different Name Servers found
|
| Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 3 Name Servers, 1 Top Level Domain: com.br
|
| A | Good: Name Servers with different domain names found.: 2 different Domains found
|
| Warning: All Name Servers from the same Country / IP location.: 3 Name Servers, 1 Countries: BR
|
| A | Info: Ipv4-Subnet-list: 3 Name Servers, 1 different subnets (first Byte): 186., 1 different subnets (first two Bytes): 186.233., 1 different subnets (first three Bytes): 186.233.204.
|
| X | Fatal: All Name Server IPv4 addresses from the same subnet. Check https://www.iana.org/help/nameserver-requirements to learn some basics about name server configurations. If you manage these name servers, fix it. If it's your provider, change your provider.:
|
| A | Good: Nameserver supports TCP connections: 1 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 1 good Nameserver
|
| X | Nameserver Timeout checking Echo Capitalization: ns2.paranaweb.com.br / 186.233.204.10
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver
|
| X | Nameserver Timeout checking EDNS512: ns2.paranaweb.com.br / 186.233.204.10
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 1 good Nameserver
|
| Nameserver doesn't pass all EDNS-Checks: ns1.paranaweb.com.br: 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: ns2.paranaweb.com.br / 186.233.204.10: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: paranaweb.com.br / 186.233.204.24: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
|
| 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 |
| 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 | 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
|
| A | Duration: 592114 milliseconds, 592.114 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)