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.
MakerDAO DAI stablecoin address
Ethereum ERC20: Ethereum
Ethereum ERC20: USD//C
Ethereum ERC20: Basic Attention Token
Ethereum ERC20: Matic Token
Ethereum ERC20: Status Network
Ethereum ERC20: Gemini dollar
Ethereum ERC20: Decentraland
Ethereum ERC20: Multi-Collateral DAI
Ethereum ERC20: Enjin Coin
Ethereum ERC20: Nexo
Category: Software Development
Last fetched: 2020-03-12T22:04:19.632185+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.
Announces web server software and optionally version details.Read more...
Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
HTTP Strict Transport Security (HSTS) is an opt-in security enhancement that is specified by a web application through the use of a special response header.Read more...
HTTP Strict Transport Security is enabled+2
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.
Fuzzy content type guessing is disabled+1
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
XSS auditor is enabled in blocking mode+1
The Referrer-Policy HTTP header governs which referrer information, sent in the Referer header, should be included with requests made.Read more...
Transport Layer Security (TLS) is enabled+2
X-Frame-Options header is missing