| 1. General Results, most used to calculate the result |
| A | name "missoula.live" is domain, public suffix is "live", top-level-domain-type is "generic", tld-manager is "United TLD Holdco Ltd."
|
| A | Good: All ip addresses are public addresses
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | Good: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
|
| B | https://missoula.live/ 142.4.30.145
|
| Missing HSTS-Header
|
| B | https://www.missoula.live/ 142.4.30.145
|
| Missing HSTS-Header
|
| B | https://missoula.live/ 142.4.30.145
| XSRF-TOKEN=eyJpdiI6IjVkYVEwTmZPUTh5clErdDNQUzFtdkE9PSIsInZhbHVlIjoiRkJnSUJLeVpOOE04K0pCY1hyazJTSDZxazY0dXdSRTVWTGt5SmV0NHZSeGk2OGNLUEVrMGphUmxhbzNPY0hQTlowR2pINFwvaXkwdW9Lbm9SYzhhWlh3PT0iLCJtYWMiOiJmNzk5ZDI1YWRlZjFlNWE2ODk1YTRmZDZiMWEwNGM3NDc1ZDk0MGU0ZTljZmNiYTI1MmYwMmFkOGU2NTY5NzAyIn0%3D; Path=/; Domain=missoula.live; Expires=2019-05-17 10:27:04
| Cookie sent via https, but not marked as secure
|
| B | https://missoula.live/ 142.4.30.145
| laravel_session=eyJpdiI6ImpseWpoMnhxb0tSbVpjUG52QzdaeWc9PSIsInZhbHVlIjoiS2JTbkY3eUx0d3NqeUxJM1VuNGlRdWhVWkNBSTQ0S3RhSzk5eEFFYVN0bUphUWFOQSsxeCtkZ0hhODNGVzVGK2lmbHo4cmFxOTZJMDBRdVFkdGVobFE9PSIsIm1hYyI6IjQyODMzODRjZDYwZmUxYWYxN2NmYjI1MzA1N2NmODY2NWQxYTVhZDU0N2Q4OTU1OGZmNThiMmYyNjc1ODQwZGYifQ%3D%3D; Path=/; Domain=missoula.live; Expires=2019-05-17 10:27:04; HttpOnly
| Cookie sent via https, but not marked as secure
|
| B | https://www.missoula.live/ 142.4.30.145
| XSRF-TOKEN=eyJpdiI6IjhmQkZFK2tZbkYydmp6WXZVN1ZWNHc9PSIsInZhbHVlIjoiXC9DYW9MOFQ2NGR3cWRWUlRIRkNTdXBHUWFCOGFpQWhkc3pWNER5OXN4Q1wva3NCR3gxT01WcE1qQ3NHK1NDZDFUVUVBdUc4bkxXUlZNeWhqYm5rbHlxdz09IiwibWFjIjoiZDUzZmQ2ZmExZGQ4OWE3YTEwMGY0ZDgyNGJhNDI4Y2VjOWQ0ZWY0ZWEyNmU1YmRhOTAyZjM5Njk0ODYyNmU2OSJ9; Path=/; Domain=www.missoula.live; Expires=2019-05-17 10:27:06
| Cookie sent via https, but not marked as secure
|
| B | https://www.missoula.live/ 142.4.30.145
| laravel_session=eyJpdiI6IjNBV2FwZk9VTDJGMXdxWldiZzBNR0E9PSIsInZhbHVlIjoiQllybXVvK2dcL2Z2ZmFEMHordEd0NUZsTWMxbFhqdTFqbmpXbFFhS1RcL0ttbkdrZW44OEN0eFBZK3VKTFwvV1BHWGZuUlBCQjJkK2hObU9LNEp1WXQ2eFE9PSIsIm1hYyI6IjUyODJhNDE2Zjk1OWRhNzk4NDMzODU0YWFkMmYxODc4OGFlMTNiNWIwN2Y4MTBjYTI5NGZlMDBmYmE0NDM4MzkifQ%3D%3D; Path=/; Domain=www.missoula.live; Expires=2019-05-17 10:27:06; HttpOnly
| 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.
|
| 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://missoula.live/ 142.4.30.145
|
| 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.missoula.live/ 142.4.30.145
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
|
| N | https://missoula.live/ 142.4.30.145
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://www.missoula.live/ 142.4.30.145
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| O | Old connection: SHA1 as Hash Algorithm is deprecated. Switch to SHA256 or SHA384. If your certificate has SHA256, first check your domain via ssllabs.com and update weak Cipher Suites. Forward Secrecy support is required. The part "Cipher Suites" should have a preference. First Cipher Suite with SHA instead of SHA256 or higher - that's the problem, change that. If that doesn't help, check if there is an old Firewall / router or something else, that supports only SHA1. Update that component.
|
| X | Fatal error: Nameserver doesn't support TCP connection: demand.alpha.aridns.net.au: Fatal error (-14). Details: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. - An existing connection was forcibly closed by the remote host
|
| 2. Header-Checks |
| 3. DNS- and NameServer - Checks |
| A | Good: Nameserver supports TCP connections: 2 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 2 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
|
| Nameserver doesn't pass all EDNS-Checks: demand.beta.aridns.net.au: 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 (dns3.ams). COOKIE: fatal timeout. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: demand.delta.aridns.net.au: 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 (dns5.ams). COOKIE: fatal timeout. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: demand.gamma.aridns.net.au: 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 (dns2.ams). COOKIE: fatal timeout. CLIENTSUBNET: ok.
|
| 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 | 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: 49123 milliseconds, 49.123 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)