11–20 of 45 posts
Really nice! Positive and negative results are marked green and red. Colorblind users will need additional visual clues (e.g. checkmark vs cross) to differentiate between the sections.
If you enter a URL in the suggested format – with http:// – you get an error. > Invalid domain: http://http//www.coruscade.com Either change the placeholder or, preferably, detect whether the user’s input contains http:// and adjust accordingly.
Earlier quoted context omitted.
If I enter https:// for a site I manage, the tool automatically changes it to http:// , claims that's what I entered, and then tells me the connection is not secure. Needs work.
I think this means that the tool is not automatically being redirected to https:// when visiting your website at http:// , so it's marked as insecure (See point 2. on the website).
It's minor, but you could add Apache and/or Nginx and/or Lighttpd examples for many of the recommendations.
> Your browser then sends Referer: ... While I don't doubt dataskydd's good intentions, their advice about referrers is a sign that we live in Clown World. Yes, your browser's tendency to provide a referrer might well give away information you would prefer it didn't. Unfortunately for you, the browser vendors have chosen to provide browsers that do that. In a parallel universe it would be obvious that this is a probl…
"Note: Because the source of a link may be private information or may reveal an otherwise private information source, it is strongly recommended that the user be able to select whether or not the Referer field is sent. For example, a browser client could have a toggle switch for browsing openly/anonymously, which would respectively enable/disable the sending of Referer and From information."
(https://tools.ietf.org/html/rfc1945#section-10.13)
This recommendation was not followed in any meaningful way, but Referrer Policy (https://www.w3.org/TR/referrer-policy/), which supports a whole bunch of different policies and is very easy to implement (and now widely supported), at least makes things slightly better.
Nice tool! I just added some of the recommended headers on my personal (static, single origin) sites. It's minor, but you could add Apache and/or Nginx and/or Lighttpd examples for many of the recommendations.
> Your browser then sends Referer: ... While I don't doubt dataskydd's good intentions, their advice about referrers is a sign that we live in Clown World. Yes, your browser's tendency to provide a referrer might well give away information you would prefer it didn't. Unfortunately for you, the browser vendors have chosen to provide browsers that do that. In a parallel universe it would be obvious that this is a probl…
I'm guessing the reason others are downvoting you is that Referer Policy is exactly that: it's the attempt of modern browsers to address this problem (a problem that yes, they did create, but the fact they're supporting Referer Policy at all at least shows that the problem was created out of incompetence rather than malice).
155 Cookies, 319 Third-party requests, 125 Third-parties contacted
Beat it if you can :)
newyorker.com 155 Cookies, 319 Third-party requests, 125 Third-parties contacted Beat it if you can :)
Not a clear win, but also "impressive."
Nice tool! I just added some of the recommended headers on my personal (static, single origin) sites. It's minor, but you could add Apache and/or Nginx and/or Lighttpd examples for many of the recommendations.
Definitely. Planning to redesign and rewrite the whole results page later this year.