ComparisonDNS filtering alternatives
CleanBrowsing alternatives for venues
You will be able to decide whether CleanBrowsing, Cisco Umbrella or Purple Shield fits your venue estate, judged on policy scope, estate console, guest WiFi integration and running cost. You also get a five-step plan to move off CleanBrowsing with a DNS change, not a hardware project.
Watch the explainer
Purple Shield is the CleanBrowsing alternative to choose once you run more than one network. CleanBrowsing's published plans are built for families, schools and small organisations. Shield applies protective DNS per SSID, VLAN and venue from one dashboard, on Cisco Meraki, HPE Aruba, Ruckus or any other WiFi. Whitbread and AGS Airports already run it.
Which CleanBrowsing alternative suits a venue estate?
Purple Shield replaces CleanBrowsing for venue WiFi once you filter more than one network or more than one audience. The deciding factor is policy scope. A family filter assumes one network, one household and one set of rules. A venue estate has guest, staff and often point-of-sale networks, and each needs different rules.
All three options in this guide filter in the same place: the DNS lookup. A device asks a resolver for a domain name. The resolver answers or refuses before any connection opens. This placement catches threats a firewall misses, because the firewall only inspects traffic after the device already has an address to reach. The UK National Cyber Security Centre runs Protective DNS for public sector bodies on the same principle.
DNS filtering works in every option here. The real question is whether the product was built for a home router or for an estate of venues. An estate might run three SSIDs (the network names a device sees) at every site.
Each option has a distinct focus:
- CleanBrowsing focuses on families, schools and small organisations, from free preset filters to paid plans covering up to 25 networks.
- Cisco Umbrella focuses on enterprises standardised on the Cisco security portfolio.
Cisco has announced end of sale for Umbrella DNS on 31 January 2027, with its DNS security moving to Secure Access DNS Defense.
- Shield focuses on venue estates where filtering must follow SSIDs, VLANs, venues and the guest WiFi itself.
For the wider category, see our guide to DNS filtering alternatives.
What we compared CleanBrowsing alternatives on, and why
We scored three options: CleanBrowsing, Cisco Umbrella and Purple Shield. Every competitor cell comes from that vendor's own public product and pricing material. We describe how each option is priced but never quote a competitor price, because list prices change and rarely reflect what an estate pays.
We chose eight criteria. Each one maps to a question venue IT and operations teams ask in practice:
- Where filtering acts. Filtering at DNS resolution stops a threat before a connection opens. Filtering later in the path inspects traffic that has already left the device.
- Primary market. The audience a product is designed for shapes its defaults, its console and its support model.
- Policy scope. This is the smallest unit you can give its own rules. A VLAN (virtual local area network) separates traffic on shared hardware, so guest and staff devices never share a segment.
- Estate console. This covers whether one dashboard shows every site, or whether you log in per network.
- Threat coverage. Malware, phishing and newly registered domains are the threats guest networks attract.
- Content categories. These are the controls that keep adult or illegal content off a family restaurant's guest network.
- Guest WiFi integration. This asks whether filtering connects to the captive portal, the login page a visitor sees before getting online.
- Hardware. This covers whether you must install an appliance, an agent or nothing at all.
We excluded criteria where public material did not allow a fair like-for-like score. Ad blocking and bandwidth effect are the main examples. Where Purple publishes its own figures on those, we cover them in prose with attribution.
CleanBrowsing vs Cisco Umbrella and Shield at a glance
The matrix below scores each option on the eight criteria. The Purple column is highlighted. Read across a row to see the trade-off on one criterion, and down a column to see one product's shape.
| Criterion | CleanBrowsing | Cisco Umbrella | Purple Shield |
|---|---|---|---|
| Where filtering acts | DNS layer, before connection | DNS layer, before connection | DNS layer, before connection |
| Primary market | Families, schools, small business | Enterprises on Cisco Secure | Guest and staff WiFi estates |
| Policy scope | Per linked network or device profile | Per network, device or directory identity | Per SSID, VLAN and venue |
| Estate console | Account dashboard, profiles per network | Multi-org console for partners | One dashboard across every venue |
| Threat coverage | Security filter for malware and phishing | Malware, phishing and C2 via Cisco Talos | Malware and phishing domains |
| Content categories | Preset family and adult filters | Content categories by licence package | Categories set per network policy |
| Guest WiFi integration | Not offered | Not offered | Native with Purple Access and captive portal |
| Hardware | None; repoint DNS | None; optional virtual appliance or agent | None; any WiFi or native in Purple Access |
The first row is identical across all three columns, and that is deliberate. Every option filters at the same layer, so placement is not the differentiator. Scope, console and integration are where the options separate, and that is where a venue estate feels the difference.
Where the options differ for venue WiFi
Policy scope: networks, not households
CleanBrowsing applies a filter profile to a linked network or to a device. That model fits a home with one router. A hotel has a guest SSID, a staff SSID and a back-office VLAN for payment terminals. All three share one public IP address. A profile tied to that IP cannot tell them apart.
Cisco Umbrella adds more granularity. It scopes policy by network, device or directory identity, usually through a virtual appliance or connector on site.
Shield scopes policy per SSID, VLAN and venue. You can let a staff VLAN reach supplier portals while keeping the guest SSID on a stricter category set. The hardware does not change at any site.
Estate management: one console or many
A family filter rarely needs more than one dashboard view. Run 200 venues, though, and logging into each one becomes the bottleneck.
CleanBrowsing offers a partner console for managed service providers. Cisco Umbrella offers a multi-org console for partners. Both suit a reseller managing separate client organisations. Neither is designed around a single brand's estate of venues.
Shield gives you one dashboard across every venue, SSID and VLAN. A change to the guest policy for every pub in a group is one edit. Reports roll up across the estate, so you can see which sites see the most blocked threats.
Threat intelligence and detection speed
All three options block known malware and phishing domains. Umbrella draws on Cisco Talos threat intelligence. CleanBrowsing's security filter targets malware and phishing.
The open question is speed on new threats. Shield flags malicious domains at the DNS layer before connections open. On a guest network, that window matters. Phishing domains are often registered and used within days, and visitors bring whatever their devices have picked up elsewhere.
At St George's Healthcare NHS Trust, Shield blocks threats across a busy public network, where patients and visitors connect thousands of unmanaged devices.
Bandwidth and ad blocking
Venue bandwidth is shared, and adverts plus trackers consume a surprising share of it. With ad blocking enabled, Shield cuts data use by up to 44% and DNS queries by up to 62%, on Purple's own data.
For a stadium or airport, that reclaimed capacity goes back to passengers and fans. For a small café on a single broadband line, it can decide whether video calls work at lunchtime.
- Up to 44%less data with ad blockingPurple's own data
- Up to 62%fewer DNS queriesPurple's own data
- 80,000+live Purple venuesIn 90 countries
- 500M+logins a yearAcross global network
Guest WiFi integration
Neither CleanBrowsing nor Cisco Umbrella offers guest onboarding. Each is a filter that sits beside your guest WiFi. You run the captive portal, the consent capture and the filtering in separate tools, with separate logins and separate support contracts.
Shield runs standalone on any WiFi, or bolts onto Purple Access. Bolted on, filtering policy lives next to the captive portal, conscious-choice opt-ins and network policy. One team and one dashboard handle all three.
The diagram shows where Shield sits in the connection path.
A guest device joins an SSID, the network points DNS to Shield, Shield checks the policy for that SSID, VLAN and venue, then either allows the connection or blocks it before it opens, and logs every decision to one dashboard.
Connections
- Guest device joins SSID to Network points DNS to Shield
- Network points DNS to Shield to Shield checks policy (DNS query)
- Shield checks policy to Allowed: connection opens (safe)
- Shield checks policy to Blocked: no connection made (threat or category)
- Shield checks policy to One dashboard (logs)
Where Purple Shield fits in your estate
Shield fits estates where filtering must follow the shape of the network. That usually means many venues, several SSIDs or VLANs per venue, and more than one audience. It is hardware-agnostic. It runs on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet.
You can deploy it in two ways:
- Standalone. Point the DNS on any WiFi network at Shield and set a policy per network. No Purple guest WiFi is required.
- With Purple Access. Shield becomes one layer of the same platform that runs your captive portal and network policy.
Which option fits which venue estate
CleanBrowsing
Fits when
- Families, schools and small organisations
- Free preset family filters
- Up to 25 networks on a published plan
Not when
- Guest and staff share a public IP
- Many venues need one console
Cisco Umbrella
Fits when
- Cisco Secure enterprise focus
- Directory identity focus
Not when
- Mixed hardware across venues
- Guest onboarding and filtering in one tool
Purple Shield
Fits when
- Many venues, many SSIDs and VLANs
- Guest and staff need different rules
- Mixed hardware from eight vendors
- One dashboard across the estate
Not when
- A single home network with no venue
Our recommendation: For a venue estate, choose Purple Shield: a policy per SSID, VLAN and venue from one dashboard, on the hardware you already own.
The proof comes from estates that look like yours.
Shield also inherits Purple's operating record. Purple has run since 2012, serves 80,000+ live venues in 90 countries and holds ISO 27001, Cyber Essentials and B Corp certification. For how protective DNS fits a wider security model, read our enterprise WiFi security guide.
What each option costs to run
Licence price is only part of running cost. For a venue estate, the bigger costs are setup per site and the admin overhead of running filtering apart from guest WiFi. The table compares cost structure, not amounts.
| Cost driver | CleanBrowsing | Cisco Umbrella | Purple Shield |
|---|---|---|---|
| Licence basis | Free public filters; paid plan tiers | Per seat, by licence package | Tailored quote; 30-day free trial, see Shield pricing |
| New hardware | None | None | None |
| Setup per venue | Repoint DNS and link network IP | Repoint DNS, connector or agent | Repoint DNS per network, or native in Purple Access |
| Separate guest WiFi tool | Required | Required | Not required with Purple Access |
| Admin consoles to run | Filter console plus WiFi platform | Filter console plus WiFi platform | One dashboard |
Seat pricing on guest networks
Per-seat pricing suits a workforce you can count. On guest WiFi, the seat count is whoever walks in. An airport's passenger numbers swing by season, and a stadium's swing by fixture. Before you sign a seat-based contract, ask the vendor how they count unmanaged guest devices.
The hidden cost of two consoles
When filtering and guest WiFi live in separate tools, every new venue means two setups. Every policy change means two places to check, and every incident means two logs to correlate. Over an estate of hundreds of sites, that duplication costs more staff time than most licence differences. Shield removes the second console when you run it with Purple Access.
What moving off CleanBrowsing involves
Moving from CleanBrowsing to Shield is a DNS change, not a hardware project. Most of the effort goes into mapping policy, not touching infrastructure. A typical migration runs in five steps:
- Export your current rules. List each CleanBrowsing profile, its categories and any custom allow or block lists.
- Map rules to networks. Decide which SSID, VLAN and venue each rule belongs to. This is where single profiles usually split into a guest policy and a staff policy.
- Pilot one venue. Point one site's DNS at Shield and run it for a full trading week. Compare blocked categories against your old reports.
- Roll out by region. Repoint DNS on your controller or gateway venue by venue. With Purple Access, policy applies as the venue joins the platform.
- Remove the old profiles. Retire CleanBrowsing network links once every site resolves through Shield, so no venue falls back silently.
Do not copy resolver addresses or menu paths from third-party blogs. Use the setup steps in Purple's support documentation and your hardware vendor's own guides.
The bypass risk applies to every option in this guide, CleanBrowsing included. DNS over HTTPS is defined in RFC 8484 and DNS over TLS in RFC 7858. Treat the firewall rule as part of the migration, not an afterthought.
How to decide between CleanBrowsing competitors
Use one decision rule: for a venue estate, choose Purple Shield. Shield applies filtering that follows the shape of your network, giving you different rules per SSID, VLAN or venue from one place.
Three questions settle most shortlists:
- Do guest and staff share a public IP at any venue? If yes, an IP-linked family profile cannot separate them. Shield can, per SSID and VLAN.
- Do you run mixed hardware? If your estate spans Cisco Meraki at some sites and Ubiquiti UniFi at others, a hardware-agnostic filter avoids two policies.
- Who owns guest WiFi? If one team runs the captive portal and the filtering, Shield with Purple Access gives that team one dashboard.
For head-to-head detail, read Cloudflare Gateway vs Purple Shield and an OpenDNS alternative for business WiFi. If you are also weighing resolver-style services, see Control D alternatives and the best protective DNS for guest WiFi.
Your next step: pick one venue with both guest and staff SSIDs, and pilot Shield there for a week. The Shield pricing page sets out the 30-day free trial and the two ways to buy.
Key terms
- Protective DNS
- A recursive DNS resolver that refuses to resolve domains linked to malware, phishing or blocked content categories, so no connection to that domain opens. The UK National Cyber Security Centre runs a Protective DNS service for public sector bodies on this principle. Every option in this guide filters at this layer, so placement is not the differentiator. You decide on policy scope, console and guest WiFi integration instead.
- DNS resolver
- The server that answers a device's lookup for a domain name with an IP address, as defined in the Domain Name System. A filtering resolver answers or refuses before any connection opens. You repoint DNS on your controller or gateway to the filtering resolver. That single change is the core of a migration from CleanBrowsing to Shield.
- SSID
- The Service Set Identifier defined in IEEE 802.11: the network name a device sees and joins. One access point can broadcast several SSIDs, such as guest, staff and back-office networks. A venue often runs three SSIDs per site. Shield sets a separate filtering policy per SSID, which a profile tied to one public IP cannot do.
- VLAN
- A virtual local area network, tagged under IEEE 802.1Q, that separates traffic on shared switching hardware into isolated segments, so guest and staff devices never share a segment. You segment payment terminals and staff systems from guest devices by VLAN. Shield can apply a different policy to each VLAN without changing hardware.
- Captive portal
- The login page a visitor sees before getting online on guest WiFi, where terms are accepted and consent is captured before network access is granted. CleanBrowsing and Cisco Umbrella offer no captive portal link. Shield with Purple Access runs filtering next to the captive portal in one dashboard.
- DNS over HTTPS (DoH)
- An IETF protocol, specified in RFC 8484, that sends DNS queries inside encrypted HTTPS traffic to a resolver the browser chooses, bypassing the network's configured DNS. Browsers using DoH can skip any network filter, CleanBrowsing included. Block outbound DNS to other resolvers at your firewall, or a pilot will under-report.
- DNS over TLS (DoT)
- An IETF protocol, specified in RFC 7858, that encrypts DNS queries over a dedicated TLS connection to a chosen resolver, which can also bypass network DNS settings. Treat a firewall rule against DoT and DoH as part of your migration plan, not an afterthought, so every venue resolves through Shield.
- PCI DSS segmentation
- Under the Payment Card Industry Data Security Standard, network segmentation isolates the cardholder data environment from other networks to reduce the scope of systems assessed for compliance. A filtered guest VLAN kept apart from payment terminals supports PCI DSS scoping. DNS filtering supports compliance but does not make a network compliant on its own.
- Hardware-agnostic
- Purple's term for software that runs on existing WiFi infrastructure without a proprietary appliance or vendor lock-in. Shield runs on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet, so a mixed estate keeps one policy model.
- Per-seat pricing
- A licence model that charges for each user or device covered, billed monthly or annually, as used by Cisco Umbrella. Seat counts suit a workforce you can count. On guest WiFi the count is whoever walks in, so ask how unmanaged guest devices are counted.
Worked examples
A hotel runs a guest SSID, a staff SSID and a back-office VLAN for payment terminals. All three share one public IP address, and CleanBrowsing applies one filter profile to that IP. How do you give each network its own rules?
An IP-linked profile cannot tell the three networks apart, so every guest and staff device gets the same rules. Moving to Shield lets you set a policy per SSID, VLAN and venue. The guest SSID runs a stricter content category set and ad blocking. The staff VLAN reaches supplier portals. The payment VLAN stays segmented from guest devices, which supports PCI DSS scoping. No hardware changes at the site: you repoint DNS on the existing controller or gateway, and manage all three policies from one dashboard.
A multi-venue operator wants to move its estate off CleanBrowsing without a hardware project or a gap in protection. What does the migration look like?
Treat it as a DNS change and spend the effort on policy mapping. First, export each CleanBrowsing profile with its categories and custom allow or block lists. Second, map each rule to an SSID, VLAN and venue, usually splitting single profiles into guest and staff policies. Third, pilot one venue for a full trading week and compare blocked categories against old reports. Fourth, roll out by region, repointing DNS venue by venue. Finally, retire the old CleanBrowsing network links so no site falls back silently. Block outbound DNS to other resolvers at the firewall throughout, so encrypted DNS cannot bypass the pilot.
Frequently asked questions
Is CleanBrowsing suitable for business guest WiFi?
CleanBrowsing suits families, schools and small organisations, but it is not designed for venue estates. Its profiles link to a network IP or device. That cannot separate guest and staff SSIDs sharing one public address. It also offers no captive portal link. For multi-venue guest WiFi, Shield applies a policy per SSID, VLAN and venue from one dashboard.
How is Purple Shield priced compared with CleanBrowsing?
Shield is quoted on your sites, networks, users and plan, with a 30-day free trial and no hardware costs. CleanBrowsing offers free public filters and paid plan tiers. Cisco Umbrella is licensed per user. On guest networks, compare total running cost rather than licence alone. Seat counts are hard to predict for visitors, and a separate guest WiFi tool adds a second console to every venue.
Does Shield work with the WiFi hardware we already own?
Yes. Shield is hardware-agnostic and needs no new appliance. It runs on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet. You point network DNS at Shield on your existing controller or gateway. If you also run Purple Access, Shield applies natively alongside your captive portal and network policy.
How much effort does migrating from CleanBrowsing take?
Migration is a DNS change, not a hardware project. Most of the work is mapping your existing CleanBrowsing profiles to SSIDs, VLANs and venues. Pilot one venue for a trading week, then roll out region by region. Block outbound DNS to other resolvers at the firewall, so encrypted DNS does not bypass the new policy.
Can we set different filtering for guest and staff networks?
Yes. Shield sets a policy per SSID, VLAN and venue. A guest SSID can run strict content categories and ad blocking, while a staff VLAN reaches supplier and payroll sites. Both run from one dashboard across the whole estate. Separating the two networks by VLAN also keeps guest devices off the segment that staff systems use.
Does DNS filtering help with GDPR or PCI DSS compliance?
DNS filtering supports compliance but does not make a network compliant on its own. PCI DSS treats segmentation as the way to reduce the scope of cardholder data. A filtered guest VLAN, kept apart from payment terminals, supports that. Purple holds ISO 27001 and Cyber Essentials certification and operates as GDPR and CCPA compliant.
How does Shield compare with Cisco Umbrella?
Shield is built for venue WiFi estates, and Umbrella for enterprises in the Cisco security portfolio, with Umbrella DNS reaching end of sale on 31 January 2027. Both filter at the DNS layer. Shield adds a policy per SSID, VLAN and venue, integrates natively with Purple Access, and flags threats up to 10 days sooner, on Purple's own data.
Will DNS filtering stop every threat on guest WiFi?
No single control stops every threat, but DNS filtering stops many before any connection opens. It refuses known malicious domains at lookup, which a firewall cannot do. At St George's Healthcare NHS Trust, Shield blocks about 241,000 threats a week. Pair it with VLAN segmentation and a firewall rule against encrypted DNS bypass.
