Don Marti<p>Point of order: if you use <a href="https://federate.social/tags/adBlocking" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>adBlocking</span></a> as a security tool, then DNS filtering alone is _not_ adequate protection.</p><p>The biggest current <a href="https://federate.social/tags/malvertising" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>malvertising</span></a> issue is search ads, which need either element blocking in the browser, or blocking of the click-through redirect.</p><p>Blocking the redirect can be done without an ad blocker on the client if you deploy an enterprise policy. (One advantage of policies over extensions: they cover all profiles and all user accounts)</p><p><a href="https://blog.zgp.org/search-malvertising-protection-using-enterprise-policies/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">blog.zgp.org/search-malvertisi</span><span class="invisible">ng-protection-using-enterprise-policies/</span></a></p>