Oh yes, perfectly legit. — we're on the same page on this point.That happens on sites using Extended Validation (EV) certificates and this is normal when using HTTPS filtering in AG for Windows/Mac/Android. Other than the green text, the site is still secure (look at the lock icon) due to it using AG's certificate (which is needed for HTTPS filtering) instead of the site's EV certificate.
Additionally, it's surprising that `mozilla.org` is filtered, it's in the default list of HTTPS exceptions. Have you changed anything there?
Yep, mozilla.org is being filtered because it's been removed from my HTTPS Exclusions — actually, have deleted all of the natively excluded sites since I prefer to have a complete manual override.There's no way to get the green text to show while using HTTPS filtering, other than using the Do not filter websites with EV certificates option in AG's settings > Network section. Of course, using that option means sites using EV certificates will not get filtered (and thus no ads, trackers, etc. are removed).
Unfortunately it's not possible, hence the setting to not filter sites with EV certificates.would really appreciate if the green Firefox (SSL) site label could somehow be left visible — or alternatively at least, if an AdGuard label could displace the same.
In my opinion, this is a bad idea. There are websites that need to be added to the HTTPS exclusions or else they don't function correctly. Plus, a lot of the domains in the HTTPS exclusions list are banking institutions, which from a security perspective is a very good idea to have them excluded from AG's filtering. For example removing mozilla.org from the HTTPS exclusions, if I recall correctly, breaks Firefox extension/addon updates and Firefox Sync, if you use that. I think it might break Firefox/Nightly updates too, again, if I recall correctly.Yep, mozilla.org is being filtered because it's been removed from my HTTPS Exclusions — actually, have deleted all of the natively excluded sites since I prefer to have a complete manual override.
Generally speaking, yes — that does affect quite a few HTTPS sites including mozilla.org . . . . . however, in my own case, have created the necessary exclusion rules wherever required.In my opinion, this is a bad idea. There are websites that need to be added to the HTTPS exclusions or else they don't function correctly. Plus, a lot of the domains in the HTTPS exclusions list are banking institutions, which from a security perspective is a very good idea to have them excluded from AG's filtering. For example removing mozilla.org from the HTTPS exclusions, if I recall correctly, breaks Firefox extension/addon updates and Firefox Sync, if you use that. I think it might break Firefox/Nightly updates too, again, if I recall correctly.Yep, mozilla.org is being filtered because it's been removed from my HTTPS Exclusions — actually, have deleted all of the natively excluded sites since I prefer to have a complete manual override.![]()