News for hackers. Stuff that matters.

A comment on Marking HTTP as Non-Secure.

Re:Marking HTTP as Non-Secure by sft on Saturday December 13, 2014 @06:29AM (#8744927)
Google and others rarely ever mention DNS/DNSSEC, even though just as much information is being sent insecurely in the form of DNS queries/responses.

Learn more:

https://github.com/jedisct1/dnscrypt-proxy

http://dnscrypt.org/

Check if you already have it enabled (unlikely if this is the first time you're learning about this) http://test.dnssec-or-not.com/

[ Parent | on HN ]
Re:Marking HTTP as Non-Secure by kissickas on Saturday December 13, 2014 @06:43AM (#8744957)
Is this working for everyone else? I get a "server not found" message.

http://downforeveryoneorjustme.com/http://test.dnssec-or-not... tells me that the server is up.

[ Parent | on HN ]
Re:Marking HTTP as Non-Secure by sft on Saturday December 13, 2014 @07:14AM (#8745014)
working fine here

there are others to check if you have it (I'm pretty sure you won't unless you have explicitly set it up yourself)

google 'DNSSEC test'

btw setting up DNSCrypt-proxy takes all of 10 minutes on Windows

[ Parent | on HN ]