| 1. General Results, most used to calculate the result |
| A | name "cloud-ip.cc" is domain, public suffix is ".cc", top-level-domain is ".cc", top-level-domain-type is "country-code", Country is Cocos (Keeling) Islands (the), tld-manager is "eNIC Cocos (Keeling) Islands Pty.
Ltd. d/b/a Island Internet Services", num .cc-domains preloaded: 871 (complete: 276475)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: cloud-ip.cc has 4 different ip addresses (authoritative).
|
| A | Good: Minimal 2 ip addresses per domain name found: www.cloud-ip.cc has 4 different ip addresses (authoritative).
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: cloud-ip.cc has 2 ipv4, 2 ipv6 addresses
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: www.cloud-ip.cc has 2 ipv4, 2 ipv6 addresses
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | https://www.cloud-ip.cc/ 46.166.184.116
| https://www.cloudns.net/dynamic-dns/
| Correct redirect https to https
|
| A | https://www.cloud-ip.cc/ 185.206.180.131
| https://www.cloudns.net/dynamic-dns/
| Correct redirect https to https
|
| A | https://www.cloud-ip.cc/ 2a00:1768:2001:63::46:116
| https://www.cloudns.net/dynamic-dns/
| Correct redirect https to https
|
| A | https://www.cloud-ip.cc/ 2a0b:1640:1:1:1:1:7ab2:6611
| https://www.cloudns.net/dynamic-dns/
| Correct redirect https to https
|
| A | https://185.206.180.131/ 185.206.180.131
| https://185.206.180.131/index.html
| Correct redirect https to https
|
| 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.
|
| A | Good: every cookie sent via https is marked as secure
|
| A | Good: Every cookie has a SameSite Attribute with a correct value Strict/Lax/None
|
| 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):4 complete Content-Type - header (5 urls)
|
| https://185.206.180.131/index.html
|
| Url with incomplete Content-Type - header - missing charset
|
| B | https://cloud-ip.cc/ 46.166.184.116
|
| Missing HSTS-Header
|
| B | https://cloud-ip.cc/ 185.206.180.131
|
| Missing HSTS-Header
|
| B | https://cloud-ip.cc/ 2a00:1768:2001:63::46:116
|
| Missing HSTS-Header
|
| B | https://cloud-ip.cc/ 2a0b:1640:1:1:1:1:7ab2:6611
|
| Missing HSTS-Header
|
| B | https://www.cloud-ip.cc/ 46.166.184.116
|
| Missing HSTS-Header
|
| B | https://www.cloud-ip.cc/ 185.206.180.131
|
| Missing HSTS-Header
|
| B | https://www.cloud-ip.cc/ 2a00:1768:2001:63::46:116
|
| Missing HSTS-Header
|
| B | https://www.cloud-ip.cc/ 2a0b:1640:1:1:1:1:7ab2:6611
|
| Missing HSTS-Header
|
| D | http://cloud-ip.cc/ 185.206.180.131
| http://cloud-ip.cc/index.html
| 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.cloud-ip.cc/ 185.206.180.131
| http://www.cloud-ip.cc/index.html
| 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://cloud-ip.cc/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.206.180.131
| http://cloud-ip.cc/index.html
| 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.cloud-ip.cc/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.206.180.131
| http://www.cloud-ip.cc/index.html
| 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://cloud-ip.cc/index.html
| https://www.cloud-ip.cc/
| 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.
|
| E | http://cloud-ip.cc/ 46.166.184.116
| https://www.cloud-ip.cc/
| 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.
|
| E | http://cloud-ip.cc/ 2a00:1768:2001:63::46:116
| https://www.cloud-ip.cc/
| 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.
|
| E | http://cloud-ip.cc/ 2a0b:1640:1:1:1:1:7ab2:6611
| https://www.cloud-ip.cc/
| 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.
|
| E | http://www.cloud-ip.cc/index.html
| https://www.cloudns.net/dynamic-dns/
| 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.
|
| E | http://www.cloud-ip.cc/ 46.166.184.116
| https://www.cloudns.net/dynamic-dns/
| 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.
|
| E | http://www.cloud-ip.cc/ 2a00:1768:2001:63::46:116
| https://www.cloudns.net/dynamic-dns/
| 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.
|
| E | http://www.cloud-ip.cc/ 2a0b:1640:1:1:1:1:7ab2:6611
| https://www.cloudns.net/dynamic-dns/
| 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 | https://www.cloudns.net/dynamic-dns/
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
|
| K | http://cloud-ip.cc/ 185.206.180.131, Status 302
| http://cloud-ip.cc/ 46.166.184.116, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://cloud-ip.cc/ 185.206.180.131, Status 302
| http://cloud-ip.cc/ 2a00:1768:2001:63::46:116, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://cloud-ip.cc/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.206.180.131, Status 302
| http://cloud-ip.cc/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a00:1768:2001:63::46:116, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://cloud-ip.cc/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.206.180.131, Status 302
| http://cloud-ip.cc/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a0b:1640:1:1:1:1:7ab2:6611, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://cloud-ip.cc/ 185.206.180.131, Status 302
| http://cloud-ip.cc/ 2a0b:1640:1:1:1:1:7ab2:6611, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://cloud-ip.cc/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.206.180.131, Status 302
| http://cloud-ip.cc/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 46.166.184.116, Status 301
| Configuration problem - different ip addresses with different status
|
| N | https://185.206.180.131/ 185.206.180.131
| https://185.206.180.131/index.html
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://46.166.184.116/ 46.166.184.116
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://[2a00:1768:2001:0063:0000:0000:0046:0116]/ 2a00:1768:2001:63::46:116
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://[2a0b:1640:0001:0001:0001:0001:7ab2:6611]/ 2a0b:1640:1:1:1:1:7ab2:6611
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| Fatal: More then one ip address per domain name found, but checking all ip addresses different http status found.: Domain cloud-ip.cc, 4 ip addresses, 2 different http results.
|
| Fatal: More then one ip address per domain name found, but checking all ip addresses different http status found.: Domain www.cloud-ip.cc, 4 ip addresses, 2 different http results.
|
| Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain cloud-ip.cc, 4 ip addresses.
|
| Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain www.cloud-ip.cc, 4 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.cloud-ip.cc
|
| 2. Header-Checks |
| A | www.cloudns.net
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
| A |
| X-Frame-Options
| Ok: Header without syntax errors found: SAMEORIGIN
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. SAMEORIGIN. Better solution: Use a Content-Security-Policy Header with a frame-ancestors directive. DENY - use 'none', SAMEORIGIN - use 'self'. If you want to allow some domains to frame your page, add these urls.
|
| A |
| X-Xss-Protection
| Ok: Header without syntax errors found: 1; mode=block
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. 1; mode=block
|
| F | www.cloudns.net
| Content-Security-Policy
| Critical: Missing Header:
|
| F | www.cloudns.net
| Referrer-Policy
| Critical: Missing Header:
|
| F | www.cloudns.net
| Permissions-Policy
| Critical: Missing Header:
|
| B | www.cloudns.net
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | www.cloudns.net
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | www.cloudns.net
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 21 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
|
| A | Info:: 21 Queries complete, 21 with IPv6, 0 with IPv4.
|
| A | Good: All DNS Queries done via IPv6.
|
| Ok (4 - 8):: An average of 5.3 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 4 different Name Servers found: ns71.cloudns.net, ns72.cloudns.com, ns73.cloudns.net, ns74.cloudns.uk, 4 Name Servers included in Delegation: ns71.cloudns.net, ns72.cloudns.com, ns73.cloudns.net, ns74.cloudns.uk, 4 Name Servers included in 1 Zone definitions: ns71.cloudns.net, ns72.cloudns.com, ns73.cloudns.net, ns74.cloudns.uk, 1 Name Servers listed in SOA.Primary: ns74.cloudns.uk.
|
| A | Good: Only one SOA.Primary Name Server found.: ns74.cloudns.uk.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns74.cloudns.uk.
|
| 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: ns71.cloudns.net, ns72.cloudns.com, ns73.cloudns.net, ns74.cloudns.uk
|
| 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, 3 Top Level Domains: uk, net, com
|
| A | Good: Name Servers with different domain names found.: 3 different Domains found
|
| A | Good: Name servers with different Country locations found: 4 Name Servers, 5 Countries: BG, DE, FR, NL, US
|
| A | Info: Ipv4-Subnet-list: 4 Name Servers, 4 different subnets (first Byte): 109., 178., 185., 51., 4 different subnets (first two Bytes): 109.201., 178.156., 185.206., 51.91., 4 different subnets (first three Bytes): 109.201.133., 178.156.179., 185.206.180., 51.91.57.
|
| A | Excellent: Every Name Server IPv4-address starts with an unique Byte.
|
| A | Info: IPv6-Subnet-list: 4 Name Servers with IPv6, 4 different subnets (first block): 2001:, 2a00:, 2a01:, 2a0b:, 4 different subnets (first two blocks): 2001:41d0:, 2a00:1768:, 2a01:04ff:, 2a0b:1640:, 4 different subnets (first three blocks): 2001:41d0:0305:, 2a00:1768:1001:, 2a01:04ff:00f0:, 2a0b:1640:0001:, 4 different subnets (first four blocks): 2001:41d0:0305:2100:, 2a00:1768:1001:0009:, 2a01:04ff:00f0:6e7b:, 2a0b:1640:0001:0001:
|
| A | Excellent: Every Name Server IPv6-address starts with an unique Hex-block
|
| A | Good: Nameserver supports TCP connections: 8 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 8 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
|
| Nameserver doesn't pass all EDNS-Checks: ns71.cloudns.net / 109.201.133.251: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns71.cloudns.net / 2a00:1768:1001:9::251: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns72.cloudns.com / 178.156.179.118: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: ok. COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns72.cloudns.com / 2a01:4ff:f0:6e7b::1: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns73.cloudns.net / 51.91.57.244: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns73.cloudns.net / 2001:41d0:305:2100::5961: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns74.cloudns.uk: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns74.cloudns.uk / 185.206.180.55: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns74.cloudns.uk / 2a0b:1640:1:1:1:1:1ce8:3446: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. 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 |
| Fatal: All checks of /.well-known/acme-challenge/random-filename have a redirect, destination doesn't have the random filename. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://cloud-ip.cc/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a00:1768:2001:63::46:116, Status 301
| http://cloud-ip.cc/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.206.180.131, Status 302
| 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.
|
| http://cloud-ip.cc/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a0b:1640:1:1:1:1:7ab2:6611, Status 301
| http://cloud-ip.cc/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.206.180.131, Status 302
| 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.
|
| A | Good: Every https result with status 200 and greater 1024 Bytes is compressed (gzip, deflate, br checked).
|
| https://www.cloudns.net/dynamic-dns/
|
| 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.cloudns.net/dynamic-dns/
|
| 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://46.166.184.116/ 46.166.184.116
|
| 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://[2a00:1768:2001:0063:0000:0000:0046:0116]/ 2a00:1768:2001:63::46:116
|
| 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://[2a0b:1640:0001:0001:0001:0001:7ab2:6611]/ 2a0b:1640:1:1:1:1:7ab2:6611
|
| 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://185.206.180.131/index.html
|
| 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://46.166.184.116/ 46.166.184.116
|
| 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://[2a00:1768:2001:0063:0000:0000:0046:0116]/ 2a00:1768:2001:63::46:116
|
| 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://[2a0b:1640:0001:0001:0001:0001:7ab2:6611]/ 2a0b:1640:1:1:1:1:7ab2:6611
|
| 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.
|
| A | Good: Some script Elements (type text/javascript) with a src-Attribute have a defer / async - Attribute. So loading and executing these JavaScripts doesn't block parsing and rendering the Html-Output.
|
| https://www.cloudns.net/dynamic-dns/
|
| 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. 13 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. 33 images (type image/png, image/jpg, image/jpeg, image/webp, image/gif) found without additional Compression. 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. 12 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 1 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 13 complete.
|
| Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 33 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, 33 complete.
|
| A | Good: All checked attribute values are enclosed in quotation marks (" or ').
|
| A | Good: Some img-elements have a valid alt-attribute.: 36 img-elements found, 14 img-elements with correct alt-attributes (defined, not an empty value).
|
| 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.: 22 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: 171350 milliseconds, 171.350 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)