Skip to content
Shield

ToolDNS filtering alternatives

A 30-day DNS filtering trial plan for a venue estate

Use this plan to scope a 30-day DNS filtering pilot across your venue estate and agree pass marks before day one. You will size the pilot, count the network policies to build, and set a false-positive cap and query reduction target. You can then roll out, extend or stop on a score, not a debate.

12 min read

A 30-day DNS filtering trial plan for a venue estate

Watch the explainer

Use this to scope a 30-day DNS filtering trial plan for your venue estate; at 40 venues and a 10% pilot, it returns four pilot venues. Add three networks per venue and 50,000 DNS queries per venue a day. You get 12 policies, 4.2 million logged queries, a six-ticket false-positive cap and a 30,000-query daily reduction target.

What does this DNS filtering trial plan output?

Start with placement, because it shapes every test in the pilot. Protective DNS filters at the resolver, the service that turns a domain name into an IP address. Every device makes that lookup before it connects. Purple Shield answers the lookup and refuses it when the domain is malicious or sits in a blocked category. The device never opens a connection to the blocked domain.

Filtering at the resolver, not on the access point, means you trial it with no new hardware. You change where each network sends its DNS queries, not what is installed in the ceiling. That keeps the pilot cheap to start and quick to reverse.

The tool turns your estate size and pilot choices into five numbers for a project plan:

  • Pilot venues: how many sites join the trial, never fewer than two unless your estate is smaller.
  • Network policies to build: one per SSID or VLAN at each pilot venue. An SSID is the network name a guest sees. A VLAN (virtual LAN) separates traffic on shared cabling.
  • Logged queries: the DNS lookups you will hold from enforce mode, so you know the sample is big enough to judge.
  • False-positive cap: the most tickets for wrongly blocked sites you accept before the pilot fails.
  • Reduction target: the daily DNS queries the pilot must remove against its baseline week.

Together they give you a pilot with pass marks agreed before the first day, not argued after the last. Shield's published effects are measurable, which is why the tool sets numeric tests. Purple's own data shows up to 62% fewer DNS queries and up to 44% less data on filtered networks. Not every venue will reach those ceilings, so the tool lets you set your own pass mark. For the wider category, start with our overview of DNS filtering alternatives.

The 30-day pilot calculator

Enter your estate, then adjust the pilot share and pass marks until the scope fits your team's capacity.

30-day DNS filtering pilot calculator

Enter your estate and pilot choices to get the pilot scope and pass thresholds.

Pilot venues

4

DNS queries logged in enforce mode

4,200,000

False-positive ticket cap

6

Daily queries the pilot must remove

30,000

Worked example: At 40 venues, a 10% pilot, 50,000 queries per venue a day, 21 enforce days, 0.5 tickets per venue a week and a 15% pass threshold, the result is 4 pilot venues, 4,200,000 logged queries, a 6-ticket cap and 30,000 fewer queries a day.

Assumptions
  • Pilot venues are the pilot share rounded up, never fewer than two unless the estate is smaller.
  • Daily queries come from one normal week of your current resolver or firewall logs.
  • The 30 days split into a 7-day baseline, 21 enforce days and 2 review days.
  • The reduction target compares enforce-mode daily queries with the baseline average.

Worked example: a 40-hotel estate on three networks

Take a fictional hotel group with 40 properties. Each hotel runs three networks: Guest WiFi, Staff WiFi and a back-office VLAN for property systems. Newer hotels run Cisco Meraki and older ones run HPE Aruba. Shield does not care which, because it works at the DNS layer.

These are the inputs the IT security manager entered, with the reasoning behind each:

Input Value Why this value
Venues in the estate 40 The whole group, including franchised sites
Pilot share 10% Four hotels: city center, roadside, resort and conference
Networks per venue 3 Guest, staff and back office
DNS queries per venue per day 50,000 Illustrative; read yours from a normal week of resolver logs
Days in enforce mode 21 The middle three weeks of the 30 days
Tickets accepted per venue a week 0.5 One wrongly blocked site per hotel per two weeks
Reduction pass mark 15% Conservative against Purple's up to 62%

At those inputs the tool returns four pilot hotels and 12 network policies to build. Across 21 enforce days the pilot logs 4.2 million queries, a sample large enough to judge. The false positive cap is six tickets across all four hotels. The reduction target is 30,000 fewer queries a day, taking the four hotels from 200,000 to 170,000 daily.

Those outputs become the pass marks in the scorecard below. Every test has a measure, a threshold and a week in which it is judged.

Success tests for the 40-hotel worked example Data as of 2026-06-10
TestWhat you measurePass markJudged in
Policy separationEach SSID and VLAN applies its own policyTest list gives the expected result on all 12 networksWeek 2
Threat blockingMalware and phishing domains blocked per hotelBlocks logged at all 4 pilot hotelsWeeks 2-4
Content policyBlocked categories on Guest WiFiNo blocked-category test site resolves on any guest networkWeek 2
Bypass resistanceEncrypted DNS and hard-coded resolver testsBlocked or redirected on every pilot networkWeek 2
False positivesHelp desk tickets for wrongly blocked sites6 or fewer across the pilotWeeks 2-4
Query reductionDaily queries against the baseline average30,000 fewer a day across 4 hotelsWeek 4
Lookup speedMedian DNS response timeNo worse than the baseline weekWeeks 2-4
Venue reportingPer-venue report from one dashboardOperations reads each hotel's report without IT helpWeek 4
Pass marks come from the calculator at its default inputs.

How are the trial numbers built?

The 30 days split into four phases. The enforce phase sets the days input, so change the phases and you change the sample and the ticket cap.

Day 0Prepare pilot venuesPick venues, map SSIDs andVLANs, agree pass marksDays 1-7Baseline weekSecurity-only policy,record daily queries andticketsDay 8Switch on contentpolicyApply a category policy pernetworkDays 8-14TuneClear false positives, runbypass testsDays 15-28Hold steadyNo policy changes, collectthe sampleDays 29-30Review and decideScore each test, then rollout or extend
The 30-day DNS filtering pilot in four phases

A timeline running from preparation through a baseline week, content policy switch-on, tuning, a steady hold period and a final review.

Connections

  1. Prepare pilot venues to Baseline week
  2. Baseline week to Switch on content policy
  3. Switch on content policy to Tune
  4. Tune to Hold steady
  5. Hold steady to Review and decide

Each output follows from the inputs with no hidden weighting:

  • Pilot venues are your pilot share of the estate, rounded up. The floor is two, because one venue cannot separate a policy fault from a site fault. The ceiling is the estate itself: min(sites, max(2, ceil(sites*pct/100))).
  • Policies are pilot venues multiplied by networks per venue. Four hotels with three networks each give 12.
  • Logged queries multiply daily queries per venue by enforce days and pilot venues: 50,000 x 21 x 4 = 4.2 million.
  • The ticket cap scales your weekly rate to the enforce period, then rounds up: 0.5 x (21 / 7) x 4 = 6.
  • The reduction target applies your pass mark to the combined daily baseline: 50,000 x 15% x 4 = 30,000.

Four assumptions sit underneath, and each is visible in the tool. First, daily queries stay broadly stable across the month. Second, the baseline week is a normal week, not a federal holiday or a sold-out conference. Third, your helpdesk can tag tickets that mention blocked or missing websites. Fourth, you compare daily averages, not single days, so one busy Saturday does not decide the result.

For the baseline, point the pilot networks at Shield with a security-only policy. Alternatively, keep your current resolver for a week and export its query counts. A security-only baseline has one advantage: threat data starts on the first day. Shield flags threats earlier, so early blocks are worth recording.

How do you adapt it to your estate?

Match the pilot share to estate size

Small properties hit the floor quickly. A six-venue retail chain at 10% still pilots two stores, which is right. Large properties hit the opposite problem. A 500-venue property portfolio at 10% means 50 pilot venues and 150 policies to tune in a single week. Drop the share to 3% or 4% instead. At 4%, the tool returns 20 venues, still enough to cover every venue type you run.

Count every network, not just Guest WiFi

The networks input is where pilots most often go wrong. List every SSID and VLAN at a pilot venue, including point-of-sale (POS) and building-systems VLANs. Staff WiFi secured with IEEE 802.1X, the port-based network access standard, still needs its own DNS policy. Shield applies a policy per SSID, VLAN and venue from one dashboard, so each network gets the categories it needs. Guests get a family-safe policy, staff a business policy, and POS a tight allow-list.

Normalize for foot traffic

DNS volume follows people. A stadium on a game day or a shopping center in December will swamp a quiet baseline week. Where foot traffic swings, divide daily queries by daily visitors or occupied rooms before comparing. Then set the pass mark against queries per visitor, not raw totals.

Use the right test list per vertical

Build the content test list around the people on each network. Hotels test what guests reach, retail tests what shoppers reach, and airports test passenger networks. Healthcare tests patient and visitor networks separately from clinical VLANs. Higher education tests student networks, where encrypted DNS bypass attempts are most likely.

DNS over HTTPS (DoH) is defined in RFC 8484. DNS over TLS (DoT) is defined in RFC 7858. Both encrypt the lookup, which protects privacy but hides it from a resolver you did not choose. Test them on every pilot network, not just Guest WiFi.

Running Shield alongside Cisco Umbrella or Cloudflare Gateway

All three resolve DNS in the cloud, so the same eight tests apply to each. One network can only use one resolver at a time. Split the pilot by venue rather than running two services on the same SSID. Score each candidate on the same venue types and the same pass marks. Then compare how each maps policy to your real structure of venues, SSIDs and VLANs. For larger or managed properties, read DNS filtering for MSPs and multi-site estates.

What to do with the pilot result

Print or download the plan below and work through it with the venue operations manager. It follows the four phases, and each group closes before the next one opens.

30-day DNS filtering pilot checklist

0 of 17 done

Before the first day
Baseline week (days 1-7)
Tune (days 8-14)
Hold and review (days 15-30)

The decision follows from the scorecard. If every test passes, roll out in waves of venues that match your pilot types. Use the pilot policies as templates. If the ticket cap fails but everything else passes, the content policy is too tight. Loosen the categories that drove the tickets and extend the hold phase by 14 days. If the bypass test fails, fix the firewall rules before you judge anything else. An unfiltered path makes every other number unreliable.

If query reduction misses its mark, check the baseline first. A quiet baseline week makes any later week look worse. Rerun the comparison against queries per visitor before you call it a failure.

When the pilot passes, request a tailored quote through Shield pricing and use the tool's outputs as the scope. If you are still weighing a self-hosted or free resolver, read Pi-hole vs managed DNS filtering next. After that, read free vs paid DNS filtering. For how DNS filtering fits with network authentication and segmentation, see the enterprise WiFi security guide.

Key terms

Protective DNS
Filtering applied at the recursive resolver defined by the DNS protocol in RFC 1034 and RFC 1035. The resolver refuses to answer lookups for domains classed as malicious or in a blocked category, so the device never connects to them. This is where Purple Shield sits. Because it filters at the resolver, not the access point, you can trial it with no new hardware and reverse it by restoring the previous DNS setting.
DNS resolver
The service, specified in RFC 1034 and RFC 1035, that turns a domain name into an IP address on behalf of a client device. Every device makes this lookup before opening a connection. Your pilot changes which resolver each network hands out. Only one resolver can serve a network at a time, so comparing services means splitting the pilot by venue.
DNS over HTTPS (DoH)
A protocol defined in RFC 8484 that carries DNS queries and responses inside HTTPS, encrypting the lookup and sending it to a resolver chosen by the browser or app. DoH can bypass the resolver you configured. Bypass tests in week 2 confirm whether the firewall blocks or redirects known DoH endpoints on every pilot network.
DNS over TLS (DoT)
A protocol defined in RFC 7858 that encrypts DNS traffic using Transport Layer Security over a dedicated port, protecting lookup privacy from on-path observers. Like DoH, DoT hides lookups from a resolver you did not choose. A failed DoT bypass test makes every other pilot number unreliable, so fix it first.
SSID
The Service Set Identifier defined in IEEE 802.11: the network name a wireless access point advertises and a device selects to join. Shield applies a policy per SSID, so Guest WiFi and Staff WiFi at the same venue each count as a separate policy in the networks input.
VLAN
A virtual LAN as specified in IEEE 802.1Q, which tags Ethernet frames so separate logical networks share the same physical cabling and switches. POS, back-office and building-systems VLANs are the networks pilots most often miss. Each needs its own DNS policy, such as a tight allow-list for POS.
IEEE 802.1X
The IEEE standard for port-based network access control, which authenticates a device or user through an authentication server before granting network access. Staff WiFi secured with 802.1X still needs its own DNS policy. Authentication controls who joins the network, not which domains they can resolve.
DHCP
The Dynamic Host Configuration Protocol defined in RFC 2131, which assigns an IP address and network settings, including DNS server addresses, to a device when it joins. Before day one, confirm whether each network hands out DNS through DHCP or the wireless controller. That is the setting you change to start and end the pilot.
False positive
A legitimate domain blocked by a filtering policy because it was misclassified as malicious or as part of a blocked content category. The ticket cap sets how many wrongly blocked sites you accept before the pilot fails. Allow-list business sites within one business day during tuning.
Baseline week
A normal seven-day period of DNS query counts and helpdesk tickets recorded under a security-only policy or from your current resolver logs, used as the comparison point for enforce mode. The reduction target compares enforce-mode daily averages with this baseline. Avoid federal holidays or sold-out events, which skew the comparison.
PCI DSS
The Payment Card Industry Data Security Standard published by the PCI Security Standards Council, setting security requirements for any environment that stores, processes or transmits cardholder data. Filtering a POS VLAN cuts exposure to malicious domains, but network segmentation sets your PCI DSS scope. Confirm it with your Qualified Security Assessor.
CCPA/CPRA
The California Consumer Privacy Act and California Privacy Rights Act, which govern the processing of personal data, including principles on storage limitation and security. DNS logs can include device IP addresses, so set retention and access rules before the baseline week starts.

Worked examples

A fictional hotel group runs 40 properties on Cisco Meraki and HPE Aruba, each with Guest WiFi, Staff WiFi and a back-office VLAN. How should the IT security manager scope a 30-day DNS filtering pilot?

The manager set a 10% pilot share, giving four hotels: downtown, roadside, resort and conference. Three networks per hotel meant 12 policies to build. Using an illustrative 50,000 DNS queries per venue a day and 21 enforce days, the pilot logs 4.2 million queries, a sample large enough to judge. A rate of 0.5 tickets per venue a week gave a cap of six false-positive tickets across the pilot. A conservative 15% pass mark set a target of 30,000 fewer queries a day, taking the four hotels from 200,000 to 170,000 daily. Mixed hardware did not matter, because Shield works at the DNS layer.

A 500-venue estate applies the default 10% pilot share and gets 50 pilot venues and 150 policies to tune in a single week. How should it adjust the plan?

At 10%, the tuning week becomes unmanageable for the team. The plan recommends dropping the share to 3% or 4% above around 100 venues. At 4%, the calculator returns 20 pilot venues, which is still enough to cover every venue type the estate runs. The team can then clear false positives, run bypass tests and tune every policy during days 8 to 14. Where foot traffic swings between venues, the team should also divide daily queries by visitors before comparing, so busy sites do not distort the reduction result.

Frequently asked questions

How much does a 30-day Shield trial cost?

The trial is free for 30 days, and Purple then prices Shield on a tailored quote. The quote reflects your estate: venue count, networks to filter, and whether Shield runs standalone or on Purple Access. Use this tool's outputs, pilot venues and policies, as the scope for that conversation. Request the trial and a quote from the [Shield pricing](product:shield/pricing) page.

Will Shield work with the access points we already own?

Yes. Shield filters at the DNS layer, so it works on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet networks alike. You change the DNS server each network hands out, usually in DHCP or the wireless controller. No new hardware goes in. To end the pilot, restore the previous DNS setting.

How many venues should be in a DNS filtering pilot?

Use two at minimum, and enough to cover every venue type you run. One venue cannot tell a policy fault from a site fault. For most properties, 10% works up to around 100 venues. Above that, drop to 3% or 4%, so the team can tune every policy during the second week of the pilot.

How does Shield compare with Cisco Umbrella and Cloudflare Gateway in a trial?

Run all three against the same eight tests, because each resolves DNS in the cloud. The useful difference is how policy maps to a venue property portfolio. Shield applies a policy per SSID, VLAN and venue from one dashboard, so guest, staff and POS networks each get their own rules. Score each candidate on the same venue types and pass marks.

How do we migrate from an existing DNS filter after the pilot?

Migrate venue by venue, with the pilot venues as your template. Rebuild your category policy per SSID and VLAN in Shield, then repoint each network's DNS in waves. Keep the old service live for venues not yet moved, and run the bypass and policy tests after each wave. The [Cisco Umbrella pricing guide](guide:cisco-umbrella-pricing) covers the cost side.

Does DNS filtering help with CCPA/CPRA and PCI DSS?

It supports both, but it does not make you compliant on its own. DNS logs can include device IP addresses, so set retention and access rules before the baseline week. Purple is ISO 27001 certified and CCPA/CPRA compliant. For PCI DSS, filtering a POS VLAN cuts exposure to malicious domains, but segmentation sets your scope. Confirm it with your Qualified Security Assessor.

How much staff time does the pilot need?

Most of the effort falls on preparation and the tuning week. Mapping networks, exporting baseline counts and running the bypass tests take the bulk of IT's time. During the hold phase, the team reviews tickets daily and makes no policy changes. The final review needs both owners together for the two closing days of the plan.

Can we run Shield without Purple's guest WiFi?

Yes. Shield runs standalone on any network, or on Purple Access if you already use it for guest or staff onboarding. Either way, you set a policy per network and VLAN, so the trial plan is the same. Purple runs at 80,000+ venues in 90 countries, and Shield works on the network you already have.

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.