Results for jami.net
jami.net uses HTTPS by default.
Chromium reports the following:
|Certificate||valid and trusted||The connection to this site is using a valid, trusted server certificate issued by Go Daddy Secure Certificate Authority - G2.|
|Connection||secure connection settings||The connection to this site is encrypted and authenticated using TLS 1.2, ECDHE_RSA with X25519, 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:
HSTS policy for https://jami.net:
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 set to
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:
|X-Content-Type-Options||X-Content-Type-Options header not implemented|
|X-Frame-Options||SAMEORIGIN||X-Frame-Options (XFO) header set to SAMEORIGIN or DENY|
|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.
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.
5 requests (5 secure, 0 insecure) to 3 unique hosts.
A third-party request is a request to a domain that's not
jami.net or one of its subdomains.
We use Disconnect's open source list of trackers to classify hosts.
The server jami.net (188.8.131.52) appears to have been located in Canada during our test.
See more information (e.g., provider) about this IP address using KeyCDN's tool.
|date||Thu, 20 Feb 2020 15:57:33 GMT|
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.