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

0

Persistent cookies

943

Session cookies

5

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 943
persistent cookies with average life-time of 341
days and longest 730 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 5 session
cookies.

Last fetched: 2018-12-08T17:36:21.951425+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...

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

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

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

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 is not readable by client-side JavaScript code
» More...

Sample value:

d91e05e508e47789ab856f377086571411544290557

This cookie seems to be a hexadecimal-encoded data.
Attempted decoded value:

b'\x91\xe0^P\x8eGx\x9a\xb8V\xf3w\x08eqA\x15D)\x05W'

Length: 21 bytes (168 bits)

Information entropy: 4.39 bits (average bits per symbol)

Information content: 92.24 bits

Cookie classification: same-originpersistent

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.

Adobe Flash Shared Objects

Adobe Flash
Shared Object
is a cookie-like, client-side data storage facility used by Flash applications. Local
Shared Objects are pretty much like
same-origin cookies, retrieved by an application running on the same page, while Remote
Shared Objects are stored by the
application on a third-party server.

Publisher identifiers

Web Plugins

Historically, web plugins such as Adobe Flash, Java applets, Silverlight etc were used to deliver rich
user experience
to users in HTML-only browsers. As HTML5 support became more widespread offering the same experience but
in
standards-based manner, web browser vendors decided to gradually abandond support for these plugins so
that in long-term website owners
should thus plan to replace the plugin-based functionality with one based on HTML5 features.

http://www.bastardofuori.altervista.org/swf/clock_calendar.swf

Type: Shockwave Flash

http://www.bastardofuori.altervista.org/swf/google.swf

Type: Shockwave Flash

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 20 third-party JavaScript files and 5 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