One of the tools that we make publicly available, free of charge, is our Whitelist Assistant.
What is a Whitelist?
Let me answer that in context and in contrast to a Blacklist. There are two fundamental approaches to filtering in the context of website access.
Option 1: Allow all, block some. This is effectively a Blacklist. This is an approach where bad domains are disallowed.
Option 2: Block all, allow some. This is effectively a Whitelist. In this approach, only websites and domains explicitly listed can be accessed.
Why is Whitelisting so hard?
One of the key reasons that whitelists have been difficult to adopt in the past is because of the great deal of dependencies on non-obvious domains. Let’s say you wanted to whitelist our website at www.DNSthingy.com. In the old days, you would simply concatenate the www and make a whitelist entry of DNSthingy.com so that http://DNSthingy.com as well as http://www.DNSthingy.com would work.
It’s not quite that simple anymore, especially since a website could be a combination of several sources of information that “live” on different domains, and/or different servers.
For example, let’s say your business needs to interact on eBay and you’re on a whitelist system. You would need to whitelist all of these domains (if accessing from a commonwealth country, possibly more if you’re visiting from elsewhere):
bluekai.com (behaviour profiling)
facebook.com (to be able to like something)
akamaihd.net (Content Delivery Network)
turn.com (behaviour profiling)
frooition.com (ebay designer)
2o7.net (behaviour profiling)
A tool to make Whitelisting easier
For our own subscribers (or if you’re running your own whitelist system), we are facilitating a free Google Chrome Extension called Whitelist Assistant by DNSthingy. If you’re a DNSthingy subscriber, there are additional features such as integration into your subscriber account coming shortly.