All-in-one free web application security tool. Web application vulnerability and privacy scanner with support for HTTP cookies, Flash, HTML5 localStorage, sessionStorage, CANVAS, Supercookies, Evercookies. Includes a free SSL/TLS, HTML and HTTP vulnerability scanner and URL malware scanner.
1x1 transparent GIF is frequently used as user tracking mechanism
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-05-08T09:36:22.354761+00:00
HTTP status: 5 Sub-resource URL
Advanced user tracking and fingerprinting techniques are used by websites to bypass privacy protection in web browsers and increase tracking persistence.
b'GIF8' … b'\x01\x00\x01\x00'
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...
P3P is a mostly abandoned standard for website privacy policy declaration that has little use today. Please consider switching to DoNotTrack standard.
0Location: https://cm.creativecdn.com/adx/cm?v=2&pi=adx&tdc=sin&chain=&google_gid=CAESEBTJp_x6C85IzhLes2a7nb4&google_cver=1&google_ula=5153224,0
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
).
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
.
XSS auditor is disabled
0Transport Layer Security (TLS) is enabled
+2X-Frame-Options
header is missing
X-Content-Type-Options
header is missing