https://cm.g.doubleclick.net/pixel?google_nid=zeotap_ddp&google_cm=&zpartnerid=1&env=mWeb&zdid=738&eventType=pageview&zpb=sharethisZHwAB14dpG0AAAATMee0Aw%3D%3D&google_tc=

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: 2020-01-14T11:23:00.909319+00:00

HTTP status: 5 Sub-resource URL


TLS/SSL configuration report

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

See full SSL/TLS security report for cm.g.doubleclick.net

Advanced trackers

Advanced user tracking and fingerprinting techniques are used by websites to bypass privacy protection in web browsers and increase tracking persistence.

b'\x89PNG' … b'IHDR' … b'\x00\x00\x00\x01\x00\x00\x00\x01'

Security-related HTTP headers

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

  • Location: https://mwzeom.zeotap.com/mw?google_gid=CAESEM-3BOvQv1n8Y5pctddFW6k&google_cver=1&zpartnerid=1&env=mWeb&zdid=738&eventType=pageview&zpb=sharethisZHwAB14dpG0AAAATMee0Aw==

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

  • Server: HTTP server (unknown)

    Announces web server software and optionally version details.

    Read more...

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

Sub-resources

Parent pages

Parent pages loading this resource.
Fully automated RESTful API is now available. Subscribe for your free trial today!