https://apikeys.civiccomputing.com/c/v?d=datalexconsultancy.ie&p=CookieControl+Free&v=8&k=c981c9aefc3d3696831a2c2314ab9862f60f1739&format=json

Category: Engineering

Keywords: blog port work award civic users apache cookie server control digital winning industry services software requested solutions management development apikeysciviccomputingcom


Last fetched: 2020-02-12T17:46:28.814625+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 apikeys.civiccomputing.com

Security-related HTTP headers

  • Server: Apache

    Announces web server software and optionally version details.

    Read more...

  • Access-Control-Allow-Origin: *

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

  • X-XSS-Protection: 1

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

  • Referrer-Policy: strict-origin-when-cross-origin

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

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