While cloudflare.com/ssl/encrypted-sni/#results tells me that "DNSSEC. Attackers cannot trick you into visiting a fake website by manipulating DNS responses for domains that are outside their control," this extension claims that "cloudflare.com not secure by DNSSEC. Domain www.cloudflare.com is not secure through DNSSEC. Your connection is prone to man-in-the-middle attacks."

Results inaccurate when choosing Cloudflare as the resolver, but can be worked around by choosing Google as the resolver. No option for custom resolver or even native recursive resolution.

Can hopefully be made even better with https://bugzilla.mozilla.org/show_bug.cgi?id=1852752

this is only a choice of 1.1.1.1 or 8.8.8.8 that i can manually enter in settings, poitless i guess

Unfortunately we never got to choose the resolver, and now it just stopped providing accurate results altogether.

This use to work... but now no longer works.

Wow! A DNSSEC extension that works! And no extra steps to install either.

used to display info and change but now it just always stays at NOPE doubt it's nope and 99% sure it's not me causing it.

Recently the Addon shows my Domain as "not secure by DNSSEC". But 3 Website to test the DNSSEC status says the Domain is secured by DNSSEC.

No longer works. Was good in the past, but these days say 100% of websites are not secured by DNSSEC, which is outright wrong.

Thank you for this add-on. I just hope (since it isn't a "recommended" extension) that it is trustworthy. Aside from that concern, it serves its purpose. It would be nice if Firefox had built-in DNSSEC validation.

This add on works well, however there are some issues as pointed out by other reviewers. I would like to note that ECDSAP256SHA256 works for me. It would also be nice if the add on verified https sites with DANE pinned certificates.

It's great! And yes, would be even better once we have custom DNS, over TLS or not.
But this is a feature I have been waiting for so long, so I'm not going to hide my current feeling about this extension, it's awesome!!

Well there, the future has not come yet?

It will be nice to choose a custom DNSSec, I don't trust on google, and some ISP redirect the 1.1.1.1 to his own DNS.

Using Cloudflare and Google for validation is not a good idea.
But also, validation fails for some kind of signatures, exemple: those using ECDSAP256SHA256.

I would give at least 4 stars, if it would use my local resolver instead of using google/cloudflare for DNS lookups.

Reason behind the downgrade:
1. it introduces a single point of failure:
if either of those sites can't answer, _ALL_ users of this extension (who have configured that site) can't use it, if it would use the local resolver and that failed it would be just the users of the local machine who experience that problem.

2. it is a privacy hazard:
a hacker needs to crack only a single (ok: two) machine(s) to get a complete log of who on this world tried to communicate with which web server....
if it would use the local configured resolver that _might_ still be a problem, depending on the configuration of said resolver, but mostly (I hope) those will contact multiple authoritative servers to walk from the root to the leaf containing the desired information and only the _last_ server will know which site I wanted to contact, but there it's irrelevant, since _that_ site knows it anyway.... (btw.: _THIS_ is the reason why I disabled this extension)

3. it can't verify local domains
according to 'dig' my own domains are DNSSEC enabled and working correctly, still your extension reports them as unsigned because there is no global glue record, as such while it is reachable from the world (via dyndns), the world doesn't see the DNSSEC information stored on my local dns-server.

Please let the user choose (a text input) his own DNS resolver(s)