The Immunity Network
Every customer makes every other customer harder to attack, without anyone sharing their traffic, and without anyone being able to weaponize the network against a victim.
–attackers currently shared
–reports in the last 24 hours
–contributing organizations (rounded down)
–hours before every entry expires
Live from the network. Counts are rounded so that no single customer can be identified from them.
How poisoning is prevented
- Independent confirmation. An address is published only after at least three different organizations report it.
- Reputation. When a customer undoes a block, its report is withdrawn and its weight drops; low-weight reporters stop counting.
- Expiry. Every published entry has a time-to-live; nothing is blocked forever on hearsay.
- Never-block list. Public DNS resolvers, AWS, Google Cloud, Cloudflare and Fastly ranges, and our management plane can never be published, however many reports arrive.
- Your dial still decides. A shared indicator is a reason, not an order: it is enforced only at autonomy level 3 or above, after your own blast-radius check.
Privacy and integrity
- Only the attacker's IP address and a reason category leave your organization. No traffic, no hostnames, no reporter identity.
- Contributing is opt-in per organization and can be switched off at any time.
- The feed is signed with Ed25519; hosts verify it against the key they pinned at enrollment and reject stale or altered feeds.
- Air-gapped and regulated customers can run a private, self-hosted hub instead, and federate it with this network if they choose.
Run your own hub, and join this one if you choose
A self-hosted control plane runs its own Immunity Network across its own organizations. That suits an MSP and its customers, a group of companies, or an air-gapped site. A hub can also be connected to the global network in two separate ways, each enabled by us on request.
- Receive. Your hub downloads the global feed and checks its Ed25519 signature against a key you pinned yourself. It refuses stale or replayed feeds, and every entry still passes your own never-block list.
- Contribute. Under a signed contribution agreement, your hub sends a signed list of first-hand reports, meaning attackers your organizations saw themselves, never ones it learned from us. Only addresses and reason categories are sent.
- Counted once. However many organizations your hub serves, it counts as one reporter. It loses weight when its reports are withdrawn, and federated hubs together can never publish an address without at least one of our own customers confirming it.
- Revocable. Access is a credential we can revoke at any time. Revoking it withdraws that hub's reports immediately.