blocklist-mirror

This bouncer exposes CrowdSec's active decisions via provided HTTP endpoints in pre-defined formats.

  • Network Services
  • Tools & Utilities
This bouncer exposes CrowdSec's active decisions via provided HTTP endpoints in pre-defined formats. It can be used by network appliances which support consumption of blocklists via HTTP.

Platform availability

Available on 1 of 6 install platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)

Also on Docker Hub and GitHub

Health score

74/100 Good

Maintained
75last commit 2 days ago
Popular
8927,182 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
10060 MB minimum RAM, runs on ARM
How is this calculated?

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). Factors without data are left out and the rest are rescaled.

Availability: platform listings confirmed today, links checked today

GitHub stars
27,182
Open issues
8
Last commit
2026-10-07
Latest release
37522026.280.37009
License
GPL-3.0
Activity
rising

Checked yesterday - source: GitHub (hagezi/dns-blocklists)

Resources & Compatibility

Minimum requirements: 60 MB RAM. ARM (e.g. Raspberry Pi) is supported.

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

First-install notes

  • Choose the right .netset file Each .netset file is a plain-text list of IP ranges, organized by provider, country, or continent. Choose the exact file you need because different providers and regions contain different addresses, and the wrong file can block or allow far too much traffic. source
  • Load the list with ipset On Linux, use ipset (a fast tool for storing IP ranges) to load the .netset file before referencing it in iptables (the firewall rule engine). If the set name or file path is wrong, the firewall rule will not work correctly. source
  • Check before you block traffic The example uses a DROP rule, which blocks all incoming traffic from addresses in the ipset, so review the list and test carefully. If you block addresses you need, connections will silently fail and can lock out services. source
  • Unraid initial setup Create the config directory and file: run mkdir /mnt/user/appdata/blocklist-mirror, cd into it, then create cfg.yaml with nano. Copy in the contents of the cfg.yaml from the CrowdSec documentation page. Save, close, and start the container. source

Fetched yesterday - each note links to its source

Alternatives (2)

Checked 8 days ago - source: AlternativeTo

Common questions

How does blocklist-mirror expose its blocklist to other systems?

It exposes the blocklist through a webserver, which is the approach covered in OPNsense installation discussions for the CrowdSec blocklist-mirror bouncer.

Can firewalls subscribe to a self-hosted blocklist-mirror?

Yes. The source reports Fortigate and Check Point firewalls subscribed to a self-hosted mirror, successfully consumed the threat feed, and blocked threats.

Answers sourced from forum.opnsense.org, www.reddit.com

Community

Collected 9 days ago - public community threads