Privacy Impact Score is a score reflecting overall cookie-related impact of
the website relative to other websites, primarily taking into account the number of third-party domains
it reports to and number of persistent cookies it sets. See
Privacy Impact Score
article for more details.

Third-party domains

18

Persistent cookies

41

Session cookies

2

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 18
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 41
persistent cookies with average life-time of 1471
days and longest 7848 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 2 session
cookies.

Last fetched: 2018-05-18T03:27:15.312728+00:00

HTTP status: 200 200
OK

Cookies and Privacy Attributes

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

Tracker criteo (category advertising)
will be blocked by
privacybadger

This cookie expires in 846 days

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

A number of privacy protection projects maintain lists of known web trackers. These trackers
will be in most cases effectively blocked by their browser extensions:

Tracker adscale (category advertising)
will be blocked by
disconnectme

Tracker adscale (category advertising)
will be blocked by
privacybadger

This cookie expires in 1025 days

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

A number of privacy protection projects maintain lists of known web trackers. These trackers
will be in most cases effectively blocked by their browser extensions:

Tracker adscale (category advertising)
will be blocked by
privacybadger

This cookie expires in 692 days

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

The cookie is only valid during current browser session and it will be deleted when you
close
browser

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

A number of privacy protection projects maintain lists of known web trackers. These trackers
will be in most cases effectively blocked by their browser extensions:

Tracker adform (category advertising)
will be blocked by
privacybadger

This cookie expires in 722 days

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

Tracker criteo (category advertising)
will be blocked by
privacybadger

This cookie expires in 1027 days

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

Tracker adform (category advertising)
will be blocked by
privacybadger

This cookie expires in 722 days

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

A number of privacy protection projects maintain lists of known web trackers. These trackers
will be in most cases effectively blocked by their browser extensions:

Tracker adform (category advertising)
will be blocked by
privacybadger

This cookie expires in 722 days

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

Tracker adform (category advertising)
will be blocked by
privacybadger

This cookie expires in 669 days

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

A number of privacy protection projects maintain lists of known web trackers. These trackers
will be in most cases effectively blocked by their browser extensions:

Tracker adform (category advertising)
will be blocked by
privacybadger

This cookie expires in 693 days

httpOnly This cookie can be read by client-side JavaScript
which might increase chances of stealing it in case of a successful
Cross-Side Scripting attack. It's recommended that cookies storing authentication-related
session token are protected by the flag
» More...

Sample value:

1

Length: 1 bytes (8 bits)

Information entropy: 0.00 bits (average bits per symbol)

Information content: 1.00 bits

Cookie classification: third-partypersistent

TLS/SSL configuration report

LocalStorage objects

HTML5 LocalStorage is client-side storage introduced by HTML5 and supported by all major
browsers.
Data stored there is not sent automatically by the browser (unlike HTTP cookies) but is accessible
to
JavaScript code permanently, until deleted by the application or cleaned manually by the user.
These object can be thus compared to first-party persistent cookies from privacy point of
view.

SessionStorage objects

HTML5 SessionStorage is client-side storage introduced by HTML5 and supported by all major
browsers.
Data stored there is not sent automatically by the browser (unlike HTTP cookies) but is accessible
to
JavaScript code during the browser session only, so until the browser window or tab is closed.
These object can be thus compared to first-party session cookies from privacy point of
view.

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.

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 "report-only" mode where no content blocking is enforced and would-be-blocked origins are reported allowing website authors to fine-tune the policy.

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.

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

The header is not in enforcement mode and it provides no actual
protection
to the users. Please consider switching the enforcement mode by using
Content-Security-Policy header.

No base-uri allows attackers to inject base tags which override the base URI to an attacker-controlled origin. Set to 'none' unless you need to handle tricky relative URLs scheme

Consider adding block-all-mixed-content directive if your website is only accessible over TLS and you are certain it doesn not have any legacy plaintext resources. Otherwise you may add adding upgrade-insecure-requests directive if your website may still have some legacy plaintext HTTP resources and you want them to be still available rather than blocked

Sub-resources

Sub-resources

Most web pages load a number of sub-resources such as images, style sheets
(CSS),
JavaScript files, web fonts, audio or video files and other web pages in frames. Each of these
sub-resources
may be loaded from the same server (first-party resource) or servers belonging to other parties
(third-party resources).
In the latter case, the third-party will see a request coming from your browser with the
information
on
the originating page and it can set its own cookies, both of which are frequently used for user
tracking.
Note that the cookies set by these sub-resources are already recorded in our cookie statistics
for
this page.

The page loads 40 third-party JavaScript files and 4 CSS but does not employ Sub-Resource Integrity to prevent breach if a third-party CDN is compromised

Symbols

Resource
securely loaded over TLS

Resource
insecurely loaded over plaintext HTTP.

A third-party
resource. It may perform its own tracking on your requests
and receive partial information about your activities on the original website