https://www.facebook.com/ChillVeeintheworld55555555555555555555555555555CLB

Title: "Warakorn Warapornprasert | Facebook"
Description: "Warakorn Warapornprasert is on Facebook. Join Facebook to connect with Warakorn Warapornprasert and others you may know. Facebook gives people the power..."

Category: Social Network

Keywords: apps data make share users others people policy account content cookies provide facebook policies services companies including statement advertising information

Third-party domains
1
 
Persistent cookies
3
 
Session cookies
1
 

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 1 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 3 persistent cookies with average life-time of 303 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 1 session cookies.


Last fetched: 2017-03-06T07:34:25.515835+00:00

HTTP status: 200 200


Cookies and Privacy Attributes

fr

Facebook tracking cookie

» More...
  • Type: HTTP Cookie
  • Domain: facebook.com
  • This cookie expires in 90 days
  • httpOnly This cookie is not readable by client-side JavaScript code » More...
  • Size: 52 bytes
  • Sample value:
    0oIu7IeJ2O4sdbkQw..BYvUwL.Er.AAA.0.0.BYvUwL.AWUbj8Kc
wd

Facebook tracking cookie

» More...
  • Type: HTTP Cookie
  • Domain: facebook.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...
  • Size: 7 bytes
  • Sample value:
    400x300
ATN

Microsoft advertising tracking cookie

» More...
  • Type: HTTP Cookie
  • Domain: atdmt.com
  • This cookie expires in 730 days
  • httpOnly This cookie is not readable by client-side JavaScript code » More...
  • Size: 53 bytes
  • Sample value:
    1.1488800780.16584534230093894178.AYLKdYiBYVCuZGKvO2w

Microsoft advertising tracking cookie

» More...
  • Type: HTTP Cookie
  • Domain: atdmt.com
  • This cookie expires in 90 days
  • httpOnly This cookie is not readable by client-side JavaScript code » More...
  • Size: 67 bytes
  • Sample value:
    AXzeMGc3GdOcFJp1GddjEwfSJSFE6jTw1hRON6yf7Ff55Jd_Wq3VyqsglSAFeEJAPMs

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 www.facebook.com

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.

  • Type: HTML5 SessionStorage cookie
  • Size: 186 bytes

HTTP security-related headers assessment

Security score
7

Security-related HTTP headers

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

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

  • P3P: CP="Facebook does not have a P3P policy. Learn why here: http://fb.me/p3p"

    Largely abandoned format for declaring website's privacy policy in machine-readable format. The only reason for many websites to use the header was that old versions of Microsoft Internet Explorer disallowed third-party cookies on websites missing P3P.

    Read more...

  • Public-Key-Pins-Report-Only: max-age=500; pin-sha256="WoiWRyIOVNa9ihaBciRSC7XHjliYS9VwUGOIud4PB18="; pin-sha256="r/mIkG3eEpVdm+u/ko/cwxzOMo1bk4TyHIlByibiA5E="; pin-sha256="q4PO2G2cbkZhZ82+JgmRUyGMoAeozA+BSXVXQWB8XWQ="; report-uri="http://reports.fb.com/hpkp/"

    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=15552000; 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...

  • 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://www.facebook.com

    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!