ComparisonDNS filtering alternatives
Control D alternatives for business WiFi
Use this comparison to decide whether Control D, Cisco Umbrella or Purple Shield fits your venue estate, based on where each attaches policy and how it is licensed. You will also be able to plan a low-risk move off Control D, starting with a single-venue pilot and a controller DNS change.
Watch the explainer
The strongest Control D alternative for business WiFi is Purple Shield. Shield applies a protective DNS policy per SSID, VLAN and venue from one dashboard, with no new hardware. It works on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist and Ubiquiti UniFi, and Purple already runs in 80,000+ venues.
Which Control D alternative suits a multi-venue estate?
For any estate where one venue carries more than one network, we recommend Purple Shield. The answer depends on one question: how many distinct policies does each venue need?
- One network, one rulebook. A small office can run on almost any protective DNS service.
- Several networks per venue. A hotel with a guest SSID, a staff VLAN and a point-of-sale VLAN cannot share one rulebook safely.
Placement explains why this matters. DNS filtering acts when a device looks up a domain, before any connection opens. A phishing domain blocked at lookup never receives a packet from the device. A firewall typically judges traffic by IP address and port. IP rules struggle with domains that change hosting often, and DNS filtering catches what those rules miss.
The UK National Cyber Security Centre calls this approach protective DNS and runs it for the public sector.
Control D, Cisco Umbrella and Shield all filter at this layer. They differ on three things:
- Where the policy attaches.
- Who manages it.
- How it sits beside your WiFi.
For the wider category, see our DNS filtering alternatives overview.
Which criteria decide a Control D alternative for venues?
We fixed eight criteria before scoring any vendor. Each reflects a question IT managers and venue operators raise when a single-profile setup starts to strain. Every competitor score comes from that vendor's own public documentation. Purple scores come from Purple's own data.
- Policy unit. A policy can attach to a device, a network, a user or an SSID. This decides whether guests and staff get different rules at the same venue.
- Per-VLAN control. A VLAN (virtual local area network) splits one physical network into isolated segments. Venues use VLANs to keep guest, staff and payment traffic apart, and PCI DSS scoping guidance rewards that segmentation. Filtering should follow the same split.
- Agentless guest coverage. Guests will never install software. Filtering must work at network level for every phone, laptop and tablet that joins.
- Multi-site management. You need to see and change policy for hundreds of venues from one place, without logging in site by site.
- Threat intelligence. The speed at which a service learns about new malicious domains decides how long guests stay exposed.
- Ad and tracker blocking. Blocking ads at DNS cuts bandwidth on busy guest networks, not only on-screen clutter.
- WiFi tie-in and hardware. Does DNS policy live beside your WiFi, and does it need a box at each site?
- Pricing model. What does the licence count: endpoints, users or networks?
How do Control D competitors compare side by side?
The matrix below scores each option on the criteria above. Read the policy unit and per-VLAN rows first, because they decide most venue shortlists. The remaining rows separate options that pass that first test.
| Criterion | Purple Shield | Control D | Cisco Umbrella |
|---|---|---|---|
| Policy unit | SSID, VLAN and venue | Profile per endpoint | Identity: network, user, device |
| Per-VLAN policy | Native, in one dashboard | Endpoint per VLAN or ctrld | Internal networks via virtual appliance |
| Guest devices, no agent | Yes, network level | Yes, network endpoint | Yes, network identity |
| Multi-site view | One dashboard, every venue | Organisations and sub-organisations | Multi-org console |
| Threat intelligence | Proactive threat detection | Malware and phishing filters | Cisco Talos |
| Ad and tracker blocking | Up to 44% less data, 62% fewer queries | Ads and trackers filter | Content categories |
| Sits beside your WiFi | Standalone or on Purple Access | Separate console | Separate console; Meraki integration |
| New hardware | None | None; ctrld optional | None; appliance optional |
| Licence unit | Tailored quote; standalone or on Purple Access | Per endpoint | Per user, tiered |
| Primary focus | Multi-network venue estates | Device-level control | Cisco-standardised estates |
Where do Control D, Cisco Umbrella and Shield differ?
All three block malicious domains at lookup. The differences sit in how policy reaches each network segment, and in how much work that takes per venue.
Where the policy attaches
Control D builds everything around profiles. A profile holds filters, service rules and custom rules, and you assign it to an endpoint. An endpoint can be a device or a network, such as a router. That model gives you fine-grained control per device.
At a venue, every device behind a router endpoint inherits the same profile. To split guest and staff rules, you have two routes:
- Register a separate endpoint per VLAN.
- Run Control D's ctrld daemon on a router you manage and map subnets to profiles.
Both work, but you build and maintain the split at every site.
Cisco Umbrella attaches policy to identities: networks, users, roaming devices and internal networks through its virtual appliance.
Shield attaches a policy to each SSID, VLAN and venue, set in one dashboard. A typical venue looks like this:
- Guest SSID: content filtering and threat blocking.
- Staff VLAN: threat blocking with productivity rules.
- Point-of-sale VLAN: the tightest rules of all.
You manage every policy from the same view across every venue.
Two lanes compare a single DNS profile applied to every device on a venue network with Purple Shield applying separate policies to the guest SSID, staff VLAN and point-of-sale VLAN.
Connections
- Venue router to One resolver profile (DNS query)
- One resolver profile to Wrong rules for some devices
- Guest SSID to Shield policy engine (guest policy)
- Staff VLAN to Shield policy engine (staff policy)
- Point-of-sale VLAN to Shield policy engine (POS policy)
- Shield policy engine to Query answered or blocked
Guest networks without agents
All three options filter guest devices without software, because each can resolve DNS for a whole network. The difference is effort per venue:
- Control D and Umbrella: you engineer the per-VLAN split at each site's router or appliance.
- Shield: the split follows the SSIDs and VLANs your WiFi already defines, so you configure nothing extra at the edge.
Threat intelligence speed
Each vendor publishes its approach:
- Cisco Umbrella draws on Cisco Talos threat intelligence.
- Control D offers malware and phishing filters within each profile.
Shield flags threats early. That shrinks the window between a malicious domain going live and a guest clicking it. St George's Healthcare NHS Trust relies on Shield to block malicious domains across its network.
Bandwidth and ad blocking
On a congested guest network, ads and trackers eat airtime that guests notice:
- Control D offers an ads and trackers filter.
- Umbrella handles advertising domains through content categories.
Purple has measured the effect. With ad blocking on, Shield cuts data by up to 44% and DNS queries by up to 62%. On an airport concourse or a stadium bowl, that capacity goes back to passengers and fans.
Management model
Control D supports organisations and sub-organisations, which suits managed service providers (MSPs). Umbrella offers a multi-tenant console for MSPs too. Both run as consoles separate from your WiFi.
Shield runs standalone on any WiFi or bolts onto Purple Access. There, DNS policy sits next to guest onboarding and staff access in one dashboard.
Where each option wins
- Control D focuses on device-level customisation and traffic redirection for staff who roam.
- Cisco Umbrella targets estates standardised on Cisco, with a route to its wider security edge.
- Shield provides the strongest fit wherever one venue runs several networks and the WiFi team owns the policy.
Where does Purple Shield fit?
Shield is Purple's protective DNS and content-filtering service. It runs standalone on any network or adds onto Purple Access.
Shield is hardware-agnostic. It works with:
- Cisco Meraki
- HPE Aruba
- Ruckus
- Juniper Mist
- Ubiquiti UniFi
- Cambium
- Extreme
- Fortinet
You point DNS for each SSID or VLAN at Shield in the controller you already run. Nothing changes on the access points themselves.
- 80,000+live venuesPurple data
- 90countriesPurple data
- Up to 44%less data with ad blockingPurple data
- Up to 62%fewer DNS queries with ad blockingPurple data
Shield is already in production across three of the toughest venue types:
- Hospitality: Whitbread.
- Travel: AGS Airports, where passenger volumes swing hour by hour.
- Healthcare: St George's Healthcare NHS Trust, where patient and visitor networks share sites with clinical systems.
Purple holds ISO 27001 and Cyber Essentials certification and processes data under GDPR and CCPA. For the full security picture across Guest WiFi and Staff WiFi, read our enterprise WiFi security guide.
Which protective DNS fits your venues?
Purple Shield
Fits when
- Venues run guest, staff and payment networks
- You need a policy per SSID, VLAN and venue
- You want DNS policy beside your WiFi
- You cannot add hardware at each site
Not when
- None
Control D
Fits when
- You want device-level profiles for roaming staff
- You need traffic redirection through proxy locations
Not when
- Policy must follow SSIDs and VLANs across many venues
Cisco Umbrella
Fits when
- Your estate is standardised on Cisco security
Not when
- You want DNS policy managed beside guest onboarding
Our recommendation: Choose Purple Shield when your venues carry more than one network and each needs its own policy. Start with one venue on the 30-day free trial.
What does each option cost to run?
We do not publish competitor prices. Licensing structure, though, shapes your bill more than the headline rate:
- Control D's business plans: per endpoint.
- Cisco Umbrella: per user, across tiered packages.
- Shield: a tailored quote on your sites, networks, users and plan, standalone or added onto Purple Access.
Per-user and per-endpoint models were designed around staff and devices you can count. A guest network serves visitors you cannot count in advance. Ask each vendor, in writing, how a guest network with high device churn is counted before you sign.
The second cost is operational. Every option that runs beside your WiFi adds a second console, and a second place to audit when a policy fails. Per-VLAN splits built on routers also add per-site configuration your team must maintain.
| Cost line | Purple Shield | Control D | Cisco Umbrella |
|---|---|---|---|
| Licence unit | Tailored quote; standalone or on Purple Access | Per endpoint | Per user, by package tier |
| New hardware | None | None; ctrld runs on a router you own | None; optional virtual appliance |
| Per-venue setup | Assign policy to SSID or VLAN | Create endpoints, repoint router DNS | Add network identity, repoint DNS |
| Consoles to run | One with Purple WiFi; two if standalone | Two: WiFi plus DNS | Two: WiFi plus DNS |
| Scope included | Protective DNS, content filtering, ad blocking | DNS filtering and traffic redirection | DNS security; higher tiers add secure web gateway |
The Shield pricing page sets out the 30-day free trial and the two ways to buy.
What does moving from Control D involve?
Moving off Control D is mostly a planning exercise. No hardware ships, and no guest installs anything. The work is mapping profiles to networks, then changing DNS settings you already control.
- Inventory Control D. List every profile, its filters, service rules and custom allow and block lists, plus the endpoint each one serves.
- Map profiles to networks. Decide which SSID or VLAN at each venue carries which policy. This step often reveals staff and guests sharing rules today.
- Build Shield policies. Recreate content categories and custom lists as Shield policies, one per network type rather than one per site.
- Pilot one venue. Point the guest SSID's DNS at Shield in your controller, then the staff VLAN. Keep Control D live everywhere else.
- Check the results. Review blocked-query logs and test category blocks from a guest device and a staff device.
- Roll out by region. Repeat the controller change venue by venue, or through templates where your controller supports them.
- Retire Control D. Remove ctrld from routers and delete endpoints once their query logs fall silent.
Watch staff devices closely. Control D distributes device profiles that use DNS over HTTPS (DoH, defined in RFC 8484) and DNS over TLS (DoT, RFC 7858). Encrypted DNS sends queries straight to the provider, bypassing your network resolver. Any phone still carrying a Control D profile will ignore your venue policy until you remove it.
Estates with many bespoke site profiles take longest to map. Consolidating them into a few policies by network type is the real win of the move. It also cuts the rules you audit each quarter.
How should you decide between Control D alternatives?
Use this decision rule. If any venue carries more than one network that needs its own policy, choose Shield. The same applies if you want DNS policy managed in the same dashboard as your WiFi.
If every venue runs one network with one rulebook, the criteria in this guide narrow. Shield still adds the 44% data saving and earlier threat flagging.
Three questions settle most shortlists:
- Separate rules. Do guest, staff and payment devices at the same venue need different rules?
- Scale. Will you manage more than a handful of sites from one team?
- Ownership. Does your WiFi team, rather than a separate security team, own content policy?
Two or more yes answers point to Shield.
Your next step is a single-venue pilot. Pick a site with a guest SSID and a staff VLAN, then run Shield beside Control D for one billing cycle. To widen the shortlist first, compare our view of the best protective DNS for guest WiFi. We have also written an OpenDNS alternative for business WiFi and a Cloudflare Gateway vs Shield comparison.
Key terms
- Protective DNS
- A DNS resolution service that refuses to resolve domains known to host malware, phishing or other threats, applied to the Domain Name System defined in RFC 1034 and RFC 1035. The UK National Cyber Security Centre operates a protective DNS service for the public sector. Every option in this comparison is a protective DNS service. You meet the term when assessing guest and staff network security, and the choice comes down to where each service attaches its policy.
- DNS filtering
- Blocking or allowing name lookups against category, threat and custom lists at the resolver, so a blocked domain returns no usable answer and the device never opens a connection. It operates on DNS queries (RFC 1035) rather than on IP addresses and ports. DNS filtering catches domains that change hosting often and slip past IP-based firewall rules. It is the layer where Control D, Cisco Umbrella and Shield all operate.
- VLAN
- A virtual local area network, specified in IEEE 802.1Q, which adds a 12-bit VLAN identifier tag to Ethernet frames so one physical network carries several logically isolated broadcast domains. Venues use VLANs to keep guest, staff and payment traffic apart. Your DNS policy should follow the same split, which is why per-VLAN control is a core scoring criterion.
- SSID
- The service set identifier defined in IEEE 802.11, a network name of up to 32 octets broadcast by access points so devices can select which wireless network to join. Shield attaches a policy to each SSID, so a guest network and a staff network at the same venue receive different filtering rules without extra edge configuration.
- DNS over HTTPS (DoH)
- A protocol defined in IETF RFC 8484 that carries DNS queries and responses inside HTTPS, encrypting them and sending them directly to a chosen resolver. Control D distributes device profiles using DoH. A staff phone still carrying one sends queries straight to Control D and ignores your venue policy, so remove these profiles during migration.
- DNS over TLS (DoT)
- A protocol defined in IETF RFC 7858 that encrypts DNS traffic using Transport Layer Security over a dedicated port, bypassing the local network resolver. Like DoH, DoT profiles on staff devices will bypass Shield after cutover. Check devices for lingering Control D profiles when you review pilot results.
- DHCP lease
- The time-limited assignment of an IP address and network settings, including DNS server addresses, issued to a client under the Dynamic Host Configuration Protocol in IETF RFC 2131. Devices keep their old resolver until the lease renews. Change DNS at the controller or DHCP scope and allow for lease time before you assess a pilot venue.
- PCI DSS
- The Payment Card Industry Data Security Standard, published by the PCI Security Standards Council, which sets requirements for protecting cardholder data and whose scoping guidance treats network segmentation as a way to reduce the cardholder data environment. Keeping point-of-sale devices on a segmented VLAN with the tightest DNS policy narrows what payment systems can reach. Protective DNS supports compliance but does not deliver it alone.
- GDPR
- The EU General Data Protection Regulation (Regulation (EU) 2016/679), whose Article 32 requires appropriate technical and organisational measures to secure personal data processing. Blocking phishing domains reduces the risk of credential theft, which supports your security-of-processing obligations. Purple processes data under GDPR and CCPA.
- ctrld daemon
- Control D's DNS forwarding proxy, run on a router or host you manage, which maps local subnets or clients to different Control D profiles and forwards their queries over encrypted DNS. Control D uses ctrld to split guest and staff rules at a venue. It is per-site configuration you must build and maintain, and you remove it from routers when retiring Control D.
- Policy unit
- The object a DNS filtering policy attaches to: a device or endpoint, a user, a site identified by public IP, an identity, or a network segment such as an SSID or VLAN. The policy unit decides whether guests and staff at the same venue can receive different rules. Read this row of the comparison matrix first.
Worked examples
A hotel runs a guest SSID, a staff VLAN and a point-of-sale VLAN at every site. A single resolver profile on the venue router gives every device the same rules, over-blocking staff or under-protecting guests. How should the hotel apply DNS policy?
The hotel assigns a separate Shield policy to each network segment from one dashboard. The guest SSID receives content filtering and threat blocking. The staff VLAN receives threat blocking with productivity rules. The point-of-sale VLAN receives the tightest rules of all, which also supports PCI DSS segmentation. Because each policy follows the SSIDs and VLANs the WiFi already defines, nothing extra is configured at the edge and no guest installs an agent. The same policies apply across every venue from the same view, rather than being rebuilt router by router.
An estate running Control D across many venues wants to move to Shield without disrupting guests or shipping hardware. How should the IT team sequence the move?
The team inventories every Control D profile, filter, service rule and custom list, plus the endpoint each serves. It maps those profiles to SSIDs and VLANs, then rebuilds them as Shield policies by network type rather than by site. It pilots one venue by pointing the guest SSID and then the staff VLAN at Shield in the controller, keeping Control D live elsewhere. It allows for DHCP lease renewal, reviews blocked-query logs and tests from guest and staff devices. It removes Control D DoH and DoT profiles from staff phones, rolls out by region, then retires ctrld and endpoints once their logs fall silent.
Frequently asked questions
Is Purple Shield a like-for-like Control D replacement for venues?
Yes. For network-level filtering at venues, Shield replaces Control D's role and adds policy per SSID, VLAN and venue. Both filter at the DNS layer before any connection opens. Shield attaches policy to the networks your WiFi already defines and manages it in one dashboard. If staff phones carry Control D DNS profiles, remove them during migration, or they will bypass your venue policy.
How is Shield priced compared with Control D business plans?
Shield runs standalone on any network or adds onto Purple Access, and is quoted on your sites, networks, users and plan, with a 30-day free trial. Control D's business plans are licensed per endpoint. We do not quote competitor prices. The useful comparison is structural: count the endpoints, users or networks each model charges for at your venues. The [Shield pricing page](product:shield/pricing) sets out the trial and the two ways to buy.
Do I need new hardware to switch from Control D to Shield?
No. Shield works through the DNS settings of the WiFi you already run. Supported platforms include Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet. You change the DNS server for each SSID or VLAN in your controller or DHCP scope. If you run Control D's ctrld daemon on routers, you remove it at cutover.
Can Shield apply different policies to guest and staff WiFi at the same venue?
Yes. Shield applies a policy per SSID, VLAN and venue from one dashboard. A hotel can give its guest SSID content filtering and threat blocking. Its staff VLAN gets threat blocking with productivity rules, and its payment VLAN the tightest rules. Each policy follows the network segment, so guests install nothing and no device needs an agent.
How does Control D vs Cisco Umbrella compare for guest WiFi?
Both filter guest traffic at the DNS layer without agents, but they attach policy differently. Control D assigns profiles to endpoints, which can be routers. Umbrella assigns policy to identities, including internal networks through a virtual appliance. Both run as consoles separate from your WiFi. Shield ties policy to the SSIDs and VLANs your WiFi already defines. Our [CleanBrowsing alternatives guide](guide:cleanbrowsing-alternatives) covers another option.
Does protective DNS help with GDPR and PCI DSS compliance?
It supports both, but it does not deliver compliance on its own. PCI DSS rewards keeping payment systems on a segmented network. A strict DNS policy on that VLAN narrows what those systems can reach. Under GDPR, blocking phishing domains reduces the risk of credential theft. Purple holds ISO 27001 and Cyber Essentials certification and processes data under GDPR and CCPA.
How much effort does a migration from Control D take?
Most of the effort is planning, not configuration. You inventory Control D profiles and custom lists, map them to SSIDs and VLANs, build Shield policies and pilot one venue. After that, each venue is a DNS change in your controller. Estates with many bespoke site profiles take longer, because you consolidate them into a few policies by network type.
Will DNS filtering slow down guest WiFi?
No. With ad blocking on, it lightens the load. Purple data shows Shield cuts data by up to 44% and DNS queries by up to 62% when ad blocking is enabled. A DNS block also stops a connection before it opens, so blocked content never consumes airtime. At busy venues, that capacity goes back to guests, fans and passengers.
