| 1. General Results, most used to calculate the result |
| A | name "certainly.com" is domain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 108094 (complete: 276475)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: certainly.com has 8 different ip addresses (authoritative).
|
| A | Good: Minimal 2 ip addresses per domain name found: www.certainly.com has 2 different ip addresses (authoritative).
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: certainly.com has 4 ipv4, 4 ipv6 addresses
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: www.certainly.com has 1 ipv4, 1 ipv6 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: 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):0 complete Content-Type - header (2 urls)
|
| https://www.certainly.com/ 151.101.7.4
|
| Url with incomplete Content-Type - header - missing charset
|
| https://www.certainly.com/ 2a04:4e42:1::772
|
| Url with incomplete Content-Type - header - missing charset
|
| A | http://www.certainly.com/ 151.101.7.4
| https://www.certainly.com/
| Correct redirect http - https with the same domain name
|
| A | http://www.certainly.com/ 2a04:4e42:1::772
| https://www.certainly.com/
| Correct redirect http - https with the same domain name
|
| D | http://certainly.com/ 151.101.3.4
| http://www.certainly.com/
| 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://certainly.com/ 151.101.67.4
| http://www.certainly.com/
| 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://certainly.com/ 151.101.131.4
| http://www.certainly.com/
| 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://certainly.com/ 151.101.195.4
| http://www.certainly.com/
| 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://certainly.com/ 2a04:4e42::772
| http://www.certainly.com/
| 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://certainly.com/ 2a04:4e42:200::772
| http://www.certainly.com/
| 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://certainly.com/ 2a04:4e42:400::772
| http://www.certainly.com/
| 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://certainly.com/ 2a04:4e42:600::772
| http://www.certainly.com/
| 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://certainly.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 151.101.3.4
| http://www.certainly.com/.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://certainly.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 151.101.67.4
| http://www.certainly.com/.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://certainly.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 151.101.131.4
| http://www.certainly.com/.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://certainly.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 151.101.195.4
| http://www.certainly.com/.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://certainly.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a04:4e42::772
| http://www.certainly.com/.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://certainly.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a04:4e42:200::772
| http://www.certainly.com/.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://certainly.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a04:4e42:400::772
| http://www.certainly.com/.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://certainly.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a04:4e42:600::772
| http://www.certainly.com/.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.
|
| M | https://151.101.3.4/ 151.101.3.4
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://151.101.67.4/ 151.101.67.4
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://151.101.131.4/ 151.101.131.4
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://151.101.195.4/ 151.101.195.4
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://[2a04:4e42:0000:0000:0000:0000:0000:0772]/ 2a04:4e42::772
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://[2a04:4e42:0200:0000:0000:0000:0000:0772]/ 2a04:4e42:200::772
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://[2a04:4e42:0400:0000:0000:0000:0000:0772]/ 2a04:4e42:400::772
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://[2a04:4e42:0600:0000:0000:0000:0000:0772]/ 2a04:4e42:600::772
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://151.101.7.4/ 151.101.7.4
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://[2a04:4e42:0001:0000:0000:0000:0000:0772]/ 2a04:4e42:1::772
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| N | https://151.101.3.4/ 151.101.3.4
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://151.101.67.4/ 151.101.67.4
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://151.101.131.4/ 151.101.131.4
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://151.101.195.4/ 151.101.195.4
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://[2a04:4e42:0000:0000:0000:0000:0000:0772]/ 2a04:4e42::772
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://[2a04:4e42:0200:0000:0000:0000:0000:0772]/ 2a04:4e42:200::772
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://[2a04:4e42:0400:0000:0000:0000:0000:0772]/ 2a04:4e42:400::772
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://[2a04:4e42:0600:0000:0000:0000:0000:0772]/ 2a04:4e42:600::772
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://151.101.7.4/ 151.101.7.4
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://[2a04:4e42:0001:0000:0000:0000:0000:0772]/ 2a04:4e42:1::772
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| A | Good: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain certainly.com, 8 ip addresses.
|
| A | Good: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain www.certainly.com, 2 ip addresses.
|
| 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 certainly.com, 8 ip addresses, 1 different http results.
|
| 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 www.certainly.com, 2 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.certainly.com
|
| 2. Header-Checks |
| F | www.certainly.com 151.101.7.4
| Content-Security-Policy
| Critical: Missing Header:
|
| F | www.certainly.com 151.101.7.4
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | www.certainly.com 151.101.7.4
| Referrer-Policy
| Critical: Missing Header:
|
| F | www.certainly.com 151.101.7.4
| Permissions-Policy
| Critical: Missing Header:
|
| B | www.certainly.com 151.101.7.4
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | www.certainly.com 151.101.7.4
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | www.certainly.com 151.101.7.4
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| F | www.certainly.com 2a04:4e42:1::772
| Content-Security-Policy
| Critical: Missing Header:
|
| F | www.certainly.com 2a04:4e42:1::772
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | www.certainly.com 2a04:4e42:1::772
| Referrer-Policy
| Critical: Missing Header:
|
| F | www.certainly.com 2a04:4e42:1::772
| Permissions-Policy
| Critical: Missing Header:
|
| B | www.certainly.com 2a04:4e42:1::772
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | www.certainly.com 2a04:4e42:1::772
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | www.certainly.com 2a04:4e42:1::772
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 32 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 8 Name Servers.
|
| A | Info:: 32 Queries complete, 32 with IPv6, 0 with IPv4.
|
| A | Good: All DNS Queries done via IPv6.
|
| Ok (4 - 8):: An average of 4.0 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 8 different Name Servers found: edns1.ultradns.biz, edns1.ultradns.com, edns1.ultradns.net, edns1.ultradns.org, ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com, 8 Name Servers included in Delegation: edns1.ultradns.biz, edns1.ultradns.com, edns1.ultradns.net, edns1.ultradns.org, ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com, 8 Name Servers included in 1 Zone definitions: edns1.ultradns.biz, edns1.ultradns.com, edns1.ultradns.net, edns1.ultradns.org, ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com, 1 Name Servers listed in SOA.Primary: edns1.ultradns.com.
|
| A | Good: Only one SOA.Primary Name Server found.: edns1.ultradns.com.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: edns1.ultradns.com.
|
| 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: edns1.ultradns.biz, edns1.ultradns.com, edns1.ultradns.net, edns1.ultradns.org, ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com
|
| 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: 8 different Name Servers found
|
| A | Good: All name servers have ipv4- and ipv6-addresses.: 8 different Name Servers found
|
| A | Good: Name servers with different Top Level Domains / Public Suffix List entries found: 8 Name Servers, 4 Top Level Domains: org, net, com, biz
|
| A | Good: Name Servers with different domain names found.: 5 different Domains found
|
| A | Good: Name servers with different Country locations found: 8 Name Servers, 2 Countries: CA, US
|
| A | Info: Ipv4-Subnet-list: 8 Name Servers, 2 different subnets (first Byte): 204., 216., 2 different subnets (first two Bytes): 204.74., 216.239., 8 different subnets (first three Bytes): 204.74.110., 204.74.111., 204.74.66., 204.74.67., 216.239.32., 216.239.34., 216.239.36., 216.239.38.
|
| A | Good: Name Server IPv4-addresses from different subnet found:
|
| A | Info: IPv6-Subnet-list: 8 Name Servers with IPv6, 2 different subnets (first block): 2001:, 2610:, 3 different subnets (first two blocks): 2001:0502:, 2001:4860:, 2610:00a1:, 5 different subnets (first three blocks): 2001:0502:4612:, 2001:0502:f3ff:, 2001:4860:4802:, 2610:00a1:1014:, 2610:00a1:1015:, 8 different subnets (first four blocks): 2001:0502:4612:0000:, 2001:0502:f3ff:0000:, 2001:4860:4802:0032:, 2001:4860:4802:0034:, 2001:4860:4802:0036:, 2001:4860:4802:0038:, 2610:00a1:1014:0000:, 2610:00a1:1015:0000:
|
| A | Good: Name Server IPv6 addresses from different subnets found.
|
| A | Info: Nameserver mit different domain names found. May be a problem with DNS-Updates
|
| A | Good: Nameserver supports TCP connections: 16 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 16 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 16 good Nameserver
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 16 good Nameserver
|
| X | Fatal error: Nameservers with different SOA Serial Numbers
|
| A | Good: CAA entries found, creating certificate is limited: certainly.com is allowed to create certificates
|
| A | Good: CAA entries found, creating certificate is limited: globalsign.com is allowed to create certificates
|
| A | Good: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates
|
| Warning: Unknown CAA found: certainly.com isn't defined. Unknown entry. May be wrong written, may be not longer valid. May be a missing entry in this tool.
|
| 4. Content- and Performance-critical Checks |
| https://www.certainly.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Fatal: Check of /.well-known/acme-challenge/random-filename has a http status between 400 and 499, but not 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge may not work. 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).
|
| A | Good: No https + http status 200 with inline CSS / JavaScript found
|
| https://www.certainly.com/ 151.101.7.4
|
| 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.certainly.com/ 2a04:4e42:1::772
|
| 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. 2 external CSS / JavaScript files found
|
| A | Good: All svg-Images greater 1024 Bytes without internal compression are compressed. Svg is an Xml-Application, so Compression reduces the size of the file. 8 images (type image/svg+xml, image/x-icon, image/vnd.microsoft.icon) found with compression.
|
| 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, 2 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 2 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, 12 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 12 complete.
|
| A | Good: All checked attribute values are enclosed in quotation marks (" or ').
|
| A | Good: All img-elements have a valid alt-attribute.: 12 img-elements 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
|
| http://certainly.com/ 151.101.3.4
|
| Warning: HSTS header sent via http has no effect
|
| http://certainly.com/ 151.101.67.4
|
| Warning: HSTS header sent via http has no effect
|
| http://certainly.com/ 151.101.131.4
|
| Warning: HSTS header sent via http has no effect
|
| http://certainly.com/ 151.101.195.4
|
| Warning: HSTS header sent via http has no effect
|
| http://certainly.com/ 2a04:4e42::772
|
| Warning: HSTS header sent via http has no effect
|
| http://certainly.com/ 2a04:4e42:200::772
|
| Warning: HSTS header sent via http has no effect
|
| http://certainly.com/ 2a04:4e42:400::772
|
| Warning: HSTS header sent via http has no effect
|
| http://certainly.com/ 2a04:4e42:600::772
|
| Warning: HSTS header sent via http has no effect
|
| http://www.certainly.com/ 151.101.7.4
|
| Warning: HSTS header sent via http has no effect
|
| http://www.certainly.com/ 2a04:4e42:1::772
|
| Warning: HSTS header sent via http has no effect
|
| A | Duration: 196683 milliseconds, 196.683 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)