No! We designed the Blacklist system to particularly avoid latency. Here is how we did it:
- Your organization’s specific blacklist is stored locally. These are the sites that you have manually added. Therefore the only latency is the microseconds it takes in processing. This is literally imperceptible, and less than a millisecond in processing time.
- Sites that aren’t stored locally are checked asynchronously using our Blackcat engine. Let’s pretend the student is making a request to playboy.com. The request is sent to our servers at the same time that a request is sent to playboy.com. But, due to our lightning fast CRC32 lookups our server responds in a matter of milliseconds and redirects the request to our servers if the site in the case that it’s inappropriate. Otherwise, we do not redirect the request, and it goes through as normal, without any latency.