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
Keywords: ssp tech cloud deals learn careers console request adserver agencies appnexus audience overview products companies extension publisher publishers advertisers capabilities
Last fetched: 2020-08-05T16:36:32.472085+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'
Announces web server software and optionally version details.Read more...
The header exposes web server version details. These server no purpose apart from making life of security auditors and hackers easier, leading them straight to exploits for this particular version of product. WebCookies.org does offer security design and penetration testing services so we can help!-1
P3P: policyref="http://cdn.adnxs.com/w3c/policy/p3p.xml", CP="NOI DSP COR ADM PSAo PSDo OURo SAMo UNRo OTRo BUS COM NAV DEM STA PRE"
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
XSS auditor is disabled0
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.
The header sets permissive AJAX access by using wildcard origin
*. It may be OK if the website is a publicly accessible REST API but otherwise it should be not present at all
Transport Layer Security (TLS) is enabled+2
X-Frame-Options header is missing
X-Content-Type-Options header is missing