Skip to content
Shield

ComparisonDNS filtering alternatives

An OpenDNS alternative for business and guest WiFi

You will be able to choose an OpenDNS replacement for business and guest WiFi by placement, policy granularity and licensing unit. You can then plan a migration from OpenDNS or Cisco Umbrella to network-level protective DNS. The six-step sequence runs from audit to a single-venue pilot and a site-by-site rollout with...

14 min read

An OpenDNS alternative for business and guest WiFi

Watch the explainer

If you run venue WiFi, the best OpenDNS alternative is one that filters at the network rather than on each device. If you want a policy per network and venue, with no agent to install, choose Purple Shield. It blocks about 241,000 threats a week at St George's Healthcare NHS Trust, and Whitbread and AGS Airports run it.

Which OpenDNS alternative fits business and guest WiFi?

Start with placement, because it decides everything else. Protective DNS is a resolver that refuses to answer for known malicious or unwanted domains. Phishing pages, malware downloads and command-and-control servers never resolve, so the connection never starts. The UK NCSC runs a Protective DNS service for the public sector on the same principle.

Filtering can sit in one of two places:

  • On the network. Every device that joins inherits the policy.
  • On the device. An agent carries the policy wherever a laptop goes.

For venue WiFi, the network is the right place. Guests, shoppers and passengers bring phones you will never manage, and you cannot ask them to install anything. Shield filters at the network level. It applies a policy per SSID (the WiFi network name), per VLAN (virtual LAN, a logical segment of one physical network) and per venue.

The answer flips on one axis: whether your priority is networks you operate or managed laptops that roam. Cisco Umbrella and Cloudflare Gateway are built around people and enrolled devices. If your problem is WiFi across sites, that model adds enrolment and licensing steps that venue WiFi does not need.

What happened to OpenDNS for business?

OpenDNS launched as a free public resolver in 2006 and later sold paid business filtering. Cisco acquired OpenDNS in 2015 and moved the business product into Cisco Umbrella. Umbrella is now sold as tiered packages, licensed per user. The tiers run from DNS-layer security through to secure internet gateway (SIG) bundles.

For a small operator, that changed the shape of the product. A simple DNS filter for a few networks became an entry point into an enterprise security portfolio. The OpenDNS brand stuck while the packaging moved, which is why so many IT teams still search for it.

Is OpenDNS still free?

OpenDNS Home and FamilyShield remain free resolvers aimed at households. Cisco points business networks to Umbrella instead.

The free service also carries policy exposure. In 2024, Cisco withdrew OpenDNS from France after a court order to block piracy sites. A free consumer resolver gives you no service-level commitment and no control over decisions like that.

How we compared OpenDNS alternatives

We scored four options:

  • OpenDNS Home and FamilyShield
  • Cisco Umbrella
  • Cloudflare Gateway
  • Purple Shield

Each competitor entry comes only from that vendor's public material. That includes the Cisco Umbrella documentation and the Cloudflare One documentation. We compare how each option is priced, never the amount. List prices change, and they rarely match a negotiated quote.

We chose seven criteria that decide a venue or MSP rollout:

  1. Placement. Where the filtering decision happens: on a router, at a cloud resolver or in a device agent.
  2. Policy granularity. Whether you can set different rules per SSID, VLAN and site.
  3. Unmanaged device coverage. Whether guest phones are protected with nothing installed.
  4. Hardware dependency. Whether you need new appliances or a specific WiFi vendor.
  5. Reporting. What you can see about the threats you block.
  6. Licensing structure. The unit you pay for as your estate grows.
  7. Multi-site management. Whether one team can run many venues from one place.

Other resolvers also appear on shortlists. We cover them in CleanBrowsing alternatives for venues and Control D alternatives for business WiFi. For the wider category, see our DNS filtering alternatives overview.

How do OpenDNS, Umbrella, Cloudflare Gateway and Shield compare?

The matrix scores each option against the seven criteria, plus the use each vendor designs for. Read it row by row. The placement row explains most of the differences below it.

OpenDNS alternatives compared for business and guest WiFi Data as of 2026-06-10
CriterionOpenDNS HomeCisco UmbrellaCloudflare GatewayPurple Shield
Where filtering happensRecursive DNS set on a home router or deviceCloud DNS by network, plus optional virtual appliance and roaming clientCloud DNS by registered location, plus the WARP client on devicesCloud protective DNS applied to each network you operate
Designed forHouseholds and personal useEnterprise security teams within Cisco's security portfolioZero Trust programmes within Cloudflare OneBusiness, guest and staff WiFi across venues
Policy granularitySettings per registered networkPer network, internal range, directory group or devicePer location, or per person and device with the clientPer SSID, VLAN and venue from one dashboard
Unmanaged guest devicesCovered at the router, with no identityCovered by network policy; identity needs a connector or clientCovered by location policy; identity needs the WARP clientEvery device on the filtered network, with no agent
WiFi hardware dependencyNone; a DNS setting changeNone for DNS; native Cisco Meraki integrationNone for DNS location policiesHardware-agnostic: Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme, Fortinet
ReportingBasic network statisticsActivity search and security reportsGateway logs and analyticsThreats blocked per network, such as ~241,000 a week at St George's
Licensing structureNo charge for home usePer-user subscription packagesPer-user plans with an entry tier for small teamsTailored quote, with a 30-day free trial
Multi-site managementSingle dashboard per accountMulti-organisation console for MSPsCloudflare One account dashboardOne dashboard across venues, standalone or on Purple Access
Competitor entries summarise each vendor's public product material as at the asOf date. We describe how each is priced, never the amount.

The pattern is consistent across the rows. OpenDNS Home is a household product. Umbrella and Gateway are identity platforms that can filter networks. Shield is a protective DNS for WiFi that starts from the network.

Where do the OpenDNS alternatives differ?

Placement: network policy versus device agents

Umbrella and Gateway can filter a network by its public IP or a registered location. Their richer features follow the person, and those features need a connector, a directory sync or an agent on the device.

That design suits a security team protecting managed laptops. It does not help with the phone a hotel guest connects in the lobby. Nobody will enrol that phone, and nobody should try.

Shield inverts the model. The network is the unit of policy, so every device inherits protection the moment it joins.

Network-level: Purple ShieldDevice-level: agent-based DNSjoinsDNS queryallowedblockedDNS queryGuest phone joinsvenue WiFiNothing installed onthe deviceSSID and VLANpolicyGuest, staff andback-office rulesdifferShield protectiveDNSResolves safe domains,refuses known threatsSafe site loadsThreat blockedPhishing, malware,unwanted contentManaged laptopEnrolled in devicemanagementAgent rolled outto each deviceMust be deployed beforepolicy appliesVendor cloudresolverPolicy follows theperson
Where the filtering decision happens: on the network with Shield, or on the device with an agent

Two lanes compare a guest phone filtered by Shield at the venue network with a managed laptop filtered through a device agent.

Connections

  1. Guest phone joins venue WiFi to SSID and VLAN policy (joins)
  2. SSID and VLAN policy to Shield protective DNS (DNS query)
  3. Shield protective DNS to Safe site loads (allowed)
  4. Shield protective DNS to Threat blocked (blocked)
  5. Managed laptop to Agent rolled out to each device
  6. Agent rolled out to each device to Vendor cloud resolver (DNS query)

Policy granularity on shared WiFi

One building often carries three or four networks. A hotel may run a guest SSID, a staff SSID, a conference SSID and a back-office VLAN for point-of-sale systems. Each needs different rules.

A family-facing guest network needs adult content blocked. A staff network may need social media allowed for marketing teams. A payments VLAN should reach almost nothing beyond its processors.

OpenDNS Home gives you settings per registered network, which works for a house with one router. Shield sets policy per SSID, VLAN and venue from one dashboard. You can write one guest policy once and apply it to 200 sites, then override it where a venue needs something different.

Threat intelligence and what it saves

Protective DNS is only as good as its view of new threats. Shield flags emerging threats rapidly, blocking malicious domains before they can cause harm.

Blocking also saves capacity. Shield refuses unwanted domains before anything loads. Purple's own data shows networks running Shield use up to 44% less data and make up to 62% fewer DNS queries. On a congested stadium, station or hotel network, that headroom goes back to the visitors you want to serve.

Hardware and rollout

None of the four options needs a new box for basic DNS filtering. The difference is what comes after. Umbrella's identity features and Gateway's device policies both bring an agent rollout. Umbrella's deepest wireless integration is with Cisco Meraki.

Shield stays at DNS on any vendor's network. For more on securing the wider estate, read our enterprise WiFi security guide.

DNS over HTTPS is defined in RFC 8484, and DNS over TLS in RFC 7858. Both encrypt DNS, which protects privacy but can hide queries from a network filter. Whichever option you choose, plan the bypass controls as part of the rollout.

Where Purple Shield fits

Shield is Purple's protective DNS for business, guest and staff WiFi. It runs standalone or on Purple Access. It works at DNS, so it sits on top of the network you already run. That is the same hardware-agnostic cloud overlay model Purple uses across 80,000+ venues in 90 countries.

The proof comes from busy, mixed-device networks:

  • Hospitality. Whitbread runs Shield across a large hospitality estate.
  • Travel. AGS Airports runs Shield, where passengers bring thousands of unmanaged devices.
  • Healthcare. St George's Healthcare NHS Trust runs Shield, where patients, visitors and staff share the same infrastructure.
  • ~241,000threats blocked a weekSt George's Healthcare NHS Trust
  • Up to 62%fewer DNS queriesPurple data
  • Up to 44%less dataPurple data
  • 80,000+venues in 90 countriesPurple platform

The fit block compares where filtering can sit. Use it to check your own estate against each approach.

Where should protective DNS sit in your estate?

Network-level protective DNS (Purple Shield)

Fits when

  • You run guest, staff or multi-tenant WiFi across one or many venues
  • You need a different policy per SSID, VLAN and venue
  • Visitors bring devices you will never manage
  • You want to keep your existing WiFi hardware

Not when

  • You expect every guest to install an app or agent before they connect

Device-agent DNS filtering

Fits when

  • Policy has to follow enrolled laptops off your network
  • Every protected device is managed and licensed per person

Not when

  • Visitors bring phones and laptops nobody will enrol

Free household resolvers

Fits when

  • You are filtering a single home network

Not when

  • You operate a business network and need reporting, support or multi-site control

Our recommendation: For business and guest WiFi, choose Purple Shield: policy per SSID, VLAN and venue from one dashboard, on the hardware you already own, with a 30-day free trial.

What does each OpenDNS alternative cost to run?

The licence is only part of the bill. The larger cost is often people time, which goes on enrolling devices, maintaining agents and managing policy site by site. The table compares cost structure, not amounts.

Cost structure of OpenDNS alternatives for business WiFi Data as of 2026-06-10
Cost driverCisco UmbrellaCloudflare GatewayPurple Shield
Licence unitPer user, by package tierPer user, by planTailored quote for your estate
What grows the billHeadcount covered and package tierHeadcount covered and planScope agreed with Purple in your quote
Endpoint softwareCisco Secure Client module for off-network protectionWARP client for device-level policyNone needed for devices on your networks
HardwareNone for DNS; optional virtual appliancesNone for DNS location policiesNone; runs on your existing WiFi
Admin effort per venueNetwork identities per site, plus client rollout for roamingLocation set-up per site, plus client rollout for identityPolicy per SSID, VLAN and venue in one dashboard
How you buyCisco and partner channelSelf-serve or Cloudflare salesPurple directly, standalone or with Purple Access
Structures summarise each vendor's public material as at the asOf date. No competitor prices are stated.

Licensing for guest networks

Per-user licensing works when you know who your people are. A security team can count staff and buy that many licences.

Guest WiFi does not work that way. The people on your network change hourly, and none of them sit in your directory. So the question for venue operators is not only the rate. It is whether the unit of licensing matches what you operate.

How Purple prices Shield

Purple prices Shield through a tailored quote, built around your estate and whether you run it standalone or on Purple Access. We do not publish list prices.

You can start with a 30-day free trial on your own network. That lets you measure blocked threats and query reduction before you commit. Request both on the Shield pricing page.

Hidden running costs

Agents need packaging, updates and support tickets when they break a VPN or a captive portal (the sign-in page shown before WiFi access). Directory connectors need maintaining.

Network-level protective DNS removes those tasks for guest devices, because there is nothing on the device to maintain. Your remaining work is policy design, which you do once per network type.

How hard is it to migrate from OpenDNS?

Most of the effort is DNS changes and policy design, not hardware. If OpenDNS or Umbrella currently filters at the network, Shield replaces it at the same point. Follow this sequence:

  1. Audit where OpenDNS sits today. Check DHCP scopes, firewall DNS forwarders, router settings and any Cisco Meraki Umbrella integration. Note any network still pointing at the free home resolvers.
  2. Map categories to networks. List your SSIDs and VLANs, then decide which categories each should block. A family-facing guest SSID needs stricter content rules than a back-office VLAN.
  3. Pilot one venue on the 30-day free trial. Point that venue's DNS at Shield and compare the block reports with what OpenDNS showed.
  4. Close the bypass routes. Redirect or block outbound DNS to other resolvers, so nobody can skip policy.
  5. Roll out venue by venue. Change DNS settings site by site, and record the old configuration for rollback.
  6. Retire the old account. Once every network resolves through Shield, end the OpenDNS or Umbrella subscription at renewal.

Purple supplies the resolver settings and policy guidance for your estate during the trial. We do not reproduce configuration values here, because they depend on your deployment.

Where migration takes longer

Two situations add work:

  • Umbrella roaming clients. If you rely on the roaming client for staff laptops, plan that endpoint change as a separate workstream from venue WiFi.
  • Personal OpenDNS accounts. If a site manager set up a personal account years ago, the audit step will find it. Bring it under central control first.

How to choose your OpenDNS replacement

Use one decision rule. If filtering must apply to networks you operate, especially where visitors bring their own devices, choose Shield.

That covers hotels, pubs, restaurants, retail stores, airports, rail, stadiums, campuses and healthcare sites. In each, the network is the only control point you own. Shield gives you policy per SSID, VLAN and venue from one dashboard, on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme or Fortinet.

If your requirement is purely device-level protection for laptops off your network, that is an endpoint question. Scope it separately from venue WiFi.

Your next step takes about one meeting:

Key terms

Protective DNS
A recursive DNS resolver, operating under the Domain Name System defined in RFC 1034 and RFC 1035, that refuses to resolve domains classed as malicious or unwanted. Phishing, malware and command-and-control domains never resolve, so the connection never starts. The UK NCSC runs a Protective DNS service for the public sector on this principle. This is the category OpenDNS, Cisco Umbrella, Cloudflare Gateway and Purple Shield all sit in. Where the resolver applies its decision, on the network or on the device, decides which option fits venue WiFi.
SSID
Service Set Identifier, the network name an access point broadcasts under the IEEE 802.11 standard. One physical access point can broadcast several SSIDs, each mapped to its own policy and segment. A hotel may run guest, staff and conference SSIDs from the same hardware. Shield applies a distinct DNS policy per SSID, which OpenDNS Home cannot do beyond one setting per registered network.
VLAN
Virtual LAN, a logical segment of one physical network defined by IEEE 802.1Q, which tags Ethernet frames so traffic stays isolated between segments sharing the same switches. You meet VLANs when separating point-of-sale or back-office systems from guest traffic. Shield sets policy per VLAN, so a payments segment can reach almost nothing beyond its processors.
DNS over HTTPS (DoH)
Specified in IETF RFC 8484, DoH carries DNS queries inside HTTPS, encrypting them and sending them over port 443 rather than standard DNS on port 53. DoH protects privacy but can hide queries from a network DNS filter. Plan bypass controls, such as blocking known public resolvers, as part of any rollout.
DNS over TLS (DoT)
Specified in IETF RFC 7858, DoT encrypts DNS queries in a TLS session on a dedicated port, separate from unencrypted DNS on port 53. Like DoH, DoT can route a device around your filtering resolver. Firewall rules that close bypass routes belong in step four of the migration sequence.
Port 53 redirection
Port 53 is the standard port for DNS over UDP and TCP under RFC 1035. Redirection is a firewall rule that captures outbound queries on port 53 and sends them to a chosen resolver, whatever the device has configured. Devices with a hard-coded resolver ignore the DNS settings handed out by DHCP. Redirecting port 53 to Shield keeps those devices under your network policy.
Secure internet gateway (SIG)
A cloud security service that inspects web traffic beyond DNS, typically combining DNS-layer filtering with proxying and firewall functions in one licensed bundle. Cisco Umbrella packages run from DNS-layer security through to SIG bundles, licensed per user. For a small operator this turns a DNS filter into an entry point to a wider security portfolio.
Roaming client (device agent)
Endpoint software, such as the module in Cisco Secure Client or the Cloudflare WARP client, that applies the vendor's DNS or gateway policy to a device wherever it connects and ties that policy to a person. Agents suit managed laptops that roam off-site. Nobody will enrol a guest phone in a hotel lobby, which is why network-level filtering suits venue WiFi.
Captive portal
A web page an access network presents before granting internet access, used for sign-in, terms acceptance or data capture, typically triggered by intercepting the first HTTP request or DNS lookup. Device agents can break a captive portal or a VPN, generating support tickets. Network-level protective DNS avoids that hidden running cost for guest devices.
PCI DSS
The Payment Card Industry Data Security Standard, maintained by the PCI Security Standards Council, which sets security requirements for systems that store, process or transmit cardholder data. Network segmentation can reduce which systems fall into assessment scope. Segmenting guest WiFi from cardholder systems reduces your PCI DSS scope. Shield's per-VLAN policies sit alongside that segmentation but do not replace your compliance programme.
GDPR
The EU General Data Protection Regulation (Regulation (EU) 2016/679), with UK GDPR alongside it. Article 33 requires controllers to notify the supervisory authority of a personal data breach, where feasible within 72 hours. Blocking phishing and malware domains reduces the chance of a breach that triggers GDPR reporting duties. Purple is GDPR certified, alongside ISO 27001, CCPA and Cyber Essentials.

Worked examples

A hotel runs a guest SSID, a staff SSID, a conference SSID and a back-office VLAN for point-of-sale systems. OpenDNS Home only allows one setting per registered network. How should it set DNS policy?

The hotel moves to network-level protective DNS with Purple Shield, which sets policy per SSID, VLAN and venue from one dashboard. The family-facing guest SSID blocks adult content. The staff SSID allows social media for the marketing team. The payments VLAN reaches almost nothing beyond its processors. Nothing is installed on guest phones, because every device inherits policy the moment it joins. For a group, the team writes one guest policy once, applies it across 200 sites, then overrides it where a venue needs something different. Outbound port 53 is redirected to Shield and known public resolvers are blocked, so hard-coded DNS and DNS over HTTPS cannot bypass the policy.

A multi-site operator still filters venue WiFi through OpenDNS, with some sites on Cisco Umbrella and one site manager using a personal OpenDNS account set up years ago. How does it migrate?

The team follows a six-step sequence. It audits DHCP scopes, firewall DNS forwarders, router settings and any Cisco Meraki Umbrella integration, which surfaces the personal account so it can be brought under central control first. It maps blocking categories to each SSID and VLAN. It pilots one venue on Shield's 30-day free trial and compares block reports with what OpenDNS showed. It closes bypass routes by redirecting outbound DNS. It rolls out site by site, recording each old configuration for rollback. Umbrella roaming clients on staff laptops run as a separate endpoint workstream. Finally, it ends the OpenDNS or Umbrella subscription at renewal.

Frequently asked questions

Is OpenDNS still free?

Yes, for home use. OpenDNS Home and FamilyShield remain free resolvers aimed at households, and Cisco directs business networks to its paid Cisco Umbrella packages. A free home resolver offers no service-level commitment, limited reporting and no multi-site control. For a hotel, pub, store or airport, that leaves you running business WiFi on a consumer product with no say over service changes.

What replaced OpenDNS Umbrella for small operators?

Cisco Umbrella replaced it, sold as tiered packages licensed per user. For small operators running WiFi rather than fleets of managed laptops, a WiFi-native protective DNS is often the closer fit. Purple Shield applies a policy per SSID, VLAN and venue from one dashboard, runs standalone or on Purple Access, and starts with a 30-day free trial on your own network.

Is there a protective DNS without per-user seats?

Yes: network-level protective DNS applies policy per network, not per enrolled person. Shield protects every device on a filtered SSID or VLAN, so guests need nothing installed and nothing assigned to them. Purple prices Shield through a tailored quote rather than a public list, so ask us how it would be scoped for your estate during the 30-day free trial.

Will Shield work with the WiFi hardware I already own?

Yes. Shield works at DNS, so it needs no new hardware and no specific access point vendor. It runs on networks built with Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet. You change where each network sends its DNS queries, then set the policy for that SSID or VLAN in the Shield dashboard.

How long does migrating from OpenDNS take?

Effort scales with your number of networks, not your hardware, because migration is mostly DNS changes and policy design. Audit where OpenDNS is configured, map its categories to Shield policies per SSID and VLAN, then pilot one venue. Plan that pilot to finish inside the 30-day free trial, close DNS bypass routes, and roll out site by site with a rollback record.

How does Shield compare with Cisco Umbrella and Cloudflare Gateway?

Shield is built for WiFi operators, while Umbrella and Gateway are built around people and managed devices. Umbrella sits inside Cisco's security portfolio and Gateway inside Cloudflare One, and both are licensed per user. Shield covers unmanaged guest devices with no agent and runs at Whitbread and AGS Airports. See [Shield vs Cisco Umbrella](guide:shield-vs-cisco-umbrella) for detail.

Does Shield help with GDPR and PCI DSS?

Shield supports your compliance programme but does not replace it. Blocking phishing and malware domains reduces the chance of a breach that triggers GDPR reporting duties. Under PCI DSS, segmenting guest WiFi from cardholder systems reduces your assessment scope, and Shield's per-VLAN policies sit alongside that segmentation. Purple holds ISO 27001 and Cyber Essentials certification and is GDPR and CCPA certified.

How much does Shield cost?

Shield is priced through a tailored quote, not a public list price. The quote reflects your estate and whether you run Shield standalone or on Purple Access. Every deployment can start with a 30-day free trial, so you can measure blocked threats and DNS query reduction on your own network first. Request both on the [Shield pricing page](product:shield/pricing).

Sources

Decide what your network reaches, free for 30 days

Tell us your networks and who uses them, and we map a policy to each. Point one at Shield and see what it stops for 30 days.

Tell us your networks. We map a policy to each one.