Protective DNS for UK small businesses: what's actually available
Protective DNS blocks lookups of known-malicious domains before your device connects to them, but the UK's National Cyber Security Centre (NCSC) runs its own free Protective DNS service only for the public sector and schools; a typical small business doesn't qualify. AdminKit explains what NCSC's own guidance recommends instead.
By AdminKit team, Netbase JSC · Updated
Key takeaways
- Protective DNS is a resolver that refuses to answer lookups for known-malicious domains, so a device never gets the address it would connect to. Every device pointed at it is covered without installing anything.
- NCSC’s free PDNS is for the UK public sector and, through PDNS for Schools, for schools and the organisations that provide their DNS. A typical small business does not qualify.
- NCSC’s guidance for the private sector says to procure a commercial service, and lists what to look for in a provider.
- Options range from a free public blocking resolver to paid tiers with per-device policy and reporting, to a service built and run for you.
- It is one layer. Devices or browsers that use their own resolver, including DNS over HTTPS, skip it unless you configure them not to.
What does a protective DNS resolver do with each request?
It checks the domain in each lookup against threat intelligence and, if the domain matches, refuses to return a normal answer, so the connection never starts. Lookups for everything else are answered as usual.
Protective DNS (sometimes written PDNS) is a recursive DNS resolver that checks every domain lookup against threat-intelligence lists before answering, blocking the lookup outright if the domain is known-malicious: malware distribution, phishing, or the command-and-control infrastructure that malware already on a device would otherwise use to “call home.” NIST’s Secure DNS Deployment Guide (SP 800-81r3) describes the usual block response as an answer saying the name does not exist, such as NXDOMAIN, and notes that implementations can also log queries that trigger a policy as a sign of possible infection. CISA’s description of its own Protective DNS Resolver adds the other common responses: the service “blocks, redirects, or sinkholes the query response” and sends an alert.
Device asks: www.example.com -> not on any list -> normal answer (A/AAAA)
Device asks: bad-domain.example -> matches threat feed
Resolver: returns NXDOMAIN, or a block/sinkhole address
Resolver: logs the device, the domain and the time
Result: the connection to the malicious host never starts
Because it works at the DNS layer, it protects every device that’s configured to use it, without needing software installed on each one, and it can catch an already-compromised device trying to reach out, not just stop an initial infection. It’s a detection and blocking layer, not a replacement for a firewall, antivirus, or patching: it only ever sees and acts on domain names sent to the resolver you configure, nothing else.
Who can use the NCSC’s own PDNS service?
UK public sector organisations, plus schools and the bodies that supply DNS to schools. A typical small business is not on the list.
The UK’s National Cyber Security Centre (NCSC) has run its own Protective DNS service since 2017 as part of its Active Cyber Defence programme, and per NCSC’s own PDNS information page, it has resolved over 2.5 trillion queries and prevented access to over 1.5 million malicious domains at the time of its most recent published figures. That scale is real, but the eligibility is specific: NCSC’s PDNS was built for, and is mandated for use by, UK public sector organisations — central government departments, and more broadly local government, the NHS, and emergency services.
Since a phased rollout that began 26 October 2023, NCSC extended a free “PDNS for Schools” offering too, with a three-year delivery contract awarded to Cloudflare Inc. (working with Accenture) announced in April 2024, per NCSC’s own announcement. Combining NCSC’s PDNS eligibility with the PDNS for Schools categories in NCSC’s own blog post introducing that service:
| Organisation | NCSC service | Eligible? |
|---|---|---|
| Central government, local government, NHS, emergency services | PDNS | Yes |
| Local authorities or eligible public sector networks in Scotland, Wales and Northern Ireland that provide DNS to their schools | PDNS for Schools | Yes |
| Local authorities in England that provide DNS to their maintained schools | PDNS for Schools | Yes |
| School internet service providers | PDNS for Schools | Yes |
| Multi-academy trusts, academies or independent schools that don’t receive DNS from any of the above and can implement it themselves | PDNS for Schools | Yes |
| A shop, trades business, professional practice or small manufacturer | Neither | No |
NCSC’s own guidance page, titled “Protective DNS for the private sector,” says this directly: it is aimed at private sector organisations that do not qualify to use NCSC’s PDNS, and it states clearly that if an organisation does qualify for the government service, a commercially procured protective DNS service should not be treated as a substitute for it. In other words, NCSC isn’t silent on private-sector protective DNS — it has a dedicated page for it, and that page’s message is “go and procure a commercial service,” not “here’s how to apply.”
What does NCSC recommend to private-sector organisations?
NCSC’s private-sector guidance says to choose a commercial provider against three criteria: it should be trusted, with demonstrable knowledge and experience in DNS and cyber security; able to show it understands and actively blocks the kinds of threats PDNS is meant to catch; and able to give assurances that its deny lists and detection capability are kept current against new threat intelligence, not left static. Those criteria are a reasonable checklist to apply to any provider below, not just a formality.
NCSC’s separate advice for small and medium-sized organisations also points toward tools with no DNS angle but worth knowing about alongside protective DNS: the free Cyber Action Toolkit and Check Your Cyber Security tool for a general self-assessment, Exercise in a Box for testing incident response, and Cyber Essentials, NCSC’s government-backed certification built around five baseline technical controls, as the minimum standard NCSC recommends for organisations of any size. GOV.UK’s Cyber Essentials overview describes the scheme as a set of standard technical controls suitable for all organisations, of any size, in any sector.
Which protective DNS options can a UK small business actually buy or use?
- Quad9 — free, no account or sign-up, run by the non-profit Quad9 Foundation (backed by the Global Cyber Alliance, IBM and others per its own site), blocking lookups of malware, phishing, spyware and botnet domains from an updated threat list, with a stated no-logging privacy policy. There’s no business tier or per-device dashboard — it’s the same free public resolver for a household or a business, which makes it a reasonable no-cost baseline but not a managed solution with reporting.
- NextDNS — per its own pricing page, the free tier covers 300,000 queries/month with unlimited devices and configurations and every feature available, dropping only to unfiltered resolution (not an outage) once the monthly quota is used. Its paid Pro plan (€1.99/month or €19.90/year) removes the query cap; its Business plan is listed at €19.90/month or €199/year per 50 employees and adds email support, which is sized specifically for a small-to-mid business rather than a single household.
- Cloudflare Gateway (part of Cloudflare Zero Trust) — Cloudflare publishes a free plan for Zero Trust, including Gateway’s DNS-policy filtering, aimed at small teams, with per-seat pricing applying once you grow past it; check Cloudflare’s own Zero Trust plans page for the current free-tier seat limit and feature set, since Cloudflare’s pricing pages are updated independently of this guide.
- Control D — per AdminKit’s own comparison with NextDNS and Control D, Control D states a 99.98% malware block rate on its own homepage and offers native filtering apps across major operating systems; its free trial requires creating an account, unlike Quad9’s no-signup approach.
- Cisco Umbrella — a DNS-security product built for organisations of any size up to large enterprise, per Cisco’s own product page; it offers a 14-day free trial rather than a permanent free tier, which makes it a heavier commitment to evaluate than the free options above.
The same options grouped by type:
| Option type | Examples on this page | Cost to start | What you get beyond blocking |
|---|---|---|---|
| Free public blocking resolver | Quad9 | Free, no account | Nothing to manage; no dashboard or business tier |
| Configurable resolver with free and paid tiers | NextDNS, Cloudflare Gateway | Free tier, then paid plans | Per-device policy and reporting; plans sized for small teams |
| Vendor security product | Control D, Cisco Umbrella | Account or time-limited trial | Native apps, vendor support |
| Built and run for you | AdminKit Protective DNS (Netbase) | Scoped engagement | Per-site or per-device blocking with every block logged |
Pick based on what you actually need: Quad9 if you want a free blocking resolver with nothing to manage; NextDNS or Cloudflare Gateway if you want per-device policy, reporting, or a plan explicitly sized for a small team; Control D or Cisco Umbrella if you want a vendor-backed product with native apps and support, and are willing to create an account or run a trial to get there. Check current pricing and limits on each provider’s own page before deciding, since all of them can and do change independently of when this guide was last updated.
What should you ask a provider before you switch?
Ask how it blocks, what it logs, and what happens when it fails. NCSC’s criteria cover trust and threat intelligence; NIST SP 800-81r3 adds practical points worth turning into questions:
| Question | Why it matters |
|---|---|
| Where does your threat intelligence come from, and how often is it updated? | NCSC’s criteria call for deny lists kept current, not static. |
| Do you inspect all record types, not only A and AAAA? | NIST says a protective DNS service should be able to analyse all record types, such as MX, SOA and TXT. |
| Can we see which device made a blocked lookup, and export the logs? | NIST says blocked queries should always be logged, and recommends feeding those logs into your wider security monitoring. |
| What happens if your service is unreachable? | NIST notes that a setup that fails open falls back to ordinary, unfiltered resolution. |
| Do you support DNS over HTTPS or DNS over TLS for our devices? | Encrypted DNS to the protective resolver keeps lookups private on the way there. |
How do you check which resolver your devices actually use?
Run nslookup on a device and read the Server line: that is the resolver that answered. If it isn’t the protective resolver you configured, the device isn’t protected.
Example output (illustrative, documentation addresses):
$ nslookup example.com
Server: 192.0.2.53
Address: 192.0.2.53#53
Non-authoritative answer:
Name: example.com
Address: 203.0.113.10
Compare the Server address with the resolver your router hands out and with your provider’s published addresses. A block usually shows up as a “can’t find” or NXDOMAIN reply for a domain your provider lists as blocked, though some services return a block-page address instead. Router settings, a VPN, or a device with a hardcoded DNS server can all send lookups somewhere else; the DNS resolver test page walks through the manual check, and is my router’s DNS hijacked? covers the case where the router itself has been changed.
Can browsers and apps bypass protective DNS?
Yes. An application with its own DNS over HTTPS (DoH, RFC 8484) or DNS over TLS resolver can skip the operating system’s resolver, and with it your protective resolver.
NIST SP 800-81r3 describes this as an application-layer stub resolver that “bypasses the OS resolver”, common in modern browsers, and says organisations may need to configure such applications so the local resolver used for control and logging is not bypassed. Its suggested controls: block outbound plain DNS except from authorised resolvers, block unapproved DNS over TLS on TCP port 853, block known public DoH services (harder, because DoH shares port 443 with ordinary HTTPS), and use device management to stop users choosing an unapproved encrypted DNS service. Chromium’s DoH design notes say Chrome’s automatic mode upgrades to the current DNS provider’s own DoH server rather than switching provider, and that managed deployments should be opted out automatically. For the privacy side of that trade-off, see DoH vs DoT.
Where does AdminKit’s Protective DNS fit?
AdminKit Protective DNS is a filtering resolver that Netbase builds and runs for your network as a custom engagement, for shops, small offices and small industrial sites that want malicious-domain blocking per site or device, with every block logged, without buying new hardware — talk to our team to scope it. It sits alongside the options above rather than replacing them: a UK small business that wants a self-serve filter can sign up to one of the services listed, and one that wants it built and run for them can talk to Netbase. Either way, AdminKit’s free DNS lookup tool is useful for understanding your current DNS setup while you evaluate a provider, and the DNS resolver test page (see also best free DNS leak test tools) shows how to confirm which resolver your devices actually use. For a wider view of free tools that check a domain’s DNS and mail records, see AdminKit’s roundup of the best free DNS and email deliverability checkers.
What’s the bottom line for a UK small business?
If you run a typical UK small business — not central or local government, the NHS, or a school covered by PDNS for Schools — NCSC’s own free Protective DNS service isn’t available to you, and NCSC’s own guidance says so directly rather than leaving it ambiguous. The practical path is a commercial protective DNS provider, chosen against NCSC’s own criteria (trusted provider, demonstrable security expertise, actively maintained threat intelligence), sized to what you actually need: a free baseline resolver, a reporting-capable paid tier, or a vendor-backed product with support. This guide is part of AdminKit’s DNS cluster of DNS guides and tools. For the general, non-UK version, including router-level setup and how to test it, see protective DNS for small business.
Trademarks belong to their respective owners; AdminKit is not affiliated with the NCSC, Quad9 Foundation, NextDNS, Cloudflare, Inc., Control D, or Cisco Systems, Inc.
This guide is general information, not a security audit of your specific network — see our disclaimer for what AdminKit's guidance does and does not commit to.
Frequently asked questions
Can a UK small business sign up for NCSC's free PDNS service?
Generally no. NCSC's Protective DNS (PDNS) was built for public sector organisations — central and local government, the NHS, emergency services — and, since a phased rollout that began 26 October 2023, for schools and the local authorities, school internet service providers, multi-academy trusts, academies and independent schools that provide their DNS. NCSC's own guidance page for private sector organisations states plainly that it is aimed at the organisations that do not qualify for NCSC's PDNS, and that if an organisation does qualify, a commercially procured protective DNS service should not be treated as a substitute. A typical small business outside those categories should plan on a commercial provider, not the government service.
Is there a completely free protective DNS option a small business can use today?
Yes — Quad9, run by the non-profit Quad9 Foundation, is free with no account or sign-up and blocks lookups of domains on its threat-intelligence lists (malware, phishing, spyware, botnets), per its own site. It's a straightforward, no-cost baseline for blocking known-bad domains across any device you point at it, though it has no per-device dashboard, reporting, or business-specific support tier — it's the same free consumer resolver for everyone.
What if we need per-device policies or reporting, not just a blocking resolver?
That's where a paid or business-tier option comes in. NextDNS's free tier covers 300,000 queries/month with unlimited devices and configurations and every feature unlocked, per its own pricing page; its Business plan (listed at €19.90/month or €199/year per 50 employees, with email support) is sized for exactly this. Cloudflare's Gateway, part of Cloudflare Zero Trust, offers a published free plan for small teams with DNS-policy filtering, before per-seat pricing applies beyond that. Compare features and current pricing on each provider's own site before committing, since both change pricing independently of this guide.
Does Cyber Essentials require a protective DNS service?
No. Cyber Essentials, NCSC's government-backed certification scheme, is built around five core technical controls (firewalls, secure configuration, access control, malware protection, and patch management) and does not itself mandate a protective DNS product. A protective DNS service can support the malware-protection control in practice, but it isn't a Cyber Essentials line item on its own.
How does a UK small business get AdminKit's Protective DNS?
Through a Netbase custom engagement: Netbase builds and runs AdminKit Protective DNS for your network — a filtering resolver that blocks known-malicious and command-and-control domains per site or device and logs every block, without new hardware. Talk to our team at /contact/. AdminKit's free DNS lookup tool helps you check your current setup while you compare it with the self-serve options above.
Does using a protective DNS service replace a firewall or antivirus?
No — it's one layer, not a replacement for the others. Protective DNS only sees and acts on domain name lookups; it has no visibility into traffic that bypasses the configured resolver (a hardcoded DNS server on a device, or a different protocol entirely) and does nothing for threats that don't involve a DNS lookup at all. NCSC's own small business guidance treats it as one control alongside device patching, access control, and backups, not a single fix.
Can a browser's DNS over HTTPS setting bypass protective DNS?
It can. NIST SP 800-81r3 notes that browsers and other applications with their own DoH or DoT resolver can bypass the operating system's resolver, so organisations may need to configure those applications to keep using the resolver that enforces policy. Chromium's design notes say Chrome's automatic mode upgrades to the current DNS provider's own DoH server rather than switching provider, and that managed deployments should be opted out automatically, with policies available to administrators.
Sources
- NCSC — Protective DNS (PDNS) information page
- NCSC — Protective DNS for the private sector (guidance)
- NCSC — PDNS new partnership announcement (Cloudflare/Accenture)
- NCSC — Introducing PDNS for Schools (blog post)
- NCSC — Cyber security advice for small to medium sized organisations
- Quad9 — homepage
- NextDNS — pricing
- Cloudflare — Zero Trust / Gateway plans
- Control D — homepage
- Cisco Umbrella — product page
- NIST SP 800-81r3 — Secure Domain Name System (DNS) Deployment Guide (March 2026)
- CISA — Protective Domain Name System (DNS) Resolver
- GOV.UK — Cyber Essentials scheme: overview
- RFC 8484 — DNS Queries over HTTPS (DoH)
- Chromium — DNS over HTTPS (DoH) design notes
Want AdminKit to watch this for you?
Free checks tell you the state today. Protective DNS and monitoring tell you when it changes.
Talk to an expert
Huy Nguyen (David), Founder & CEO, Netbase JSC
Ask whether this fix applies to your setup, or get a second pair of eyes on your DNS and mail records.