https://privacyinternational.org/misc/drupal.js?o74bv0=

Category: Educational

Keywords: data work legal where people policy collect cookies privacy process personal purposes research campaigns financial governments information surveillance international communications


Last fetched: 2016-06-04T02:55:51.525222+00:00

HTTP status: 200 200


TLS/SSL configuration report

TLS score
A

See full SSL/TLS security report for privacyinternational.org

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.

    Read more...

  • X-Frame-Options: DENY

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

    Read more...

  • Public-Key-Pins: pin-sha256="RRM1dGqnDFsCJXBTHky16vi1obOlCgFFn/yOhI/y+ho="; pin-sha256="WoiWRyIOVNa9ihaBciRSC7XHjliYS9VwUGOIud4PB18="; pin-sha256="lT09gPUeQfbYrlxRtpsHrjDblj9Rpz+u7ajfCrg4qDM="; pin-sha256="h6801m+z8v3zbgkRHpq6L29Esgfzhj89C1SyUCOQmqU=";pin-sha256="DuDQSSa4ubaTzab5MBjh2NvrEkDzt10kPEdnDQUPnZ0=";pin-sha256="lCppFqbkrlJ3EcVFAkeip0+44VaoJUymbnOaEUk7tEU=";pin-sha256="ORuXcQB//xhdb52by/Vmo/qhrTuazztSjlMMhaafJZ0=";pin-sha256="x9SZw6TwIqfmvrLZ/kz1o0Ossjmn728BnBKpUFqGNVM=";pin-sha256="58qRu/uxh4gFezqAcERupSkRYBlBAvfcw7mEjGPLnNU=";pin-sha256="YH3gQW7+dkqR106QZabQ1Aj+6wtLuy70aAZpWreNcBc="; max-age=1209600; report-uri="http://report.globalcause.net/privacyint/live";

    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.

    Read more...

  • Content-Security-Policy: upgrade-insecure-requests; block-all-mixed-content;

    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.

    Read more...

  • Public-Key-Pins-Report-Only: pin-sha256="wO7MxsgxyViSwqj+qbxB3BHFKRplhxDXwnE1DaATywE="; pin-sha256="IcWAHRs7OCS5MVu9nUZmTMvAob2eTW0iiF1oyqBwRb0=";pin-sha256="LaEJ4v7cUhF8opUgeSMuEkRYBsW3L66vtXE3qaaYmbA=";pin-sha256="gqcCw8nTaZQ5Bh9gfDiTrXOoI/ijqDhTuCL1QD3tmOE="; max-age=1209600; report-uri="http://report.globalcause.net/privacyint/ro";

    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 report-only mode.

    Read more...

  • Strict-Transport-Security: max-age=15600000; includeSubdomains; 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.

    Read more...

  • Server: nginx

    Announces web server software and optionally version details.

    Read more...

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

    Read more...

  • Access-Control-Allow-Origin: https://*.privacyinternational.org, https://www.privacyinternational.org

    Controls origins (websites) that are allowed to load data from this web service over JavaScript-based APIs as part of Cross-Origin Resource Sharing (CORS) standard. By default, a web browser will refuse to load data over XmlHttpRequest from a website that is not in the same origin, which is a precaution against various types of data stealing attacks. The target server has to explicitly allow the origin domain using the Access-Control-Allow-Origin (ACAO) header, or it may allow all origins to access it using a wildcard *. The latter however creates a potential security issue if the website in question is transactional and processing sensitive data, so the wildcard should be only used on websites consciously offering public APIs.

    Read more...

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