Results for mail.de

Check again 2018-12-16 14:03:18 Etc/UTC

HTTPS by default

mail.de 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 DigiCert SHA2 Extended Validation Server CA.
Connection secure connection settings The connection to this site is encrypted and authenticated using TLS 1.3, 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:

HTTP Strict Transport Security (HSTS)

HSTS policy for https://mail.de:
max-age=31536000; includeSubDomains; preload

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 set in HTTP header: default-src * 'self' data: 'unsafe-inline' 'unsafe-eval'

Content Security Policy (CSP) implemented unsafely. This includes 'unsafe-inline' or data: inside script-src, overly broad sources such as https: inside object-src or script-src, or not restricting the sources for object-src or script-src.

Pass Test Info
Clickjacking protection, using frame-ancestors

The use of CSP's frame-ancestors directive offers fine-grained control over who can frame your site.

Show
Deny by default, using default-src 'none'

Denying by default using default-src 'none' can ensure that your Content Security Policy doesn't allow the loading of resources you didn't intend to allow.

Show
Restricts use of the <base> tag by using base-uri 'none', base-uri 'self', or specific origins

The base tag can be used to trick your site into loading scripts from untrusted origins.

Show
Restricts where <form> contents may be submitted by using form-action 'none', form-action 'self', or specific URIs

Malicious JavaScript or content injection could modify where sensitive form data is submitted to or create additional forms for data exfiltration.

Show
Blocks loading of active content over HTTP or FTP

Loading JavaScript or plugins can allow a man-in-the-middle to execute arbitrary code on your website. Restricting your policy and changing links to HTTPS can help prevent this.

Show
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.

Show
Uses CSP3's 'strict-dynamic' directive to allow dynamic script loading (optional)

'strict-dynamic' lets you use a JavaScript shim loader to load all your site's JavaScript dynamically, without having to track script-src origins.

Show
Blocks execution of JavaScript's eval() function by not allowing 'unsafe-eval' inside script-src

Blocking the use of JavaScript's eval() function can help prevent the execution of untrusted code.

Show
Blocks execution of inline JavaScript by not allowing 'unsafe-inline' inside script-src

Blocking the execution of inline JavaScript provides CSP's strongest protection against cross-site scripting attacks. Moving JavaScript to external files can also help make your site more maintainable.

Show
Blocks inline styles by not allowing 'unsafe-inline' inside style-src

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.

Show
Blocks execution of plug-ins, using object-src restrictions

Blocking the execution of plug-ins via object-src 'none' or as inherited from default-src can prevent attackers from loading Flash or Java in the context of your page.

Show

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 set to no-referrer in meta element.

Subresource Integrity (SRI)

Subresource Integrity (SRI) not implemented, but all external resources are loaded over HTTPS

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

Type URL
script https://www.googleadservices.com/pagead/conversion.js
script https://googleads.g.doubleclick.net/pagead/viewthroughconversion/970467430/?random=1544968996319&cv=...
script https://www.google-analytics.com/analytics.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 nosniff X-Content-Type-Options header set to "nosniff"
X-Frame-Options SAMEORIGIN X-Frame-Options (XFO) header set to SAMEORIGIN or DENY
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.

Cookies

First-party cookies (3)

Domain Name Value Expires on HttpOnly Secure SameSite
.mail.de _gid GA1.2.2058521142.154... 2018-12-17 14:03:15Z
.mail.de _gat 1 2018-12-16 14:04:15Z
.mail.de _ga GA1.2.2113346395.154... 2020-12-15 14:03:15Z

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

3 requests (3 secure, 0 insecure) to 2 unique hosts.

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

Host IP Country Classification URLs
www.google-analytics.com 216.58.198.206 US Disconnect (Google) Show (2)
www.googleadservices.com 172.217.22.130 US Disconnect (Google) Show (1)

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 mail.de (62.201.172.8) 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
content-encoding gzip
content-length 7768
content-security-policy default-src * 'self' data: 'unsafe-inline' 'unsafe-eval'
content-type text/html; charset=UTF-8
date Sun, 16 Dec 2018 14:03:15 GMT
server nginx
set-cookie ac=; domain=.mail.de; path=/; expires=Sunday, 16-Dec-2018 05:03:15 CET; Secure; HttpOnly cc=; domain=.mail.de; path=/; expires=Sunday, 16-Dec-2018 05:03:15 CET; Secure; HttpOnly dc=; domain=.mail.de; path=/; expires=Sunday, 16-Dec-2018 05:03:15 CET; Secure; HttpOnly tt=; domain=.mail.de; path=/; expires=Sunday, 16-Dec-2018 05:03:15 CET; Secure; HttpOnly
status 200
strict-transport-security max-age=31536000; includeSubDomains; preload
vary Accept-Encoding
x-content-security-policy default-src * 'self' data: 'unsafe-inline' 'unsafe-eval'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
x-webkit-csp default-src * 'self' data: 'unsafe-inline' 'unsafe-eval'
x-xss-protection 1; mode=block

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.