Bewertungen für DNSSEC
DNSSEC von Antoine POPINEAU
Bewertungen von Firefox-Benutzer 18361289
Bewertet mit 3 von 5 Sternen
von Firefox-Benutzer 18361289, vor 8 MonatenCan hopefully be made even better with https://bugzilla.mozilla.org/show_bug.cgi?id=1852752
39 Bewertungen
- Bewertet mit 2 von 5 Sternenvon Korwin, vor 4 MonatenWhile 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."
- Bewertet mit 4 von 5 Sternenvon Wolfizen, vor 6 MonatenResults 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.
- Bewertet mit 1 von 5 Sternenvon PSYCHOPATHiO, vor 9 Monatenthis is only a choice of 1.1.1.1 or 8.8.8.8 that i can manually enter in settings, poitless i guess
- Bewertet mit 2 von 5 Sternenvon Popi, vor einem JahrUnfortunately we never got to choose the resolver, and now it just stopped providing accurate results altogether.
- Bewertet mit 5 von 5 Sternenvon Firefox-Benutzer 7035052, vor 2 JahrenWow! A DNSSEC extension that works! And no extra steps to install either.
- Bewertet mit 2 von 5 Sternenvon CognitiveFeline, vor 3 Jahrenused 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.
- Bewertet mit 1 von 5 Sternenvon ploedman, vor 3 JahrenRecently 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.
- Bewertet mit 2 von 5 Sternenvon MarSanMar, vor 3 JahrenActualmente, esta extensión no funciona. La usé mucho tiempo y estaba contento con su funcionamiento, pero ahora mismo he tenido que buscar una alternativa.
- Bewertet mit 5 von 5 Sternenvon Jernej, vor 3 Jahren
- Bewertet mit 1 von 5 Sternenvon Firefox-Benutzer 13662450, vor 4 JahrenNo longer works. Was good in the past, but these days say 100% of websites are not secured by DNSSEC, which is outright wrong.
- Bewertet mit 4 von 5 Sternenvon Trashify, vor 5 Jahren
- Bewertet mit 5 von 5 Sternenvon Asclepius, vor 5 JahrenThank 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.
- Bewertet mit 5 von 5 Sternenvon Boris Volkov, vor 5 Jahren
- Bewertet mit 4 von 5 Sternenvon Firefox-Benutzer 15136226, vor 5 JahrenThis 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.
- Bewertet mit 4 von 5 Sternenvon Firefox-Benutzer 14672905, vor 5 JahrenIt'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!! - Bewertet mit 3 von 5 Sternenvon Firefox-Benutzer 13680056, vor 5 JahrenIt 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.
- Bewertet mit 5 von 5 Sternenvon Firefox-Benutzer 15299958, vor 5 Jahren
- Bewertet mit 1 von 5 Sternenvon Renaud, vor 6 JahrenUsing Cloudflare and Google for validation is not a good idea.
But also, validation fails for some kind of signatures, exemple: those using ECDSAP256SHA256. - Bewertet mit 5 von 5 Sternenvon Firefox-Benutzer 14754691, vor 6 Jahren
- Bewertet mit 2 von 5 Sternenvon Firefox-Benutzer 14514156, vor 6 JahrenI 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. - Bewertet mit 2 von 5 Sternenvon IPv777, vor 6 JahrenPlease let the user choose (a text input) his own DNS resolver(s)
- Bewertet mit 5 von 5 Sternenvon Firefox-Benutzer 13310694, vor 6 Jahren