| 1. General Results, most used to calculate the result |
| A | name "en.furusjoenrundt.no" is subdomain, public suffix is "no", top-level-domain-type is "country-code", Country is Norway, tld-manager is "UNINETT Norid A/S"
|
| A | Good: All ip addresses are public addresses
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | Good: destination is https
|
| 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):4 complete Content-Type - header (7 urls)
|
| https://en.furusjoenrundt.no/ 2a02:1660:4104:630c:62:50:189:186
|
| Url with incomplete Content-Type - header - missing charset
|
| https://www.en.furusjoenrundt.no/ 62.50.189.186
|
| Url with incomplete Content-Type - header - missing charset
|
| https://www.en.furusjoenrundt.no/ 2a02:1660:4104:630c:62:50:189:186
|
| Url with incomplete Content-Type - header - missing charset
|
| B | https://en.furusjoenrundt.no/ 35.176.138.189
|
| Missing HSTS-Header
|
| B | https://test.bapp.no/
|
| Missing HSTS-Header
|
| B | https://en.furusjoenrundt.no/ 2a02:1660:4104:630c:62:50:189:186
|
| Missing HSTS-Header
|
| B | https://www.furusjoenrundt.no/
|
| Missing HSTS-Header
|
| B | https://www.en.furusjoenrundt.no/ 62.50.189.186
|
| Missing HSTS-Header
|
| B | https://www.en.furusjoenrundt.no/ 2a02:1660:4104:630c:62:50:189:186
|
| Missing HSTS-Header
|
| 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.
|
| D | http://en.furusjoenrundt.no/ 2a02:1660:4104:630c:62:50:189:186
| http://www.furusjoenrundt.no/
| 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.en.furusjoenrundt.no/ 62.50.189.186
| http://www.furusjoenrundt.no/
| 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.en.furusjoenrundt.no/ 2a02:1660:4104:630c:62:50:189:186
| http://www.furusjoenrundt.no/
| 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://en.furusjoenrundt.no/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:1660:4104:630c:62:50:189:186
| http://www.furusjoenrundt.no/404.shtml
| 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.en.furusjoenrundt.no/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 62.50.189.186
| http://www.furusjoenrundt.no/404.shtml
| 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.en.furusjoenrundt.no/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:1660:4104:630c:62:50:189:186
| http://www.furusjoenrundt.no/404.shtml
| 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://en.furusjoenrundt.no/ 35.176.138.189
| https://test.bapp.no/
| 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.
|
| I | http://en.furusjoenrundt.no/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 35.176.138.189
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Not used to calculate the result because it's a http - check. But listed so you should fix it.
|
| K | https://en.furusjoenrundt.no/ 35.176.138.189, Status 301
| https://en.furusjoenrundt.no/ 2a02:1660:4104:630c:62:50:189:186, Status 200
| Configuration problem - different ip addresses with different status
|
| K | http://en.furusjoenrundt.no/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 35.176.138.189, Status 404
| http://en.furusjoenrundt.no/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:1660:4104:630c:62:50:189:186, Status 301
| Configuration problem - different ip addresses with different status
|
| L | https://en.furusjoenrundt.no/ 35.176.138.189
| https://en.furusjoenrundt.no/
| Error direct loop
|
| N | https://en.furusjoenrundt.no/ 35.176.138.189
| https://en.furusjoenrundt.no/
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://en.furusjoenrundt.no/ 2a02:1660:4104:630c:62:50:189:186
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://www.en.furusjoenrundt.no/ 62.50.189.186
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://www.en.furusjoenrundt.no/ 2a02:1660:4104:630c:62:50:189:186
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | www.en.furusjoenrundt.no:465
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | www.en.furusjoenrundt.no:993
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | www.en.furusjoenrundt.no:995
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | www.en.furusjoenrundt.no:2222
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | 62.50.189.186:465
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | 62.50.189.186:993
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | 62.50.189.186:995
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | 62.50.189.186:2222
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| 2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05) |
| 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
|
| 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.
|
| http://en.furusjoenrundt.no/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:1660:4104:630c:62:50:189:186, Status 301
| http://en.furusjoenrundt.no/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 35.176.138.189, Status 404
| Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| https://en.furusjoenrundt.no/ 2a02:1660:4104:630c:62:50:189:186
|
| Warning: https result with status 200 and size greater then 1024 Bytes without Compression found. Add Compression support (gzip, deflate, br - these are checked) so the html content is compressed.
|
| https://www.en.furusjoenrundt.no/ 62.50.189.186
|
| Warning: https result with status 200 and size greater then 1024 Bytes without Compression found. Add Compression support (gzip, deflate, br - these are checked) so the html content is compressed.
|
| https://www.en.furusjoenrundt.no/ 2a02:1660:4104:630c:62:50:189:186
|
| Warning: https result with status 200 and size greater then 1024 Bytes without Compression found. Add Compression support (gzip, deflate, br - these are checked) so the html content is compressed.
|
| https://test.bapp.no/
|
| 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.furusjoenrundt.no/
|
| 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://test.bapp.no/
|
| 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.furusjoenrundt.no/
|
| 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://test.bapp.no/
|
| 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.
|
| https://www.furusjoenrundt.no/
|
| 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. 2 external CSS / JavaScript files without GZip found - 103 with GZip, 105 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. 81 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. 17 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 24 with Cache-Control max-age too short (minimum 7 days), 81 with Cache-Control long enough, 122 complete.
|
| A | Good: All images are sent with a long Cache-Control header (minimum 7 days). So the browser can reuse these files, no download is required. 103 image files with long Cache-Control max-age 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.furusjoenrundt.no/404.shtml
| 3.907 seconds
| Warning: 404 needs more then one second
|
| A | Info: Different Server-Headers found
|
| A | Duration: 118116 milliseconds, 118.116 seconds
|