Results for mailbox.org
mailbox.org 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 SwissSign Server Silver CA 2014 - G22.|
|Connection||secure connection settings||The connection to this site is encrypted and authenticated using TLS 1.2, ECDHE_RSA with P-384, and CHACHA20_POLY1305.|
|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://mailbox.org:
max-age=15768000; includeSubDomains; preload
Content Security Policy set in HTTP header:
default-src 'self' data: ; img-src 'self' https://piwik.mailbox.org; script-src 'self' 'unsafe-inline' https://piwik.mailbox.org ; style-src 'self' data: 'unsafe-inline' ; frame-src 'self' https://verwaltung.mailbox.org https://manage.mailbox.org https://status.mailbox.org; frame-ancestors 'self';
Content Security Policy (CSP) implemented unsafely. This includes
script-src, overly broad sources such as
script-src, or not restricting the sources for
Clickjacking protection, using
The use of CSP's
Deny by default, using
Denying by default using
Restricts use of the
Blocks loading of active content over HTTP or FTP
Blocks loading of passive content over HTTP or FTP
This site's Content Security Policy allows the loading of passive content such as images or videos over insecure protocols such as HTTP or FTP. Consider changing them to load them over HTTPS.
Blocks inline styles by not allowing
Blocking inline styles can help prevent attackers from modifying the contents or appearance of your page. Moving styles to external stylesheets can also help make your site more maintainable.
Blocks execution of plug-ins, using
Blocking the execution of plug-ins via
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
no-referrer-when-downgrade, strict-origin-when-cross-origin in
Referrer-Policy HTTP header.
|X-Content-Type-Options||nosniff||X-Content-Type-Options header set to "nosniff"|
|X-Frame-Options||SAMEORIGIN||X-Frame-Options (XFO) implemented via the CSP frame-ancestors directive|
|X-XSS-Protection||1; mode=block||X-XSS-Protection header set to "1; mode=block"|
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.
localStorage not used.
No third-party requests.
A third-party request is a request to a domain that's not
mailbox.org or one of its subdomains.
The server mailbox.org (184.108.40.206) appears to have been located in Germany during our test.
See more information (e.g., provider) about this IP address using KeyCDN's tool.
|cache-control||must-revalidate, no-cache, private max-age=300|
|content-security-policy||default-src 'self' data: ; img-src 'self' https://piwik.mailbox.org; script-src 'self' 'unsafe-inline' https://piwik.mailbox.org ; style-src 'self' data: 'unsafe-inline' ; frame-src 'self' https://verwaltung.mailbox.org https://manage.mailbox.org https://status.mailbox.org; frame-ancestors 'self';|
|date||Mon, 20 May 2019 10:58:59 GMT|
|expires||Mon, 20 May 2019 11:03:58 GMT|
|feature-policy||accelerometer 'none'; camera 'none'; gyroscope 'none'; magnetometer 'none'; microphone 'none'; usb 'none';|
|strict-transport-security||max-age=15768000; includeSubDomains; preload|
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.