Skip to main content
Pixa Teknologi

DNSFilter: DNS Security & Web Protection

Restrict connections to phishing, malware, and restricted web categories. DNSFilter enforces policies on DNS queries across office networks and configured remote worker devices.

  • Malicious domain blocking
  • Web category access filtering
  • Off-network device protection

Web Access Risks

Threats from Links and Domains

Links arrive through email, chat, documents, search results, ads, and applications. Without DNS-layer protection, users and devices can still connect to malicious domains or web categories outside company policy.

Protection should also follow staff when working from home, public networks, or off-site locations.

Risky Access Patterns

Filtering priorities depend on threat types, web categories, work locations, and device setup.

  • Users clicking phishing links from email, chat, or shared documents.

  • Devices connecting to malware hosts, botnets, or command-and-control domains.

  • Access to web categories outside company policy.

  • Remote staff working over untrusted external networks.

  • Lack of team visibility into DNS requests and blocked domains.

Deployment

Network and Endpoint Protection

Configure DNS forwarding for office networks or deploy supported roaming clients on mobile staff devices. Policies cover threat categories, acceptable web use, and necessary allowlists.

  1. DNS Query Inspection

    DNS requests routed through DNSFilter are checked against your active policy.

  2. Threat & Category Matching

    Domains are evaluated against threat intelligence feeds and web content categories.

  3. Risky Domain Blocking

    Domains matching policy rules or threat feeds are blocked before connection, while safe queries resolve.

  4. Activity Logging & Reports

    DNS request logs and block events are recorded in the dashboard for administrator review.

DNS and Web Controls

Filtering at the DNS Layer

DNSFilter combines malicious domain blocking, web content filtering, remote roaming protection, and DNS reporting in one cloud service. DNS filtering complements endpoint and email security and applies to DNS requests routed through the service.

  • Protective DNS

    Inspect DNS lookups and block known malicious domains before a connection is established.

  • Phishing and Malware Protection

    Helps block domains linked to phishing, malware, ransomware, and botnets using vendor threat feeds.

  • Content Filtering

    Enforce internet usage guidelines across web content categories.

  • Roaming Client

    Apply consistent DNSFilter protection on supported devices both inside and outside office networks.

Visibility through Reporting

DNS query logs help IT teams monitor requested domains, blocked traffic, and policy exceptions that may need tuning.

Our Support

Policies Tailored to Work Patterns

We review office networks, branch sites, and remote devices, prepare initial policies, and validate critical business sites. Implementation and post-rollout tuning follow your agreed scope.

  1. Identify work locations, networks, users, and devices.

  2. Choose protection methods for office networks and remote endpoints.

  3. Define threat rules, web categories, allowlists, and blocklists.

  4. Complete initial setup and test essential business URLs.

  5. Review block logs and refine filtering rules.

FAQ

Frequently Asked Questions

How does DNSFilter differ from antivirus or a firewall?

DNSFilter inspects DNS queries and blocks domains by threat intelligence or web category. Antivirus protects the device OS and files, while firewalls govern network traffic. Together they complement one another depending on your IT setup.

Can DNSFilter cover main offices and branch locations?

Yes. Network DNS settings can route requests through DNSFilter. Each site is reviewed based on ISP connections, routers/firewalls, and access policy needs.

How are employees protected when working outside the office?

Supported Roaming Clients enforce DNS policies even as users move across home or public Wi-Fi networks. OS compatibility, install permissions, and device setup are checked beforehand.

Does every device require installing an application?

Not always. Office-wide protection uses network DNS settings, while off-site endpoints generally use the Roaming Client for consistent policy enforcement and per-device reporting.

What happens if a required business website gets blocked?

Check the domain, block category, and active policy. Administrators can adjust category rules or add reviewed domains to an allowlist, while ensuring alternative DNS or VPN software does not bypass enforcement.

DNS and Web Protection Aligned with Work Patterns

Share your network setup, device types, and access policies. We will help evaluate relevant DNSFilter deployment scenarios.