| 1. General Results, most used to calculate the result |
| A | name "pinkpurplehome.tw1.quickconnect.to" is subdomain, public suffix is ".to", top-level-domain is ".to", top-level-domain-type is "country-code", Country is Tonga, tld-manager is "Government of the Kingdom of Tonga
H.R.H. Crown Prince Tupouto'a
c/o Consulate of Tonga", num .to-domains preloaded: 126 (complete: 276475)
|
| A | Good: All ip addresses are public addresses
|
| Warning: Only one ip address found: pinkpurplehome.tw1.quickconnect.to has only one ip address.
|
| Warning: Only one ip address found: www.pinkpurplehome.tw1.quickconnect.to 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: pinkpurplehome.tw1.quickconnect.to has no ipv6 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: www.pinkpurplehome.tw1.quickconnect.to has no ipv6 address.
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | https://www.pinkpurplehome.tw1.quickconnect.to/ 125.228.116.235
| https://www.quickconnect.to/portal/error.html?error=20
| Correct redirect https to https
|
| 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 (5 urls)
|
| http://pinkpurplehome.quickconnect.to/
|
| Url with incomplete Content-Type - header - missing charset
|
| http://portal.quickconnect.to/error.html?error=20
|
| Url with incomplete Content-Type - header - missing charset
|
| http://portal.quickconnect.to/https_first/error.html?error=20
|
| Url with incomplete Content-Type - header - missing charset
|
| http://pinkpurplehome.quickconnect.to/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Url with incomplete Content-Type - header - missing charset
|
| https://125.228.116.235/ 125.228.116.235
|
| Url with incomplete Content-Type - header - missing charset
|
| B | https://pinkpurplehome.tw1.quickconnect.to/ 125.228.116.235
|
| Missing HSTS-Header
|
| B | https://www.quickconnect.to/portal/error.html?error=20
|
| Missing HSTS-Header
|
| B | https://www.pinkpurplehome.tw1.quickconnect.to/ 125.228.116.235
|
| Missing HSTS-Header
|
| D | http://pinkpurplehome.tw1.quickconnect.to/ 125.228.116.235
| http://pinkpurplehome.quickconnect.to/
| 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.quickconnect.to/portal/error.html?error=20
| http://portal.quickconnect.to/error.html?error=20
| 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.pinkpurplehome.tw1.quickconnect.to/ 125.228.116.235
| http://www.quickconnect.to/portal/error.html?error=20
| 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://pinkpurplehome.tw1.quickconnect.to/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 125.228.116.235
| http://pinkpurplehome.quickconnect.to/.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://www.pinkpurplehome.tw1.quickconnect.to/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 125.228.116.235
| http://www.quickconnect.to/portal/error.html?error=20
| 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.
|
| F | https://pinkpurplehome.tw1.quickconnect.to/ 125.228.116.235
| http://pinkpurplehome.quickconnect.to/
| Wrong redirect https - http - never redirect https to http
|
| F | https://www.quickconnect.to/portal/error.html?error=20
| http://portal.quickconnect.to/https_first/error.html?error=20
| Wrong redirect https - http - never redirect https to http
|
| 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 | http://pinkpurplehome.quickconnect.to/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| 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.
|
| N | https://www.pinkpurplehome.tw1.quickconnect.to/ 125.228.116.235
| https://www.quickconnect.to/portal/error.html?error=20
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://125.228.116.235/ 125.228.116.235
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| O | pinkpurplehome.tw1.quickconnect.to / 125.228.116.235 / 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
|
| O | www.pinkpurplehome.tw1.quickconnect.to / 125.228.116.235 / 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
|
| 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 different. So that domain requires Server Name Indication (SNI), so the server is able to select the correct certificate.: Domain pinkpurplehome.tw1.quickconnect.to, 1 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 different. So that domain requires Server Name Indication (SNI), so the server is able to select the correct certificate.: Domain www.pinkpurplehome.tw1.quickconnect.to, 1 ip addresses.
|
| 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.pinkpurplehome.tw1.quickconnect.to
|
| 2. Header-Checks |
| U |
|
| No https result with http status 2** or 4** (standard-check) found, no header checked.
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 16 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
|
| A | Info:: 16 Queries complete, 16 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:: 4 different Name Servers found: ns-1412.awsdns-48.org, ns-1987.awsdns-56.co.uk, ns-55.awsdns-06.com, ns-597.awsdns-10.net, 4 Name Servers included in Delegation: ns-1412.awsdns-48.org, ns-1987.awsdns-56.co.uk, ns-55.awsdns-06.com, ns-597.awsdns-10.net, 4 Name Servers included in 1 Zone definitions: ns-1412.awsdns-48.org, ns-1987.awsdns-56.co.uk, ns-55.awsdns-06.com, ns-597.awsdns-10.net, 1 Name Servers listed in SOA.Primary: ns-55.awsdns-06.com.
|
| A | Good: Only one SOA.Primary Name Server found.: ns-55.awsdns-06.com.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns-55.awsdns-06.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: ns-1412.awsdns-48.org, ns-1987.awsdns-56.co.uk, ns-55.awsdns-06.com, ns-597.awsdns-10.net
|
| 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: 4 different Name Servers found
|
| A | Good: All name servers have ipv4- and ipv6-addresses.: 4 different Name Servers found
|
| A | Good: Name servers with different Top Level Domains / Public Suffix List entries found: 4 Name Servers, 4 Top Level Domains: org, net, com, co.uk
|
| A | Good: Name Servers with different domain names found.: 4 different Domains found
|
| Warning: All Name Servers from the same Country / IP location.: 4 Name Servers, 1 Countries: US
|
| A | Info: Ipv4-Subnet-list: 4 Name Servers, 1 different subnets (first Byte): 205., 1 different subnets (first two Bytes): 205.251., 4 different subnets (first three Bytes): 205.251.192., 205.251.194., 205.251.197., 205.251.199.
|
| A | Good: Name Server IPv4-addresses from different subnet found:
|
| A | Info: IPv6-Subnet-list: 4 Name Servers with IPv6, 1 different subnets (first block): 2600:, 1 different subnets (first two blocks): 2600:9000:, 4 different subnets (first three blocks): 2600:9000:5300:, 2600:9000:5302:, 2600:9000:5305:, 2600:9000:5307:, 4 different subnets (first four blocks): 2600:9000:5300:3700:, 2600:9000:5302:5500:, 2600:9000:5305:8400:, 2600:9000:5307:c300:
|
| A | Good: Name Server IPv6 addresses from different subnets found.
|
| 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
|
| X | Nameserver Timeout checking EDNS512: ns-55.awsdns-06.com / 2600:9000:5300:3700::1
|
| 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: ns.trs-dns.com: 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: amazon.com is allowed to create certificates
|
| A | Good: CAA entries found, creating certificate is limited: godaddy.com is allowed to create certificates
|
| A | Good: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates
|
| A | Good: CAA entries found, creating certificate is limited: sectigo.com is allowed to create certificates
|
| 4. Content- and Performance-critical Checks |
| http://pinkpurplehome.quickconnect.to/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| A | Good: No https + http status 200 with inline CSS / JavaScript found
|
| A | Good: Every https result with status 200 has a minified Html-Content with a quota lower then 110 %.
|
| https://125.228.116.235/ 125.228.116.235
|
| 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://125.228.116.235/ 125.228.116.235
|
| 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.
|
| http://pinkpurplehome.quickconnect.to/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 3 script elements without defer/async.
|
| A | Good: All CSS / JavaScript files are sent compressed (gzip, deflate, br checked). That reduces the content of the files. 3 external CSS / JavaScript files found
|
| 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. 3 images (type image/png, image/jpg, image/jpeg, image/webp, image/gif) found without additional Compression. Not required because these images are already compressed
|
| A | Good: All CSS / JavaScript files are sent with a long Cache-Control header (minimum 7 days). So the browser can re-use these files, no download is required. 4 external CSS / JavaScript files with long Cache-Control max-age found
|
| Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 31 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), 3 with Cache-Control long enough, 34 complete.
|
| A | Good: Some checked attribute values are enclosed in quotation marks (" or ').: 46 Html-Elements checked, 26 without problems.
|
| I | Wrong: Attribute values found, not enclosed in quotation marks (" or ').: 20 Html-Elements with attributes and missing enclosed quotation marks found. 50 wrong attributes.
|
| 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.: 12 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 | Info: Different Server-Headers found
|
| A | Duration: 540506 milliseconds, 540.506 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)