DNSSEC Validator

This plugin does not work. It is enabled, but does not do anything.

Does not put anything in the address bar. Settings page works, it's enabled, just doesn't apparently do anything. And on the "support" page the link provided gives a 404 not found error.

Great tool! Really useful and I wish Google Chrome had this functionality already build in. It would be great if the version available here could be upgrade to the latest, so it will include TLSA validation as well.

Doesn't work here. Nothing is displayed, options page is blank.

Doesn't work with SOCKS/http proxy set. Extension says the IP is 127.0.0.1, which obviously doesn't match the resolved IP.

Hello, if the DNS server or the resolver, which is currently being used, does not support DNSSEC then a warning pop-up is displayed. Typically this behaviour can occur at wireless connection when user moves between several WIFI connection without restarting the browser. In such situation, you should change the validator settings. Set a custom resolver which supports DNSSEC data forwarding (e.g., 8.8.8.8), or you can use the ‘Without resolver’ choice. Best Regards. Martin Straka Labs CZ.NIC

Nice small extension! Worked like a charm until today: I keep on getting a popup complaining my resolver/server doesn't support DNSSEC every minute. I disabled the extension till a solution will be implemented.

I thought this was working perfectly, i.e. it shows the grey icon for 'Not secured by DNSSEC' on most sites, but the green one on my own domain which I know is. However I keep on getting a popup complaining my resolver/server doesn't support DNSSEC, when it definitely does as evidenced both by prior testing and this extension showing the green icon for my own domain. This is on a static ADSL 2+ connection with 'Use system settings' (which means my own local bind 9 instance on a Debian stabl... Show more

labs.nic.cz: Domain is signed, but chain of trust can not be established.

"Domain is signed, but chain of trust can not be established." This is displayed on all DNSSEC enabled sites, pro bably due to being unable to verify one IPv6 root server -- no IPv6 from ISP here.