zveloDB™ is the market’s premium URL database and web classification service, providing best-in-class accuracy and coverage. The zveloDB supports nearly 500 topic-based, malicious, phishing, objectionable and sensitive categories, powering the world’s leading Web and DNS Filtering, Endpoint Security, Brand Safety, Contextual Targeting, Subscriber Analytics, and other applications.

Advantages of DNS RPZ | How It Works

Advantages of RPZ: Basics & Common Configurations

Since the release of BIND 9 in 2010, RPZ has proven a powerful technology for security and network management—allowing organizations to implement an additional DNS configuration layer. In fact, BIND is the most widely used Domain Name System software on the internet—making RPZ configuration options like integrating commercial feeds, blocklists, and URL databases like zveloDB™ all the more attractive. So let’s take a moment to revisit the advantages of RPZ.

Content as the New Clickbait: The Battle against News & Politics

Politics and News: The Growing Trend of Content as the New Clickbait

Over the past decade, the use of “clickbait” ads has become the norm in order to entice viewers to click on the ad and drive traffic to a publisher. Web surfers have grown accustomed to seeing the same types of clickbait ads and sponsored stories like the ones shown below with sensational headlines about curing cancer, stopping aging, improving your sex life and more.

Securely Logging & Tracing HTTP Requests in Go | zvelo

Securely Logging & Tracing HTTP Requests in Go

I was recently debugging a nasty issue in one of our backend services and needed to view the exact HTTP request & response being sent to an authentication server. Fortunately, Go’s standard library provides http.RoundTripper, httputil.DumpRequestOut & httputil.DumpResponse, which are great for dumping the exact out-bound request & the response. But since an authentication request contains credentials and a response contains a security token, it would have been insecure to record credentials & tokens in our logging systems. How could I securely exfiltrate the information I needed, while maintaining security and not requiring a whole lot of changes to my codebase or deployment environment?