https://www.denkwerk.com/data/cases-studies/social-tools.json

Category: Uncategorized

Keywords: value agency berlin brands create munich people cologne digital germany hamburg welcome creating denkwerk homepage locations ownermanaged international


Last fetched: 2018-05-25T03:55:34.609093+00:00

HTTP status: 5 Sub-resource URL


TLS/SSL configuration report

TLS score
A

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

Security-related HTTP headers

  • Server: Apache/2.4.33 (Amazon) OpenSSL/1.0.2k-fips PHP/7.1.17

    Announces web server software and optionally version details.

    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-WebKit-CSP: default-src 'self' 'unsafe-inline' 'unsafe-eval' data: *.denkwerk.com www.googletagmanager.com tagmanager.google.com www.google-analytics.com *.doubleclick.net;         connect-src 'self' *.denkwerk.com;         font-src 'self' *.denkwerk.com;         media-src *.denkwerk.com player.vimeo.com *.vimeocdn.com gcs-vimeo.akamaized.net;

    Legacy and deprecated variant of the Content-Security-Policy header used by WebKit browsers in the initial period.

    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-Permitted-Cross-Domain-Policies: master-only

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

  • X-Content-Security-Policy: default-src 'self' 'unsafe-inline' 'unsafe-eval' data: *.denkwerk.com www.googletagmanager.com tagmanager.google.com www.google-analytics.com *.doubleclick.net;         connect-src 'self' *.denkwerk.com;         font-src 'self' *.denkwerk.com;         media-src *.denkwerk.com player.vimeo.com *.vimeocdn.com gcs-vimeo.akamaized.net;

    Legacy and deprecated variant of the Content-Security-Policy header used by WebKit browsers in the initial period.

    Read more...

  • Content-Security-Policy: default-src 'self' 'unsafe-inline' 'unsafe-eval' data: *.denkwerk.com www.googletagmanager.com tagmanager.google.com www.google-analytics.com *.doubleclick.net;         connect-src 'self' *.denkwerk.com;         font-src 'self' *.denkwerk.com;         media-src *.denkwerk.com player.vimeo.com *.vimeocdn.com gcs-vimeo.akamaized.net;

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

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

Content Security Policy

  • default-src 'self' 'unsafe-inline' 'unsafe-eval' data: *.denkwerk.com www.googletagmanager.com tagmanager.google.com www.google-analytics.com *.doubleclick.net;         connect-src 'self' *.denkwerk.com;         font-src 'self' *.denkwerk.com;         media-src *.denkwerk.com player.vimeo.com *.vimeocdn.com gcs-vimeo.akamaized.net;
  • default-src 'self' 'unsafe-inline' 'unsafe-eval' data: *.denkwerk.com www.googletagmanager.com tagmanager.google.com www.google-analytics.com *.doubleclick.net;         connect-src 'self' *.denkwerk.com;         font-src 'self' *.denkwerk.com;         media-src *.denkwerk.com player.vimeo.com *.vimeocdn.com gcs-vimeo.akamaized.net;
  • default-src 'self' 'unsafe-inline' 'unsafe-eval' data: *.denkwerk.com www.googletagmanager.com tagmanager.google.com www.google-analytics.com *.doubleclick.net;         connect-src 'self' *.denkwerk.com;         font-src 'self' *.denkwerk.com;         media-src *.denkwerk.com player.vimeo.com *.vimeocdn.com gcs-vimeo.akamaized.net;
Fully automated RESTful API is now available. Subscribe for your free trial today!