ScoutDNS
Insights tables keep their headers and show when they're loading commercialThe section your link pointed to isn't on ScoutDNS's page any more, so we've brought you to the top.
ScoutDNS is a DNS filtering and threat protection service for businesses, MSPsMSPsA managed service provider, a company that operates IT services for customers. It may manage systems, networks, backups or other ongoing technology needs., schools, and nonprofits that blocks unwanted content and malicious domains.
Summary
ScoutDNS is a commercial DNS filtering service run as cloud-based secure access infrastructure, letting organizations enforce allow/block policies without hosting anything themselves. Policies can be built from custom lists with per-entry match or subtree scope, wildcard entries covering a domain and its subdomains, and comments documenting why a rule exists, while Zero Trust TLDTLDThe rightmost label in a domain name (e.g., .com, .gov, .uk), maintained by IANA's root zone. Cyber tools filter or pivot on TLDs to scope scans, flag suspicious registrations, or classify traffic by geography or type. filtering can auto-generate an allowlist from 30 days of real query traffic and each policy gets a 0–100 Secure Score with a breakdown of what to fix. A Deployments view maps every policy assignment across sites, profiles, and personas, sites report health from WAN and relay state rather than query volume, and an MSPMSPA managed service provider, a company that operates IT services for customers. It may manage systems, networks, backups or other ongoing technology needs. dashboard gives a cross-tenant view for managed accounts, which points this squarely at MSPs and IT teams managing DNS security across multiple sites or clients rather than at individual administrators.
ScoutDNS is a DNS filtering and threat protection service for businesses, MSPs, schools, and nonprofits that blocks unwanted content and malicious domains.
How ScoutDNS helps
Which sites or client accounts have a policy gap right now?
the Deployments view lists every policy assignment across sites, profiles, and personas in one account-wide table, so a site running the wrong or no policy is visible without opening each one individually
How strong is a given policy actually configured to be?
each policy carries a 0–100 Secure Score with a per-item breakdown of what to enable to raise it, turning a vague sense of exposure into a specific list of settings to fix
Which of my sites are down right now, and is it the network or the DNS relay?
site health is reported as stateful up/down state derived from WAN and relay status rather than inferred from query volume, so a quiet site is not confused with an offline one
Which domains should a Zero Trust allowlist actually include for this organization?
the TLD filter can build the allowlist automatically from 30 days of that organization's real query traffic instead of starting from a guessed list
Why was this domain ever allowed or blocked?
a comment can be attached to any list entry at the time it is created, so the reasoning is visible later instead of being lost to whoever wrote the rule
Does a rule cover just this one host or its whole domain?
each custom list entry is explicitly scoped as match or subtree, and a wildcard entry now covers the domain and all its subdomains in one line, so the reach of a rule is stated rather than assumed
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 ScoutDNS, 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 ScoutDNS 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…
Releases
6 entries
No entries match these filters.
- October 20261
- September 20262
- August 20261
- June 20262
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 →