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.
User browser fingerprinting through HTML5 CANVAS element contents)
User tracking using web beacons)
Category: CDN Resource API Endpoint
Keywords: error found thats found1 server requested
Privacy Impact Score is a score reflecting overall cookie-related impact of the website relative to other websites, primarily taking into account the number of third-party domains it reports to and number of persistent cookies it sets. See Privacy Impact Score article for more details.
Third-party domains is the count of organisations allowed by the webmaster to trace your across the site. These cookies may be set for various purposes, like tracking ads displayed on the website, collection of statistics, targeted advertising etc. This website allows 0 other websites to track your activity.
Persistent cookies are the cookies that are preserved through browser shutdowns. This means, even if you close this page today and ever return there in future, the website will know you're a returning visitor. This may be used for "remember me" features, as well as persistent user tracking. These cookies, especially if set by third party organisations, are powerful tool for monitoring your activities across all the websites you visit. This website sets 0 persistent cookies with average life-time of 0 days and longest 0 days.
Session cookies are cleared when you close your browser and allow the website to identify user's state — such as logged-in users. They are mostly considered harmless because they cannot be used for long-term user tracking. This site sets 0 session cookies.
Last fetched: 2019-09-11T04:22:39.996492+00:00
HTTP status: 200 200 OK
Advanced user tracking and fingerprinting techniques are used by websites to bypass privacy protection in web browsers and increase tracking persistence.
b'.createElement("canvas")' … b'.createElement("canvas")' … b'.getContext("2d")' … b'.getContext("2d")' … b'.getImageData(' … b'.getImageData(' … b'String.fromCharCode(' … b'String.fromCharCode(' … b'String.fromCharCode(' … b'String.fromCharCode(' … b'String.fromCharCode(' … b'String.fromCharCode(' … b'String.fromCharCode(' … b'String.fromCharCode(' … b'String.fromCharCode(' … b'String.fromCharCode('
b'navigator.sendBeacon' … b'navigator.sendBeacon' … b'navigator.sendBeacon' … b'navigator.sendBeacon'
This file defines the cross-domain policy for Adobe applications. Dangerous if permissive or too broadly set » More...
<!DOCTYPE cross-domain-policy SYSTEM "http://www.adobe.com/xml/dtds/cross-domain-policy.dtd">
<allow-access-from domain="*" secure="false"/>
<allow-http-request-headers-from domain="*" headers="*" secure="false"/>
Read here to see how this can be abused.
Fuzzy content type guessing is disabled+1
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.
Announces web server software and optionally version details.Read more...
XSS auditor is disabled0
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
Transport Layer Security (TLS) is enabled+2
X-Frame-Options header is missing
Historically, web plugins such as Adobe Flash, Java applets, Silverlight etc were used to deliver rich user experience to users in HTML-only browsers. As HTML5 support became more widespread offering the same experience but in standards-based manner, web browser vendors decided to gradually abandond support for these plugins so that in long-term website owners should thus plan to replace the plugin-based functionality with one based on HTML5 features.