Project in development · Governed DNS lists

BitShield

In development

A DNS blocklist only really works when you know why every entry is on it. BitShield organises sources and rules by customer, site and profile, shows the effect of every change before it goes live and distributes the lists to resolvers in a controlled way.

In development A BitArmor project. Timing and availability have not yet been decided.

01The problem

Lists that grow without a memory

Multiple sources, exceptions added over time, changes applied without seeing their effect first: after a few months it is hard to say why a domain is on the list, or since when.

BitShield gives every list a traceable history: where an entry came from, which rule includes it, why, and when it was published.

02How it works

From sources to resolvers

Five steps, with a review before every publication.

  1. Sources

    Domain sources are organised in a single place.

  2. Rules

    Rules by customer, site and profile decide what goes in and what stays out.

  3. Preview

    Before publishing, you see exactly what enters and what leaves the list.

  4. Publication

    The published list remains available to consult, with the reason for every entry and a history of publications.

  5. Distribution

    Feeds reach the customer’s resolvers in a controlled way; those resolvers remain the ones already in use.

Illustrative diagram; no real data. Before publication, the preview compares the published list with the proposed change, entry by entry and with the reason for each.

03Features

What BitShield does

Built to manage DNS lists as a proper process, with review and a full history.

  • Sources in one place

    Domain sources are collected and managed together, rather than scattered across files and configurations.

  • Rules by customer, site and profile

    Each context has its own list, built from explicit inclusion and exclusion rules.

  • Preview before publishing

    Every change shows in advance which entries will join the list and which will leave it.

  • Searchable lists with reasons

    The published list can be searched and consulted, with the reason for every entry.

  • Publication history

    Every publication is tracked over time, so you can reconstruct when any entry changed.

  • Controlled distribution

    Lists reach the customer’s resolvers through controlled feeds, without replacing the existing DNS.

BitShield governs how lists are built and published. The blocking itself is still done by the customer’s resolvers, according to the published rules.

Want to know more about BitShield?

In development

Tell us how you manage DNS lists across your sites today. We’ll explain where the project stands and how it might help.

Prefer email? Write to [email protected].