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: "Blogger: Insane Coding - Post a Comment"
Category: Cloud Service/Hosting
Keywords: lrm blog free canada create custom design domain google united blogger chinese content english espanol spanish francais analytics beautiful portugues
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 1 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 3 persistent cookies with average life-time of 487 days and longest 730 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-03T08:15:13.973032+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.
P3P: CP="This is not a P3P policy! See https://www.google.com/support/accounts/bin/answer.py?hl=en&answer=151657 for more info."
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 (
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
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
Announces web server software and optionally version details.Read more...
Transport Layer Security (TLS) is enabled+2
script-src 'self' *.google.com *.google-analytics.com 'unsafe-inline' 'unsafe-eval' *.gstatic.com *.googlesyndication.com *.blogger.com *.googleapis.com uds.googleusercontent.com https://s.ytimg.com https://i18n-cloud.appspot.com www-onepick-opensocial.googleusercontent.com www-bloggervideo-opensocial.googleusercontent.com www-blogger-opensocial.googleusercontent.com https://www.blogblog.com; report-uri /cspreport
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
Policy that has
script-src but not
default-src: 'none' allows script execution by injecting plugin resources. Please read our CSP guidance for more details for more details
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-inline' allows bypassing of CSP and execution of inlined untrusted scripts. Use
script-src 'unsafe-eval' allows bypassing of CSP and execution of inlined untrusted scripts. Use
script-src *.gstatic.com is known to host JSONP which can be used to bypass CSP and execute untrusted scripts
Want second opinion? Try Google CSP Evaluator.
The website uses the following advertisement publisher ids: