Blocky

Blocky is a DNS proxy and ad-blocker for local networks written in Go that blocks ads and malware at the DNS level, with configurable blocklists and…

  • Network Services
  • Other
  • Security
  • Tools & Utilities
Blocky is a DNS proxy and ad-blocker for local networks written in Go that blocks ads and malware at the DNS level, with configurable blocklists and per-client allow/denylists for client groups such as kids or smart-home devices.

Platform availability

Available on 4 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

78/100 Good

Maintained
100last commit 23 days ago
Popular
777,077 GitHub stars
Easy to install
654 install platforms, install notes, Docker image
Light to run
404 GB minimum RAM, runs on ARM
Security check
79no serious findings, 1 minor, CI, tests, OpenSSF Scorecard 5.7/10

Availability: platform listings confirmed today, links checked 7 days ago

GitHub stars
7,077
Open issues
56
Last commit
2026-10-28
Latest release
v0.35.0
License
Apache-2.0
Activity
rising

Checked 22 days ago - source: GitHub (0xERR0R/blocky)

Resources & Compatibility

Minimum requirements: 4 GB RAM. ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Start it in the background Run docker-compose up -d to start the Blocky containers from your compose file and keep them running in the background. If you skip this, Blocky is not running and your devices can't get its DNS answers. source
  • Check it is answering After starting, run dig @<blocky-host> -p <dns-port> healthcheck.blocky A +short to confirm Blocky is alive. It should report NOERROR (meaning the DNS check succeeded), so you can tell a real problem from a normal answer. source
  • Make startup faster In your Blocky config, set upstreams.init.strategy to fast. This lets Blocky start answering while it checks its outside DNS servers (upstreams), so a slow network won't make first startup feel stuck. source
  • Create config.yaml Create a config.yaml file with your configuration before first start; all configuration options are documented on the configuration page. source

Fetched 37 days ago - each note links to its source

Alternatives (9)

  • 1.1.1.1 - Experience quick, private browsing with this top DNS resolver.
  • AdGuard DNS - Cloud-based DNS for blocking ads, trackers, and malicious domains, offering real-time stats, parental controls, and customizable filtering…
  • AhaDNS
  • Blokada - Blokada is the popular ad blocker and privacy app for Android and iOS.
  • Cisco Umbrella - Cisco Umbrella (formerly OpenDNS) provides the first line of defense against threats on the internet wherever users go.
  • Control D - Control D is a modern and customizable DNS service that blocks threats, unwanted content and ads - on all devices.
  • Google Public DNS - A free, global DNS resolution service that you can use as an alternative to your current DNS provider.
  • NextDNS - NextDNS protects you from all kinds of security threats, blocks ads and trackers on websites and in apps and provides a safe and supervised…
  • Quad9 - Quad9 is a free, recursive, anycast DNS platform that provides end users robust security protections, high-performance, and privacy.

Checked 51 days ago - source: AlternativeTo

Common questions

Does Blocky collect telemetry or hidden data?

No. The project states it has no telemetry, no data collection, and no hidden filtering.

How do I start Blocky in the background with Docker Compose?

Run docker-compose up -d to start the containers and keep them running in the background. If you skip this, Blocky is not running and devices cannot get its DNS answers.

How can I confirm Blocky is answering DNS after startup?

Run dig @<blocky-host> -p <dns-port> healthcheck.blocky A +short. It should report NOERROR, indicating the DNS check succeeded.

Can Blocky be used for DNS rebinding protection?

Yes. The source says self-hosted DNS servers can prevent rebinding attacks by filtering rebinding attempts at the resolver level, and it lists Blocky among servers with that protection.

Answers sourced from 0xerr0r.github.io, 0xerr0r.github.io, github.com, www.pistack.xyz

Community

Collected 53 days ago - public community threads