Skip to main content
Coplango
Request a BGP and peering review

Nameward

Threat and content filtering on ISP resolvers

ISPs have to block malware domains, apply required blocklists and know what their resolvers are answering, without slowing anyone down. Nameward does that on your own resolvers.
Ask for a demo
How Nameward handles a DNS queryA subscriber’s query reaches your resolver, which checks the name against local threat and category lists. Allowed names are answered as usual; blocked names get the response your policy defines. Every query and decision goes to the query log.SubscribersResolverAnsweredBlockedQuery log
  • Allowed queries
  • Blocked queries
  • Stopped by your policy

Who it’s for

ISPs and carriers that run their own resolvers and need filtering, compliance with required blocklists, and visibility into DNS traffic.

What it does

  • Filtering in the resolver

    Threat and category lists held in memory-mapped databases next to each resolver process, so a lookup is a local read.

  • Lists that update in place

    Feeds and required blocklists sync as incremental changes, without restarting resolvers.

  • Every query, searchable

    Query logs stream from the resolvers’ dnstap feed into a searchable store for reports, investigations and anomaly detection.

  • One console

    Policies, lists, resolvers and analytics in one place.

How it works

  1. Query arrives

    A subscriber’s resolver receives the query as usual.

  2. Checked against lists

    The policy module looks the name up in the local threat and category databases.

  3. Answered or blocked

    Allowed names resolve normally; blocked names get the response your policy defines.

  4. Logged for analysis

    The query and the decision are stored for reporting and detection.

See it on your own network.

We’ll walk you through it with data that looks like yours, and tell you honestly whether it fits.

Ask for a demo