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.
Title: "Rozpadl se nejlepší deblový pár, s Mirzaovou bude hrát Strýcová - iDNES.cz"
Description: "Neklapalo to, tak se rozešly. Sania Mirzaová a Martina Hingisová, které tvořily nejlepší světový deblový pár současnosti, ukončily spolupráci. Důvodem jsou špatné výsledky z poslední doby. Indka Mirzaová se podle tamní agentury PTI dohodla na spolupráci s českou tenistkou Barborou Strýcovou, s níž absolvuje mimo jiné grandslamové US Open."
Keywords: cupu jako davis hokej https kvtna naeho plkov tenis kvitov pspvek 17kvtna idnescz karolna vsledky archivovn australian zpravodaje aktualizovno sportidnescz
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 13 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 32 persistent cookies with average life-time of 1367 days and longest 7830 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 2 session cookies.
Last fetched: 2018-05-20T18:07:24.494520+00:00
HTTP status: 200 200 OK
LocalStorage is client-side storage introduced by HTML5 and supported by all major
Data stored there is not sent automatically by the browser (unlike HTTP cookies) but is accessible
These object can be thus compared to first-party persistent cookies from privacy point of
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.macromedia.com/xml/dtds/cross-domain-policy.dtd">
<allow-access-from domain="*" secure="false" />
Read here to see how this can be abused.
Announces web server software and optionally version details.Read more...
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 (
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
Content-Security-Policy-Report-Only: default-src 'self' https: 'unsafe-inline' data: 'unsafe-eval'; report-uri https://servix.idnes.cz/log/csp-report.aspx?w=sport&d=2018-05-20
Content Security Policy is used by a web server to declare a list of trusted content types (images, scripts, media etc) and origins from which they can be safely loaded as intended by the website authors. The
Content-Security-Policy-Report-Only header instruct the browser to enable CSP in "report-only" mode where no content blocking is enforced and would-be-blocked origins are reported allowing website authors to fine-tune the policy.
X-Powered-By: iDNES iweb53
A non-standard and purely informational, but still very widespread header, whose only purpose is to advertise the name and optionally version of the software used to run the web server.Read more...
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
Instructs the browser if the current website can be embedded in HTML frame by another website. Since this allows the parent website to control the framed page, this creates a potential for data theft attacks ("clickjacking") and most sensitive websites won't allow them to be framed at all (
deny) or just allow parts of them to be embedded in frames created by themselves only (
Clickjacking protection is enabled+2
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
Transport Layer Security (TLS) is not enabled-2
default-src 'self' https: 'unsafe-inline' data: 'unsafe-eval'; report-uri https://servix.idnes.cz/log/csp-report.aspx?w=sport&d=2018-05-20
base-uri allows attackers to inject
base tags which override the base URI to an attacker-controlled origin. Set to
'none' unless you need to handle tricky relative URLs scheme
block-all-mixed-content directive if your website is only accessible over TLS and you are certain it doesn not have any legacy plaintext resources. Otherwise you may add adding
upgrade-insecure-requests directive if your website may still have some legacy plaintext HTTP resources and you want them to be still available rather than blocked
default-src data: origin allows bypassing CSP and execution of inlined untrusted scripts
default-src 'unsafe-inline' allows bypassing of CSP and execution of inlined untrusted scripts. Use
default-src 'unsafe-eval' allows bypassing of CSP and execution of inlined untrusted scripts. Use
Want second opinion? Try Google CSP Evaluator.
The website uses the following advertisement publisher ids: