Does the NextDNS "Google Safe Browsing" provide the same level of protection as in-browser "Google Safe Browsing"?
Thank you and cheers
Romain Cointepas and Olivier Poitrey , kindly invited to solve the mistery.
To clarify why I am asking...
I do not want the devices to make unnecessary connection to safebrowsing@google.
So, if NextDNS is providing full google safebrowsing functionality, then I can easily add safebrowsing.googleapis.com and sb.l.google.com to Denylist.
It does for all domain based rules. It does ignore paths rules (as DNS can’t see these).
I believe you have a typo?
as DNS can see these
as DNS can't see these
I was sure the safebrowsing worked only on domain hashes not paths. I was obviously wrong.