https://www.linkedin.com/embed/feed/update/urn:li:activity:6561525985005707264

Category: Jobs & Careers

Keywords: jobs join user dansk email bahasa cookie estina policy talent careers deutsch privacy linkedin malaysia agreement indonesia solutions advertising corporation


Last fetched: 2019-12-02T22:10:03.223252+00:00

HTTP status: 5 Sub-resource URL


TLS/SSL configuration report

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

See full SSL/TLS security report for www.linkedin.com

Security-related HTTP headers

  • Server: Play

    Announces web server software and optionally version details.

    Read more...

  • Expect-CT: max-age=86400, report-uri="https://www.linkedin.com/platform-telemetry/ct"

    The Expect-CT header allows sites to opt in to reporting and/or enforcement of Certificate Transparency requirements, which prevents the use of misissued certificates for that site from going unnoticed. When a site enables the Expect-CT header, they are requesting that the browser check that any certificate for that site appears in public CT logs.

    Read more...

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

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

Content Security Policy

  • default-src *; connect-src 'self' static.licdn.com media.licdn.com static-exp1.licdn.com static-exp2.licdn.com static-exp3.licdn.com media-exp1.licdn.com media-exp2.licdn.com https://media-src.linkedin.com/media/ www.linkedin.com s.c.lnkd.licdn.com m.c.lnkd.licdn.com s.c.exp1.licdn.com s.c.exp2.licdn.com m.c.exp1.licdn.com m.c.exp2.licdn.com wss://*.linkedin.com dms.licdn.com; img-src data: blob: *; font-src data: *; child-src blob: *; style-src 'unsafe-inline' 'self' static-src.linkedin.com *.licdn.com; script-src 'report-sample' 'unsafe-inline' 'unsafe-eval' 'self' spdy.linkedin.com static-src.linkedin.com *.ads.linkedin.com *.licdn.com www.google-analytics.com platform.linkedin.com platform-akam.linkedin.com platform-ecst.linkedin.com platform-azur.linkedin.com; object-src 'none'; media-src blob: *; report-uri https://www.linkedin.com/platform-telemetry/csp?f=nf

Publisher identifiers

The website uses the following advertisement publisher ids:

Pages loading this URL

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