SPIRITTDNSFilter

Turn DNS policy into operations
Keep protection accountable

Operate DNSFilter networks, filtering policies and threat follow-up using real query evidence and device coverage. Create scoped filtering rules and verify the intended network configuration without overwriting unrelated exceptions.

SPIRITT Workspace input reading Connect me to DNSFilter, with the DNSFilter icon in a compact app tile.

What you can do with DNSFilter.

  • Policies applied precisely

    Create scoped filtering rules and verify the intended network configuration without overwriting unrelated exceptions.

  • Threat evidence into response

    Use query logs and threat summaries to route concrete incidents to security owners.

  • Coverage made visible

    Connect roaming-client status and network inventory to a maintained protection dashboard.

Get started in three steps.

01

Open your workspace

Start a SPIRITT workspace for policies applied precisely and give it your operating priorities.

A workspace connected to software projects
02

Connect DNSFilter

Connect your DNSFilter account and choose the records and actions this workspace may use. Name networks and permitted policy changes; keep customer data separated.

SPIRITT Workspace input reading Connect me to DNSFilter, with the DNSFilter icon in a compact app tile.
03

Delegate an outcome

Ask SPIRITT to build a protection console. It carries the work through and checks the result.

Code, project files, and recurring workflow arrows

Keep protection accountable

Questions

DNSFilter, with SPIRITT.

01Can it change DNS filtering policies?+
Yes. It can create or update policies, manage domain and application exceptions, and apply configurations to named networks.
02Can it prove a device is protected?+
Configuration and observed activity are separate evidence. SPIRITT uses agent protection status and available query records, rather than assuming registration proves traffic is filtered.
03How are bulk changes verified?+
Bulk network updates are asynchronous. SPIRITT checks the job result and reports successful, failed and skipped targets separately.
04Can it build weekly schedules?+
Yes. Scheduled policies use exactly 672 quarter-hour policy slots across a week, which SPIRITT can construct from an approved timetable.
05How much real-time traffic can it inspect?+
Several active QPS and client-stat views have a maximum 20-minute window. Longer analyses use the appropriate aggregate reports and explicit time ranges.
06Can it delete inactive agents?+
Cleanup and bulk deletion exist, including options with remote uninstall. Those require explicit target approval; routine coverage reviews do not delete devices.
Buy from builders who use what they sellBuilt usingSPIRITT