https://runbox.com/

Title: "Secure and Private Email Hosting Services by Runbox"
Description: "Secure and sustainable email services provided by email professionals. Powerful Email, Domain, and Web Hosting for businesses."
Third-party domains
0
 
Persistent cookies
0
 
Session cookies
0
 

Third-party domains is the count of organisations allowed by the webmaster to trace your across the site. These cookies may be set for various purposes, like tracking ads displayed on the website, collection of statistics, targeted advertising etc. This website allows 0 other websites to track your activity.

Persistent cookies are the cookies that are preserved through browser shutdowns. This means, even if you close this page today and ever return there in future, the website will know you're a returning visitor. This may be used for "remember me" features, as well as persistent user tracking. These cookies, especially if set by third party organisations, are powerful tool for monitoring your activities across all the websites you visit. This website sets 0 persistent cookies with average life-time of 0 days and longest 0 days.

Session cookies are cleared when you close your browser and allow the website to identify user's state — such as logged-in users. They are mostly considered harmless because they cannot be used for long-term user tracking. This site sets 0 session cookies.


Last fetched: 2017-01-21T05:29:34.185187+00:00

HTTP status: 200 200


TLS/SSL configuration report

TLS score
F
Grade capped at F
Certificate path cannot be verified to a known root certificate

See full SSL/TLS security report for runbox.com

HTTP security-related headers assessment

Security score
10

Security-related HTTP headers

  • X-XSS-Protection: 1; mode=block

    Controls an Cross-Site Scripting (XSS) filters built into the majority of web browsers. The filter is usually turned on by default anyway, but requirement to set the header to 1 became part of canonical set of "secure" HTTP headers. Over time, vulnerabilities in the "sanitizing" mode filter were found, so 1; mode=block became the recommended value. Some companies decided that they don't really need a browser-side XSS filter to mess with their web services which are XSS-free anyway and they became consciously disabling the XSS filter by setting the header to 0.

  • X-Frame-Options: SAMEORIGIN

    Instructs the browser if the current website can be embedded in HTML frame by another website. Since this allows the parent website to control the framed page, this creates a potential for data theft attacks ("clickjacking") and most sensitive websites won't allow them to be framed at all (deny) or just allow parts of them to be embedded in frames created by themselves only (samesite).

  • Public-Key-Pins: pin-sha256="MrS38g9Vc8IlJ3yYbku1CSe0I3MtCsjklrzd3/rj3NE="; pin-sha256="PRz8fQoHBy5mehFMYojuAVwFslhltxr1YBvk9yCXEj4="; pin-sha256="gWfGtuosAF8JPYbdDcko6bRm0546YaVVKhLPYUDFXwo="; max-age=2592000

    Announces a list of X.509 certificate hashes that are allowed to appear in the website's TLS certification path (HTTP Public Key Pinning or HPKP). This prevents malicious proxy servers from transparently replacing the public certificates with their own and wiretapping the TLS connection of the unsuspecting user. This header sets HPKP in enforcement mode.

  • Content-Security-Policy: script-src https://runbox.com https://support.runbox.com/ https://www.google.com/ 'unsafe-inline' 'unsafe-eval'; object-src https://runbox.com; img-src 'self' https://* http://*; media-src 'self'; child-src https://runbox.com; font-src 'self'; connect-src 'self'; style-src 'self' 'unsafe-inline'

    Content Security Policy is used by a web server to declare a list of trusted content types (images, scripts, media etc) and origins from which they can be safely loaded as intended by the website authors. The Content-Security-Policy-Report-Only header instruct the browser to enable CSP in enforcement mode.

  • Strict-Transport-Security: max-age=63072000; preload

    HTTP Strict Transport Security (HSTS) is an opt-in security enhancement that is specified by a web application through the use of a special response header.

  • Server: nginx

    Announces web server software and optionally version details.

  • X-Content-Type-Options: nosniff

    A non-standard but widely accepted header introduced originally by Microsoft to disable "content sniffing" or heuristic content type discovery in absence or mismatch of a proper HTTP Content-Type declaration, which led to a number of web attacks. In general, presence of the header with its only defined value of nosniff is considered as part of a properly secured HTTP response.

Fully automated RESTful API is now available. Subscribe for your free trial today!