https://securepubads.g.doubleclick.net/pcs/view?xai=AKAOjsuCzLHzhp_x5Pt6lHauhPP6FcSTlJnLFPnP7vnyH-uoipDxHrIsXdZW1rCSTaVG8mPveZWbTGpfabexImXH0CmMqbhBP3L9CGrgQnNRGdyvwuTN5N_95vOTXOsgXQnmFd3w21SYObbU2BzkkHIP3t1LK_tc4YgRNlx3S8QrAKtx46UUhR9LR75Hy0mHYmV35ZrUTGlc2UG9QUteuUZ-OLEKwDqRA3OJ0fJNGh2i2gJbFGOKOsLkshJW1z32ouEcLbM&sig=Cg0ArKJSzKJDJXO4nh-7EAE&adurl=

Category: Advertising & Tracking

Keywords: error found thats found1 server requested


Last fetched: 2019-09-11T08:22:29.909486+00:00

HTTP status: 5 Sub-resource URL


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 securepubads.g.doubleclick.net

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

  • Server: cafe

    Announces web server software and optionally version details.

    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: *

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

  • P3P: policyref="https://googleads.g.doubleclick.net/pagead/gcn_p3p_.xml", CP="CURa ADMa DEVa TAIo PSAo PSDo OUR IND UNI PUR INT DEM STA PRE COM NAV OTC NOI DSP COR"

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

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