Results for cryptix.net

Check again 2020-04-09 21:00:18 Etc/UTC

HTTPS by default

cryptix.net uses HTTPS by default.

Chromium reports the following:

State Title Summary Description
Certificate valid and trusted The connection to this site is using a valid, trusted server certificate issued by Let's Encrypt Authority X3.
Connection secure connection settings The connection to this site is encrypted and authenticated using TLS 1.2, ECDHE_RSA with P-256, and AES_256_GCM.
Resources all served securely All resources on this page are served securely.

More information about the site's TLS/SSL configuration:

HTTP Strict Transport Security (HSTS)

HSTS policy for https://cryptix.net:
max-age=3

Pass Test
max-age set to at least 6 months
includeSubDomains — policy also applies to subdomains
preload — requests inclusion in preload lists

Content Security Policy

Content Security Policy (CSP) header not implemented.

The Content Security Policy tests are based on the ones from the Mozilla HTTP Observatory scanner/grader project (Mozilla Public License 2.0) by April King, reimplemented by us for Webbkoll. The explanatory texts are from the Observatory by Mozilla website, CC-BY-SA 3.0. Any mistake or inaccuracy in the results is our fault.

Referrer Policy

Referrer Policy not set. This means that the default value no-referrer-when-downgrade, leaking referrers in many situations, is used.

Subresource Integrity (SRI)

Subresource Integrity (SRI) not implemented, and external resources are loaded over HTTP or use protocol-relative URLs via src="//...".

The following third-party resources are not loaded using SRI:

Type URL
script https://www.google.com/recaptcha/api.js?render=6LdFkIEUAAAAAMp5COodnm3lvkLgbu9rQJwHTaXe&ver=3.0
script //stats.cryptix.de/piwik.js
script https://www.gstatic.com/recaptcha/releases/OOKISvkNnVD_m_9dreR_1S0n/recaptcha__en.js

The Subresource Integrity test is based on the one from the Mozilla HTTP Observatory scanner/grader project (Mozilla Public License 2.0) by April King, reimplemented by us for Webbkoll.

HTTP headers

Pass Header Value Result
X-Content-Type-Options X-Content-Type-Options header not implemented
X-Frame-Options X-Frame-Options (XFO) header not implemented
X-XSS-Protection X-XSS-Protection header not implemented

The header tests are based on the ones from the Mozilla HTTP Observatory scanner/grader project (Mozilla Public License 2.0) by April King, reimplemented by us for Webbkoll. The explanatory texts are from the Observatory by Mozilla website, CC-BY-SA 3.0.

Cookies

First-party cookies (2)

Domain Name Value Expires on HttpOnly Secure SameSite
cryptix.net _pk_id.2.2f9e 5ca3995e1a32158d.158... 2021-05-07 21:00:08Z (Lax)
cryptix.net _pk_ses.2.2f9e 1 2020-04-09 21:30:07Z (Lax)

Third-party cookies (1)

Domain Name Value Expires on HttpOnly Secure SameSite
.google.com NID 202=uOl24ym2m5D8_d4s... 2020-10-09 21:00:09Z (None)

HttpOnly means that the cookie can only be read by the server, and not by JavaScript on the client. This can mitigate XSS (cross-site scripting) attacks.

Secure means that the cookie will only be sent over a secure channel (HTTPS). This can mitigate MITM (man-in-the-middle) attacks.

SameSite can be used to instruct the browser to only send the cookie when the request is originating from the same site. This can mitigate CSRF (cross-site request forgery) attacks.

GDPR: Rec. 60, Rec. 61, Rec. 69, Rec. 70, Rec. 75, Rec. 78, Art. 5.1.a, Art. 5.1.c, Art. 5.1.e, Art. 21, Art. 22, Art. 32.

e-PD (2002/58/EC). Rec. 24, 25, Art. 5.2.

e-PD revised (2009/136/EC). Rec. 65, 66.

More information

localStorage

localStorage not used.

Third-party requests

14 requests (14 secure, 0 insecure) to 5 unique hosts.

A third-party request is a request to a domain that's not cryptix.net or one of its subdomains.

Host IP Country Classification URLs
fonts.gstatic.com 216.58.206.227 US Content (Google) Show (2)
stats.cryptix.de 83.137.101.114 DE Show (2)
www.cryptix.de 83.137.101.114 DE Show (1)
www.google.com 216.58.213.132 US Content (Google) Show (5)
www.gstatic.com 216.58.201.227 US Content (Google) Show (4)

We use Disconnect's open source list of trackers to classify hosts.

GDPR: Rec. 69, Rec. 70, Art. 5.1.b-c, Art. 25.

Server location

The server cryptix.net (83.137.101.114) appears to have been located in Germany during our test.

See more information (e.g., provider) about this IP address using KeyCDN's tool.

Raw headers

Header Value
connection Keep-Alive
content-encoding gzip
content-length 4444
content-type text/html; charset=UTF-8
date Thu, 09 Apr 2020 21:00:06 GMT
keep-alive timeout=5, max=100
link <https://cryptix.net/wp-json/>; rel="https://api.w.org/" <https://cryptix.net/>; rel=shortlink
server Apache/2.4.10 (Debian)
strict-transport-security max-age=3
vary Accept-Encoding

What this tool checks (and doesn't check)

This tool attempts to simulate what happens when a user visits a specified page with a typical browser. The browser has no addons/extensions installed, and Do Not Track (DNT) is not enabled, since this is the default setting in most browsers.

External files such as images, scripts and CSS are loaded, but the tool performs no interactions with the page — no links are clicked, no forms are submitted.

Disclaimer: The results presented here might not be 100% correct. Bugs happen. This tool is meant to be used by site owners as a starting point for improvements, not as a rigorous analysis.

Text about HTTPS partly adapted from the CIO Council's The HTTPS-Only Standard (public domain). MaxMind's GeoLite2 country database (CC-BY-SA 4.0) is used for GeoIP lookups. See here for more information.