https://cdn.syndication.twimg.com/timeline/profile?callback=__twttr.callbacks.tl_i0_profile_Carrouseldufilm_old&dnt=false&domain=carrousel.qc.ca&lang=fr&screen_name=Carrouseldufilm&suppress_response_codes=true&t=1748028&tz=GMT%2B0000&with_replies=false

Category: Uncategorized

Keywords: ting norsk roman bahasa center melayu polski search status turkce english svenska twitter homepage hrvatski italiano indonesia portugues slovenina nederlands


Last fetched: 2019-11-08T15:01:54.687995+00:00

HTTP status: 5 Sub-resource URL


TLS/SSL configuration report

TLS score
F
Grade capped at F
Certificate path cannot be verified to a known root certificate

See full SSL/TLS security report for cdn.syndication.twimg.com

Security-related HTTP headers

  • Server: tsa_f

    Announces web server software and optionally version details.

    Read more...

  • Strict-Transport-Security: max-age=631138519

    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-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-Frame-Options: SAMEORIGIN

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

  • X-XSS-Protection: 0

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

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