http://cm.g.doubleclick.net/pixel?google_nid=pubmatic&google_cm=&google_sc=

Category: Advertising & Tracking

Keywords: error found right state thats video found1 server digital marketing requested integrated management advertising doubleclick viewability solutionsrevenue managerdoubleclick exchangedoubleclick publishersdoubleclick


Last fetched: 2016-04-25T13:13:50.819306+00:00

HTTP status: 4 Connection error error


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

Security-related HTTP headers

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

  • Server: HTTP server (unknown)

    Announces web server software and optionally version details.

    Read more...

  • Location: http://cm.g.doubleclick.net/pixel?google_nid=pubmatic&google_cm=&google_sc=&google_tc=

    The HTTP Location header is being returned by a server to redirect the web browser to a new URL of the requested resource. The URL may be relative (/index.html) or absolute (https://example.com).

    Read more...

  • P3P: policyref="http://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...

Sub-resources

Most web pages load a number of sub-resources such as images, style sheets (CSS), JavaScript files, web fonts, audio or video files and other web pages in frames. Each of these sub-resources may be loaded from the same server (first-party resource) or servers belonging to other parties (third-party resources). In the latter case, the third-party will see a request coming from your browser with the information on the originating page and it can set its own cookies, both of which are frequently used for user tracking. Note that the cookies set by these sub-resources are already recorded in our cookie statistics for this page.

Symbols

  • Resource securely loaded over TLS
  • Resource insecurely loaded over plaintext HTTP.
  • A third-party resource. It may perform its own tracking on your requests and receive partial information about your activities on the original website
  • Resource with reputation warnings
  • Blacklisted domain
  • Suspicious pattern detected
Fully automated RESTful API is now available. Subscribe for your free trial today!