| 1. General Results, most used to calculate the result |
A | name "crypto.linkpc.net" is subdomain, public suffix is ".net", top-level-domain is ".net", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .net-domains preloaded: 9994 (complete: 263653)
|
A | Good: All ip addresses are public addresses
|
A | Good: Minimal 2 ip addresses per domain name found: crypto.linkpc.net has 2 different ip addresses (authoritative).
|
A | Good: Minimal 2 ip addresses per domain name found: www.crypto.linkpc.net has 2 different ip addresses (authoritative).
|
A | Good: Ipv4 and Ipv6 addresses per domain name found: crypto.linkpc.net has 1 ipv4, 1 ipv6 addresses
|
A | Good: Ipv4 and Ipv6 addresses per domain name found: www.crypto.linkpc.net has 1 ipv4, 1 ipv6 addresses
|
A | Good: No asked Authoritative Name Server had a timeout
|
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.
|
B | https://crypto.linkpc.net/ 2a02:842b:8c15:9000:7d78:5337:80ee:2802
|
| Missing HSTS-Header
|
B | https://www.crypto.linkpc.net/ 2a02:842b:8c15:9000:7d78:5337:80ee:2802
|
| Missing HSTS-Header
|
C | Error - no preferred version www or non-www. Select one version as preferred version, then add a redirect https + not-preferred version to https + preferred version. Perhaps in your port 443 vHost something like "RewriteEngine on" + "RewriteCond %{SERVER_NAME} = example.com" + "ReWriteRule ^ https://www.example.com%{REQUEST_URI} [END,QSA,R=permanent]" (three rows, without the "). That should create a redirect https + example.com ⇒ https + www.example.com. Or switch both values to use the non-www version as your preferred version.
|
C | Error - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
|
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 | https://crypto.linkpc.net/ 2a02:842b:8c15:9000:7d78:5337:80ee:2802
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
|
I | https://www.crypto.linkpc.net/ 2a02:842b:8c15:9000:7d78:5337:80ee:2802
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
|
K | http://crypto.linkpc.net/ 77.141.38.249, Status -14
| http://crypto.linkpc.net/ 2a02:842b:8c15:9000:7d78:5337:80ee:2802, Status 200
| Configuration problem - different ip addresses with different status
|
K | http://www.crypto.linkpc.net/ 77.141.38.249, Status -14
| http://www.crypto.linkpc.net/ 2a02:842b:8c15:9000:7d78:5337:80ee:2802, Status 200
| Configuration problem - different ip addresses with different status
|
K | https://crypto.linkpc.net/ 77.141.38.249, Status -14
| https://crypto.linkpc.net/ 2a02:842b:8c15:9000:7d78:5337:80ee:2802, Status 200
| Configuration problem - different ip addresses with different status
|
K | http://crypto.linkpc.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.141.38.249, Status -14
| http://crypto.linkpc.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:842b:8c15:9000:7d78:5337:80ee:2802, Status 404
| Configuration problem - different ip addresses with different status
|
K | http://www.crypto.linkpc.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.141.38.249, Status -14
| http://www.crypto.linkpc.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:842b:8c15:9000:7d78:5337:80ee:2802, Status 404
| Configuration problem - different ip addresses with different status
|
K | https://www.crypto.linkpc.net/ 77.141.38.249, Status -14
| https://www.crypto.linkpc.net/ 2a02:842b:8c15:9000:7d78:5337:80ee:2802, Status 200
| Configuration problem - different ip addresses with different status
|
N | https://[2a02:842b:8c15:9000:7d78:5337:80ee:2802]/ 2a02:842b:8c15:9000:7d78:5337:80ee:2802
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
O | crypto.linkpc.net / 2a02:842b:8c15:9000:7d78:5337:80ee:2802 / 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.crypto.linkpc.net / 2a02:842b:8c15:9000:7d78:5337:80ee:2802 / 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
|
X | Fatal error: Nameserver doesn't support TCP connection: ns12.dnsexit.com / 162.244.82.74: ServerFailure
|
X | Fatal error: Nameserver doesn't support TCP connection: ns13.dnsexit.com / 104.223.143.26: Timeout
|
| Fatal: More then one ip address per domain name found, but checking all ip addresses different http status found.: Domain crypto.linkpc.net, 2 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.crypto.linkpc.net, 2 ip addresses, 2 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.crypto.linkpc.net
|
| 2. Header-Checks |
F | crypto.linkpc.net 2a02:842b:8c15:9000:7d78:5337:80ee:2802
| Content-Security-Policy
| Critical: Missing Header:
|
F | crypto.linkpc.net 2a02:842b:8c15:9000:7d78:5337:80ee:2802
| X-Content-Type-Options
| Critical: Missing Header:
|
F | crypto.linkpc.net 2a02:842b:8c15:9000:7d78:5337:80ee:2802
| Referrer-Policy
| Critical: Missing Header:
|
F | crypto.linkpc.net 2a02:842b:8c15:9000:7d78:5337:80ee:2802
| Permissions-Policy
| Critical: Missing Header:
|
B | crypto.linkpc.net 2a02:842b:8c15:9000:7d78:5337:80ee:2802
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
B | crypto.linkpc.net 2a02:842b:8c15:9000:7d78:5337:80ee:2802
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
B | crypto.linkpc.net 2a02:842b:8c15:9000:7d78:5337:80ee:2802
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
F | www.crypto.linkpc.net 2a02:842b:8c15:9000:7d78:5337:80ee:2802
| Content-Security-Policy
| Critical: Missing Header:
|
F | www.crypto.linkpc.net 2a02:842b:8c15:9000:7d78:5337:80ee:2802
| X-Content-Type-Options
| Critical: Missing Header:
|
F | www.crypto.linkpc.net 2a02:842b:8c15:9000:7d78:5337:80ee:2802
| Referrer-Policy
| Critical: Missing Header:
|
F | www.crypto.linkpc.net 2a02:842b:8c15:9000:7d78:5337:80ee:2802
| Permissions-Policy
| Critical: Missing Header:
|
B | www.crypto.linkpc.net 2a02:842b:8c15:9000:7d78:5337:80ee:2802
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
B | www.crypto.linkpc.net 2a02:842b:8c15:9000:7d78:5337:80ee:2802
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
B | www.crypto.linkpc.net 2a02:842b:8c15:9000:7d78:5337:80ee:2802
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| 3. DNS- and NameServer - Checks |
A | Info:: 11 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
|
A | Info:: 11 Queries complete, 5 with IPv6, 6 with IPv4.
|
| Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses.
|
A | Good: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns1.dnsexit.com (89.39.149.107), ns1.dnsexit.com (89.39.149.107)
|
A | Good (1 - 3.0):: An average of 2.8 queries per domain name server required to find all ip addresses of all name servers.
|
A | Info:: 4 different Name Servers found: ns1.dnsexit.com, ns10.dnsexit.com, ns11.dnsexit.com, ns12.dnsexit.com, 3 Name Servers included in Delegation: ns10.dnsexit.com, ns11.dnsexit.com, ns12.dnsexit.com, 4 Name Servers included in 3 Zone definitions: ns1.dnsexit.com, ns2.dnsexit.com, ns3.dnsexit.com, ns4.dnsexit.com, ns10.dnsexit.com, ns11.dnsexit.com, ns12.dnsexit.com, 1 Name Servers listed in SOA.Primary: ns1.dnsexit.com.
|
A | Good: Only one SOA.Primary Name Server found.: ns1.dnsexit.com.
|
| Error: SOA.Primary Name Server not included in the delegation set.: ns1.dnsexit.com.
|
X | Fatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns1.dnsexit.com (89.39.149.107): Delegation: ns10.dnsexit.com, ns11.dnsexit.com, ns12.dnsexit.com, Zone: ns1.dnsexit.com, ns2.dnsexit.com, ns3.dnsexit.com, ns4.dnsexit.com. Name Servers defined in Delegation, missing in Zone: ns10.dnsexit.com, ns11.dnsexit.com, ns12.dnsexit.com.Name Servers defined in Zone, missing in Delegation: ns1.dnsexit.com, ns2.dnsexit.com, ns3.dnsexit.com, ns4.dnsexit.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: 4 different Name Servers found
|
| Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 4 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.: 4 Name Servers, 1 Top Level Domain: com
|
| 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: dnsexit.com
|
A | Good: Name servers with different Country locations found: 4 Name Servers, 2 Countries: RO, US
|
A | Info: Ipv4-Subnet-list: 4 Name Servers, 4 different subnets (first Byte): 162., 63., 69., 89., 4 different subnets (first two Bytes): 162.244., 63.141., 69.30., 89.39., 4 different subnets (first three Bytes): 162.244.82., 63.141.249., 69.30.249., 89.39.149.
|
A | Excellent: Every Name Server IPv4-address starts with an unique Byte.
|
A | Good: Nameserver supports Echo Capitalization: 4 good Nameserver
|
X | Nameserver Timeout checking Echo Capitalization: ns13.dnsexit.com / 104.223.143.26
|
A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
|
X | Nameserver Timeout checking EDNS512: ns13.dnsexit.com / 104.223.143.26
|
A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 3 good Nameserver
|
| Nameserver doesn't pass all EDNS-Checks: ns1.dnsexit.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.
|
| Nameserver doesn't pass all EDNS-Checks: ns12.dnsexit.com / 162.244.82.74: 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 expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns12.dnsexit.com / 162.244.82.74: 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 expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns13.dnsexit.com / 104.223.143.26: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
|
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 |
| http://crypto.linkpc.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.141.38.249
|
| 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://www.crypto.linkpc.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.141.38.249
|
| 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://crypto.linkpc.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:842b:8c15:9000:7d78:5337:80ee:2802, Status 404
| http://crypto.linkpc.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.141.38.249, Status -14
| 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://www.crypto.linkpc.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:842b:8c15:9000:7d78:5337:80ee:2802, Status 404
| http://www.crypto.linkpc.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.141.38.249, Status -14
| 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://crypto.linkpc.net/ 2a02:842b:8c15:9000:7d78:5337:80ee:2802
|
| Warning: https result with status 200 and size greater then 1024 Bytes without Compression found. Add Compression support (gzip, deflate, br - these are checked) so the html content is compressed.
|
| https://www.crypto.linkpc.net/ 2a02:842b:8c15:9000:7d78:5337:80ee:2802
|
| 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://crypto.linkpc.net/ 2a02:842b:8c15:9000:7d78:5337:80ee:2802
|
| 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.crypto.linkpc.net/ 2a02:842b:8c15:9000:7d78:5337:80ee:2802
|
| 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://[2a02:842b:8c15:9000:7d78:5337:80ee:2802]/ 2a02:842b:8c15:9000:7d78:5337:80ee:2802
|
| 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://crypto.linkpc.net/ 2a02:842b:8c15:9000:7d78:5337:80ee:2802
|
| 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.crypto.linkpc.net/ 2a02:842b:8c15:9000:7d78:5337:80ee:2802
|
| 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://[2a02:842b:8c15:9000:7d78:5337:80ee:2802]/ 2a02:842b:8c15:9000:7d78:5337:80ee:2802
|
| 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://crypto.linkpc.net/ 2a02:842b:8c15:9000:7d78:5337:80ee:2802
|
| Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
|
| https://www.crypto.linkpc.net/ 2a02:842b:8c15:9000:7d78:5337:80ee:2802
|
| 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://[2a02:842b:8c15:9000:7d78:5337:80ee:2802]/ 2a02:842b:8c15:9000:7d78:5337:80ee:2802
|
| 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: All checked attribute values are enclosed in quotation marks (" or ').
|
A | Info: No img element found, no alt attribute checked
|
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: 461220 milliseconds, 461.220 seconds
|