| 1. General Results, most used to calculate the result |
A | name "thesimshouse.synology.me" is domain, public suffix is "synology.me", top-level-domain-type is "country-code", Country is Montenegro, tld-manager is "Government of Montenegro"
|
A | Good: All ip addresses are public addresses
|
A | Good: Minimal 2 ip addresses per domain name found: thesimshouse.synology.me has 2 different ip addresses (authoritative).
|
A | Good: Ipv4 and Ipv6 addresses per domain name found: thesimshouse.synology.me has 1 ipv4, 1 ipv6 addresses
|
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: destination is https
|
A | Good - only one version with Http-Status 200
|
A | Good: one preferred version: non-www is preferred
|
| Warning: HSTS preload sent, but not in Preload-List. Never send a preload directive if you don't know what preload means. Check https://hstspreload.org/ to learn the basics about the Google-Preload list. If you send a preload directive, you should **immediately** add your domain to the HSTS preload list via https://hstspreload.org/ . If Google accepts the domain, so the status is "pending": Note that new entries are hardcoded into the Chrome source code and can take several months before they reach the stable version. So you will see this message some months. If you don't want that or if you don't understand "preload", but if you send a preload directive and if you have correct A-redirects, everybody can add your domain to that list. Then you may have problems, it's not easy to undo that. So if you don't want your domain preloaded, remove the preload directive.
|
| 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):1 complete Content-Type - header (3 urls)
|
| http://thesimshouse.synology.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 108.162.85.109
|
| Url with incomplete Content-Type - header - missing charset
|
| http://www.thesimshouse.synology.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 108.162.85.109
|
| Url with incomplete Content-Type - header - missing charset
|
A | http://thesimshouse.synology.me/ 108.162.85.109
| https://thesimshouse.synology.me/
| Correct redirect http - https with the same domain name
|
B | Warning: HSTS max-age is too short - minimum 31536000 = 365 days required, 15768000 seconds = 182 days found
|
B | https://www.thesimshouse.synology.me/ 108.162.85.109
|
| Missing HSTS-Header
|
B | https://108.162.85.109/ 108.162.85.109
|
| Missing HSTS-Header
|
D | http://www.thesimshouse.synology.me/ 108.162.85.109
| http://www.thesimshouse.synology.me:5000/
| 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.
|
I | https://thesimshouse.synology.me/ 108.162.85.109
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
|
K | http://thesimshouse.synology.me/ 108.162.85.109, Status 301
| http://thesimshouse.synology.me/ 2001:1970:49e4:e300:211:32ff:fea6:9c61, Status -14
| Configuration problem - different ip addresses with different status
|
K | https://thesimshouse.synology.me/ 108.162.85.109, Status 200
| https://thesimshouse.synology.me/ 2001:1970:49e4:e300:211:32ff:fea6:9c61, Status -14
| Configuration problem - different ip addresses with different status
|
K | http://thesimshouse.synology.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 108.162.85.109, Status 404
| http://thesimshouse.synology.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:1970:49e4:e300:211:32ff:fea6:9c61, Status -14
| Configuration problem - different ip addresses with different status
|
N | https://www.thesimshouse.synology.me/ 108.162.85.109
| https://www.thesimshouse.synology.me:5001/
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
N | https://108.162.85.109/ 108.162.85.109
| https://108.162.85.109:5001/
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| 2. Header-Checks |
| 3. DNS- and NameServer - Checks |
A | Good: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
|
| Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 2 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.: 2 Name Servers, 1 Top Level Domain: to
|
| Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: quickconnect.to
|
A | Good: Name servers with different Country locations found: 2 Name Servers, 2 Countries: DE, GB
|
A | Info: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 157., 68., 2 different subnets (first two Bytes): 157.245., 68.183., 2 different subnets (first three Bytes): 157.245.20., 68.183.254.
|
A | Excellent: Every Name Server IPv4-address starts with an unique Byte.
|
A | Good: Nameserver supports TCP connections: 1 good Nameserver
|
A | Good: Nameserver supports Echo Capitalization: 1 good Nameserver
|
A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver
|
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: c0.nic.me: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (ns009b.app13.ams2.afilias-nst.info). COOKIE: ok. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: ddns-ns1.quickconnect.to: 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.
|
A | Good: All SOA have the same Serial Number
|
A | Good: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates
|
| 4. Content- and Performance-critical Checks |
| http://thesimshouse.synology.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:1970:49e4:e300:211:32ff:fea6:9c61
|
| Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://thesimshouse.synology.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:1970:49e4:e300:211:32ff:fea6:9c61, Status -14
| http://thesimshouse.synology.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 108.162.85.109, 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://thesimshouse.synology.me/ 108.162.85.109
|
| 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://thesimshouse.synology.me/ 108.162.85.109
|
| 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://thesimshouse.synology.me/ 108.162.85.109
|
| 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://thesimshouse.synology.me/ 108.162.85.109
|
| 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. 6 external CSS / JavaScript files without GZip found - 13 with GZip, 19 complete
|
| Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 16 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 0 with Cache-Control max-age too short (minimum 7 days), 3 with Cache-Control long enough, 19 complete.
|
| Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 1 image files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 0 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 1 complete.
|
A | Good: All checked attribute values are enclosed in quotation marks (" or ').
|
| Wrong: img-elements without alt-attribute or empty alt-attribute found. The alt-attribute ("alternative") is required and should describe the img. So Screenreader and search engines are able to use these informations.: 1 img-elements without alt-attribute, 0 img-elements with empty alt-attribute 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
|
A | Duration: 211510 milliseconds, 211.510 seconds
|