Keep the blocklist. Start with managed DNS.

The public DNS resolver retires on July 31, 2026. The easiest replacement is NextDNS or Control D; self-hosting remains available for advanced users who want full control.

Use managed DNSCompare options

What is changing: the hosted resolver addresses are going away. The easiest path is a managed DNS provider; self-hosting remains available for advanced users.

Need the full context? Read the public resolver shutdown notice.

Pick the right path

Start with the card that describes your situation. Each card is clickable and takes you straight to the next useful place.

EasiestBest starting point

Use NextDNS or Control D

This is the easiest route for most people. Use the NextDNS importer below to sync the maintained hapara.fail blocklist into your own profile.

Preview provider pathAdvanced users

Self-host the DNS

More manual, more control. Use this path if you already run DNS infrastructure or want to manage every piece yourself.

Open self-hosting docsBuilding your own workflow?

Use the raw feeds

Pull the maintained blocklist directly from GitHub or jsDelivr for scripts, self-hosted stacks, and future import tools.

View feed URLs

Managed DNS importers

This is the easiest migration surface. The NextDNS importer fetches the live blocklist, converts it from ABP syntax, and adds block rules to the denylist plus exception rules to the allowlist.

NextDNS

Add every domain from the maintained hapara.fail blocklist to a NextDNS profile's denylist, while sending ABP allow rules to the profile's allowlist. Your API key is sent to a same-origin proxy only to call NextDNS and is not stored by this site.

Control D

Future goal: provide a Control D-ready import path that keeps the user experience close to self-hosting while staying managed.

Self-hosting for advanced users

If you want the most control, this is the path. It is more manual than managed DNS, but the docs stay canonical so setup details can evolve without making this page stale.

Run your own resolver

Use your own infrastructure, subscribe it to the hapara.fail blocklist, and point your devices or network at the resolver you control.

Open the self-hosting guide
  1. Choose a host. Use a small VPS, home server, or always-on machine.
  2. Deploy the resolver. Follow the docs instead of copying commands from this page.
  3. Point clients at it. Change device or router DNS settings once your resolver is ready.
  4. Keep the list updated. Subscribe to the maintained feed so changes flow in over time.

Blocklist sources

These feeds remain the source of truth. Use them manually today, and expect the future importer tools to read from the same maintained source.

jsDelivr

Good for clients that prefer a fast CDN-backed URL.

https://cdn.jsdelivr.net/gh/hapara-fail/blocklist@main/blocklist.txtOpen jsDelivr feed

GitHub raw

Best for automation that wants the canonical repository source.

https://raw.githubusercontent.com/hapara-fail/blocklist/refs/heads/main/blocklist.txtOpen GitHub raw feed

Still deciding?

Managed DNS is the easiest path.

Use NextDNS or Control D if you want the least friction. Self-hosting remains for advanced users who want maximum control.

Go to the managed path