Different devices.
Different rules.
Target IPv4 and IPv6 networks, individual endpoints, or learned PTR hostnames. Keep global lists alongside focused assignments.
Understand precedence →SELF-HOSTED · OPEN SOURCE · CLIENT-AWARE
Your network.
Your rules.
One clear policy.
Give every device the DNS policy it needs. Manage block lists, exceptions, and schedules from one place—with a clear explanation for every decision.
Built to work alongside Technitium DNS Server.
Actual console · illustrative sample data
YOUR INFRASTRUCTURE, CONNECTEDTechnitium DNS→Blockinator policy API→Allow / block decision
POLICY WITH CONTEXT
More control.
Less guesswork.
Apply the right rules to a client, a hostname, or an entire network. Then see exactly why a query was allowed, blocked, or whitelisted.
Different devices.
Policy that follows
your day.
Use recurring weekly windows, overnight schedules, and a timezone of your choice on lists and targets.
Set a schedule →See the reason
behind a decision.
Preview policy in the tester, trace matches in Query Log, and explore traffic and response-time statistics.
Follow a decision →A CLEAR DIVISION OF WORK
Your DNS server resolves.
Blockinator decides.
Blockinator is an HTTP policy service. The companion Technitium plugin sends query metadata, receives a decision, and enforces the DNS response.
See how it fits together →- 01DNS clientA device asks for a domain
- 02Technitium + pluginSends metadata to Blockinator
- 03BlockinatorEvaluates targets, lists & schedules
- 04Resolver responseContinues resolution or returns a block
FROM CHECKOUT TO CONTROL
A practical place to start.
MAKE IT YOURS
Put your policy in place.
Start with Docker Compose, connect your resolver, and test your first rule.