Skip to main content

Curated Blocklists

Comprehensive DNS filtering lists for threat protection and content control.

What Are Curated Blocklists?

Curated blocklists are carefully maintained lists of domains that are known to host malicious content, trackers, or other unwanted material. These lists are used by DNS providers and filtering systems to automatically block access to harmful websites.

Unlike automated systems, curated lists are maintained by human experts who review and verify each domain before adding it to the list, ensuring high accuracy and minimal false positives.

Types of Blocklists

Malware Protection

  • • Virus and malware distribution sites
  • • Phishing and scam websites
  • • Botnet command and control servers
  • • Cryptocurrency mining scripts

Privacy Protection

  • • Advertising and tracking domains
  • • Analytics and data collection sites
  • • Social media trackers
  • • Third-party data brokers

Content Filtering

  • • Adult content (optional)
  • • Gambling and gaming sites
  • • Social media platforms
  • • Entertainment and streaming

Security Focused

  • • Known malicious IP addresses
  • • Suspicious domains and subdomains
  • • Command and control infrastructure
  • • Exploit kit distribution sites

Popular Blocklist Sources

StevenBlack's Unified Hosts

A comprehensive hosts file that combines multiple blocklists for maximum protection.

View on GitHub →

OISD Blocklist

Optimized Internet Service Delivered blocklist focused on ads and trackers.

Visit OISD →

AdGuard DNS Filter

Comprehensive filter for blocking ads, trackers, and malicious domains.

View on GitHub →

How to Use Blocklists

1

Choose a DNS Provider

Select a DNS provider that supports custom blocklists or uses curated lists.

2

Configure Your Device

Set up your device to use the DNS provider with blocklist protection.

3

Test and Verify

Test the configuration to ensure it's working correctly and not blocking legitimate sites.

Best Practices

  • • Start with well-maintained, reputable blocklists
  • • Test thoroughly before deploying in production
  • • Monitor for false positives and adjust as needed
  • • Keep blocklists updated regularly
  • • Use multiple layers of protection
  • • Document your configuration for future reference