https://immusec.turbineam.com/TAM/Pulpit

Category: Uncategorized

Keywords: loading

Privacy Impact Score
A

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
0
 
Session cookies
4
 

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 4 session cookies.


Last fetched: 2019-04-23T15:46:34.746380+00:00

HTTP status: 200 200 OK


Cookies and Privacy Attributes

ASP.NET generic session cookie

» More...
  • Type: HTTP Cookie
  • Domain: immusec.turbineam.com
  • The cookie is only valid during current browser session and it will be deleted when you close browser
  • httpOnly This cookie is not readable by client-side JavaScript code » More...
  • Sample value:
    u4ukyjuf3bo15kbylronyzfz

A generic language preference functional cookie. The cookie is used to store user's preferred language for the website to be able to display the preferred translation without user intervention. In contrast to content language negotiation preference passed by Accept-Language HTTP header, the cookie setting will only work for this particular website only

» More...
  • Type: HTTP Cookie
  • Domain: immusec.turbineam.com
  • 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...
  • Sample value:
    en

Generic Cross Site Request Forgery prevention token

» More...
  • Type: HTTP Cookie
  • Domain: immusec.turbineam.com
  • The cookie is only valid during current browser session and it will be deleted when you close browser
  • httpOnly This cookie is not readable by client-side JavaScript code » More...
  • Sample value:
    0VBrDiofYIOgZdEuzaECkk_7F3xWt_0roPfecP9yKq4hncH2pN8ietr_IIbYBJsMEQDnCcbfUq3-7lkroOEbuRijjwI1

Generic Cross Site Request Forgery prevention token

» More...
  • Type: HTTP Cookie
  • Domain: immusec.turbineam.com
  • 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...
  • Sample value:
    ydsfYIm0_yxiBYcNlSCS8FUTmx_0EL2988r-QkIw6O8rtNeWmbaJ8JJnowPBbHYngnXkUxKViPkvhuHshAACxgdQZIM1

TLS/SSL configuration report

TLS score
C
Grade capped at C
Grade capped due to 64-bit cipher (IDEA, RC2, DES or 3DES)

See full SSL/TLS security report for immusec.turbineam.com

HTTP security-related headers assessment

Security score
11

Security-related HTTP headers

  • Feature-Policy: accelerometer 'none'; camera 'none'; geolocation 'none'; gyroscope 'none'; magnetometer 'none'; microphone 'none'; payment 'none'; usb 'none'

    Allows web developers selectively enable and disable specific web technologies, especially those that enable two-way communication between the user and web application. For example, the header may inform the user mobile device that the website is not using camera or location tracking by design.

    Read more...

  • Strict-Transport-Security: max-age=31536000; includeSubDomains

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

  • X-Permitted-Cross-Domain-Policies: none

    Header used by Adobe Flash engine to control cross-site access for Flash applications. Most websites not using Flash would prefer to set it with the value of none as an additional precaution against using them in advanced Flash-based XSS vectors. Flash-serving websites can use them to declare the scope of detailed Flash cross-site policies per Adobe specification.

    Read more...

  • Referrer-Policy: no-referrer

    The Referrer-Policy HTTP header governs which referrer information, sent in the Referer header, should be included with requests made.

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

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

Content Security Policy

  • default-src 'self' blob: data: https://*.intercomcdn.com https://*.intercomassets.com; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-eval' 'unsafe-inline' https://*.intercomcdn.com https://*.intercom.io; connect-src 'self' wss://*.intercom.io https://*.intercom.io;

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.

Symbols

  • Resource securely loaded over TLS
  • Resource insecurely loaded over plaintext HTTP.
  • Mixed content warning. This resource is loaded over plaintext HTTP on TLS page will be blocked by most modern browser. Read more...
  • A third-party resource. It may perform its own tracking on your requests and receive partial information about your activities on the original website
  • Resource with reputation warnings
  • Blacklisted domain
  • Suspicious pattern detected
Fully automated RESTful API is now available. Subscribe for your free trial today!