That's one of the reasons why I created dnsadblock.com (besides the fact that I couldn't use it while traveling). It shows a page with a message if the request

That's one of the reasons why I created dnsadblock.com (besides the fact that I couldn't use it while traveling). It shows a page with a message if the request was blocked (ex: http://tracking.blocked.dnsadblock.com/#/ http://tracking.blocked.dnsadblock.com/#/) but only for regular http traffic because I don't want to go down the route of playing with certificates to make it work on https. I think I managed to have the blacklist/whitelist easier though by creating an activity log page that shows exactly what was blocked and allowed and on what device - in near real-time. Fun project at first but I didn't know what I was going into at first. It is a bit frustrating when starting but, once you start whitelisting what was blocked by mistake, you will see that it gets easier, almost unnoticeable by a week or so. I always had uBlock and disconnect.me and it still blocks, somewhat consistent, about 16% of the traffic which is a big number considering.