Sophos DNS Protection
changelog-20261023-6000cc6e commercialThe section your link pointed to isn't on Sophos DNS Protection's page any more, so we've brought you to the top.
Sophos DNS Protection is a security service that blocks malicious websites and threats by filtering DNS queries at the network level.
Summary
Sophos DNS Protection is a commercial DNS filtering service that blocks access to malicious and unwanted domains at the network level, run as a hosted service rather than installed software. It is aimed at network and firewall administrators who need to enforce web-category policy across an organisation without deploying agents on every endpoint, fitting the network-defense space alongside other DNS-layer filtering controls. Policies work by category, and it recently split generative AI sites out of the general business-relevant grouping into their own Generative AI category, so admins can block or allow AI services separately from other business traffic, including an allowlist pattern that blocks the category broadly while permitting an approved domain list. With 13 releases in the tracked window and the latest just 16 days old, the product is under active, frequent development.
Sophos DNS Protection is a security service that blocks malicious websites and threats by filtering DNS queries at the network level.
How Sophos DNS Protection helps
Which devices on the network are trying to reach known-malicious domains?
every DNS query is checked against threat intelligence at resolution time, so lookups to malicious or compromised domains are blocked before a connection is made, without any agent on the requesting device
Can staff reach generative AI tools I haven't approved?
the Generative AI category can be blocked on its own while an allowed domain list carries the specific AI services that are sanctioned, so only the approved names resolve
Which web categories are actually being allowed or blocked across the organisation right now?
policies are defined per category group, so reviewing a policy shows the allow or block state for each category, including any that silently inherited their setting from a related category
Did splitting out a new category change what my existing policy allows?
a category introduced under an existing group takes on the current setting of the related category it was split from, so a policy that allowed the parent category will also allow the new one until it's reviewed and set separately
Am I enforcing consistent web-category policy across every site without deploying anything to each endpoint?
filtering happens at the DNS layer for the whole network from the hosted service, so a single policy governs queries network-wide rather than needing per-device agents
Languages
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
Five scores for Sophos DNS Protection, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Sophos DNS Protection puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Website history
sophos.com, every changeSophos's home page and 1 more page as they looked each month from September 2021 to October 2026: 12 renders, 3 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Releases
14 entries
No entries match these filters.
- October 20262
- August 20263
- June 20261
- May 20261
- February 20261
- November 20251
- April 20251
- March 20251
- January 20251
- October 20241
- June 20241
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.
Choose a badge style and copy the code →