Insights
DNS malware protection: how filtering works and what to check
Learn how DNS malware filtering works, where protection stops, what to check in a service and how to interpret blocked requests.

On this page
DNS malware protection uses a filtering Domain Name System (DNS) resolver to check requested domains against threat information. It can block lookups for known or suspected malicious sites, including malware download sites and servers that send malware commands. It's an extra layer of protection, not a replacement for device security.
In short:
- Block risky lookups. Filtering can interrupt domain-based malware communication when requests reach its resolver.
- Coverage has limits. Traffic using Internet Protocol (IP) addresses directly bypasses DNS checks.
- Check block records. A matching policy event shows filtering acted, not that your device is infected.
How the filter stops a risky lookup
A resolver is the service that answers your device's requests to turn domain names into IP addresses. A protective DNS serviceOpens in a new tab adds threat checks to that process. Protective DNS is a service, not a separate protocol.
The resolver usually checks both requested domains and returned IP addresses against threat information. It can then deny the lookup or return an answer that stops communicationOpens in a new tab. Some services also alert you about the blocked attempt.
Hypothetical example: Malware already on a device tries to contact a server that sends it commands. Your device requests that server's domain, and the filtering resolver checks its policy. If the policy blocks the domain, the resolver denies normal resolution, which can interrupt that communication. It doesn't remove the malware already on your device.
What DNS filtering can't stop
Filtering checks requests that reach the service. Traffic sent directly to an IP address skips DNS, so the filter gets no lookup to check. An app using another resolver can also bypass your chosen filterOpens in a new tab.
Protection also depends on the service's threat information and the policies you enable. A domain filter doesn't inspect every downloaded file or distinguish safe and harmful files hosted under the same domain. Use filtering alongside antivirus software, a firewall and safe browsing habits. Keep device updates in place too.
DNS encryption and filtering do different jobs. Encrypting a lookup doesn't classify its destination as safe, and encrypted DNS doesn't hide all browsing activityOpens in a new tab. Choose filtering for domain policy checks, not because the word “encrypted” promises malware protection.
What to check before you choose a service
Use these checks to match the service to your network and the controls you need.
| Service requirement | Why it matters | What to check |
|---|---|---|
| Threat coverage | Recognition depends on threat information | Covered categories and update process |
| Device coverage | Requests must reach the filter | Home, roaming and managed-device support |
| Resolver control | Apps can choose another resolver | Browser and app DNS policies |
| Service reliability | Lookup failures can disrupt access | Availability, latency and outage behavior |
| Narrow exceptions | Mistaken blocks can stop needed work | Targeted overrides and review process |
| Logging and retention | Records help explain blocks but reveal requested domains | Recorded fields, access controls and retention |
Changing a router's DNS setting can enable filtering for requests that follow that setting. It doesn't prove that every app uses the same resolver. It also doesn't establish coverage for devices away from home. Check the resolver used by your intended devices and apps before treating the change as network-wide protection.
Basic public filtering can suit personal use. If you need to see and change what's blocked, look for a dedicated filtering product with those controls. Enterprise networks should also assess alerts, historical records and high availability. A service's count of blocked domains doesn't answer those operational questions.
Check what a blocked request really means
A matching policy event can identify a filtering action. A failed lookup alone leaves the cause unresolved.
A failed lookup alone isn't proof that malware was blocked. Carnegie Mellon's Software Engineering Institute guidance gives a firmer basis: records should identify what was blocked, when, the requesting device or network, and the policy triggered.
1. Record the request details.
Write down the requested domain, the time, the affected device and the selected resolver. Add any available filtering event or policy reason. These are the inputs you'll need to connect a lookup result to a policy action.
2. Look for a matching filtering event.
Compare the domain, device and time with the service's records. If they match and the event names a policy, treat that as evidence that the named policy acted. It doesn't prove that the device is infected.
3. Leave an unexplained failure unresolved.
If you only have a failed lookup, mark the cause as unknown. Check whether the resolver is available, then review any policy records you can access. Public resolvers may not provide device-level records, so you may be unable to connect the failure to a specific filtering rule.
4. Review the reason before requesting an exception.
Check the stated block reason before deciding that access should be allowed. If you need legitimate access, request a narrow exception instead of disabling filtering across the network. Only change networks you own or administer, and preserve the original policy with a way to restore it if the change causes trouble.
5. Investigate unexpected repeated requests.
Check which device and app are making the requests, then use your device security tools to investigate. Repeated blocks deserve attention, but they don't prove infection. A block record also doesn't tell you whether every file from a domain is safe.
Your notes should now name the rule that acted or clearly mark the cause as unknown. That distinction is the success check: you can explain the evidence without counting failed lookups as confirmed attacks prevented.
Where doxx.net fits. doxx.net encrypts DNS lookups and blocks unwanted domainsOpens in a new tab, but those features aren't a guarantee of malware detection. If that fits your needs, create a doxx.net account, download the app and connect a device or agentOpens in a new tab.