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: "IPSec.pl | Application Security since 1998"
Description: "This site is dedicated to application security, penetration testing, application security risk valuation and other research projects involving web framework security, cryptography and electronic signature."
Category: Information Security
Keywords: pawe used user ipsec prawo using search system content cookies ipsecpl serwisu website comments krawczyk security template echelonpl submitted application
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 2 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 2 persistent cookies with average life-time of 217 days and longest 400 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-06-16T17:47:21.148442+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
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 (
Transport Layer Security (TLS) is not enabled-2
X-Frame-Options header is missing
X-XSS-Protection header is missing
X-Content-Type-Options header is missing
connect-src http://ajax.googleapis.com https://api.mixpanel.com http://api.mixpanel.com 'self' ; child-src 'none' ; font-src https://fonts.gstatic.com data: 'self' https://ipsec.pl ; form-action https://bitpay.com 'self' ; frame-ancestors about ; frame-src https://platform.twitter.com https://googleads.g.doubleclick.net https://disqus.com http://disqus.com http://static.ak.facebook.com https://s-static.ak.facebook.com http://googleads.g.doubleclick.net https://accounts.google.com https://apis.google.com http://www.facebook.com https://www.facebook.com https://docs.google.com ; img-src https://bitpay.com https://www.paypalobjects.com data: https://ddfnmo6ev4fd.cloudfront.net https://syndication.twitter.com http://ssl.gstatic.com https://ssl.gstatic.com http://www.google-analytics.com 'self' https://licensebuttons.net https://cdn.mxpnl.com https://i.creativecommons.org http://webcookies.org http://i.creativecommons.org https://referrer.disqus.com https://a.disquscdn.com http://referrer.disqus.com http://a.disquscdn.com https://cspbuilder.info http://ipsec.pl https://pagead2.googlesyndication.com https://ipsec.pl http://www.userfriendly.org http://www.commoncriteriaportal.org https://translate.googleapis.com https://www.google.com http://books.google.com http://www.isaca.org.pl ; media-src 'none' ; object-src http://www.gstatic.com https://www.gstatic.com ; script-src 'unsafe-eval' 'unsafe-inline' 'self' http://ajax.googleapis.com https://connect.facebook.net https://platform.twitter.com https://pagead2.googlesyndication.com https://ipsecpl.disqus.com https://cdn.mxpnl.com https://a.disquscdn.com http://pagead2.googlesyndication.com https://apis.google.com http://cdn.mxpnl.com http://echelonpl.disqus.com http://a.disquscdn.com http://connect.facebook.net http://kabardianscom.disqus.com http://www.google-analytics.com https://translate.googleapis.com https://ipsec.pl ; style-src https://fonts.googleapis.com 'unsafe-eval' 'self' https://a.disquscdn.com http://a.disquscdn.com 'unsafe-inline' https://ipsec.pl https://translate.googleapis.com ; default-src 'none' ; strict-mixed-content-checking; reflected-xss filter; referrer origin-when-cross-origin;
reflected-xss directive has been deprecated since early drafts of CSP2, removed from Chrome in 2017 and never implemented in any other browsers. See Chrome status Deprecate
reflected-xss CSP directive.
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
You should definitely try using
'strict-dynamic' to eliminate those long lists of trusted third-party scripts
script-src 'report-sample' as it significantly helps debugging CSP reports. See specification
script-src 'unsafe-eval' allows bypassing of CSP and execution of inlined untrusted scripts. Use
script-src 'unsafe-inline' allows bypassing of CSP and execution of inlined untrusted scripts. Use
script-src http://ajax.googleapis.com is known to host JSONP which can be used to bypass CSP and execute untrusted scripts
script-src http://www.google-analytics.com is known to host JSONP which can be used to bypass CSP and execute untrusted scripts
style-src 'unsafe-eval' allows bypassing of CSP and execution of inlined untrusted scripts. Use
style-src 'unsafe-inline' allows bypassing of CSP and execution of inlined untrusted scripts. Use
strict-mixed-content-checking is not part of the latest W3C CSP standard
reflected-xss is not part of the latest W3C CSP standard
referrer is not part of the latest W3C CSP standard
Want second opinion? Try Google CSP Evaluator.
The website uses the following advertisement publisher ids: