Features

Four groups of features in one panel

From subscriber protection to the health of every resolver - with checks, signatures and reports.

Subscriber protection

Filtering the harmful and the unwanted

Protection levels and the phishing filter are switched on for an organization separately from blocking by law. Organization exceptions apply to protection levels only.

NCSCC phishing filter

The state list of phishing domains. The core fetches it itself, checks it, signs it and delivers it to your servers - nothing to set up by hand. Switched on with a toggle; the subscriber sees "site not found" or an NCSCC warning page.

Protection levels L1-L3

L1 - malware and phishing, L2 - plus ads and trackers, L3 - plus adult content. Every list shows since when a domain has been in it, and what changed in the last day.

Levels for individual subscribers

module

The network runs at the organization level, and selected subscribers can be given a higher one, for example a family level. Works on servers with dnsdist; your billing keeps the subscriber list and hands it to the agent on the server, and addresses never go to the core.

Memory estimate

Before a move to L2 or L3 the panel shows, for every server, how many domains will be added and how much memory that takes. If a server falls short, the switch stays off.

Maintenance window

Large lists can be applied immediately or in a nightly window. Blocking by law and your own blocks are always applied immediately.

Organization exceptions

Domains you do not want blocked by protection levels. They never apply to blocking by law.

Sources have open licenses; the full list is at get.argusdns.net/LICENSES.txt.

Blocking by law

Where decisions come from

One list for every provider, and every domain shows all its grounds with documents.

NCU

Decisions restricting access to resources.

Courts

Court decisions on blocking.

PlayCity

Decisions restricting access to gambling sites.

National Council

The list of the aggressor state's media services.

Maintaining the list

We maintain the list

You do not have to follow decisions or enter domains: that is our job. You only see the result on your servers and in the report.

We follow, verify, sign

New decisions reach us right after publication, and we check every change before it is published. Within a minute the signed version is live on all your servers.

Unblocking by order

An order refers to its own ground, and only that ground is removed. Other decisions about the domain stay in force.

Import of your list

If you already have a blocklist, we import it with decision numbers so nothing gets lost in the move.

Compliance report

For every decision - when each server applied it. CSV and PDF for any period.

Protected domains

Banks, state services, CDNs: they cannot be blocked even by a mistaken decision.

Network security

Seeing what general statistics do not show

Subscriber anomalies

module

Query spikes, a high NXDOMAIN share, signs of DNS tunneling - with a "put on watch" button next to them.

Domain diagnostics

Enter a domain and the core checks it on all your resolvers and compares it with 8.8.8.8 and 1.1.1.1. You see which list the domain is in (with the decision number) and why the server answers as it does. Next to it: flush the cache, refresh lists, add to your own blocks or exceptions.

Own blocks

Your own domain list on top of blocking by law, without grounds or documents. Applied without restarting the resolver.

Raw query log

module

The log is written only on the resolver; search by client and domain from your panel.

A check that the list really blocks

The agent on every server checks a control domain, and diagnostics shows, for any domain, a foreign rule that overrides the list.

Domain watch

Which subscribers query a chosen domain and its subdomains, and how often. A counters-only mode works without recording every query.

Command server registry

A registry of malware command servers (C2) shared between organizations: marks in watch reports and a "Block for organization" button. Only numbers are shared between organizations, never subscriber addresses.

Third-party DoH and DoT

For subscribers on watch you can close third-party DNS encryption services so queries do not bypass your resolver. Attempts show in the subscriber report.

Subscribers with their own DNS server

The system spots subscribers who run their own recursive DNS server, and a suspicious flow of foreign DNS answers arriving at your servers.

Client watch

Where a subscriber's device goes

When a server shows a subscriber with thousands of queries a minute or a high NXDOMAIN share, you can put them on watch.

IP or prefix for a set time

module

Add a subscriber from the anomaly list or by hand for 24 hours, 7 or 30 days. Extend or remove with one button.

A report with signals and numbers

Domains, frequencies, NXDOMAIN, answers; signals: a steady beacon, random names (DGA), rare domains. For each domain you see how many times other subscribers queried it in the last day and how many subscribers hit it.

Full list and export

All the client's domains for the period, without truncation. Export to xlsx, pdf or csv with no row limit, with an explanation for every domain. What you find can be blocked in one click.

This is subscriber personal data, so only queries of clients on the watch list are kept in the core, for 30 days, and every addition and export leaves an audit record. The core does not see queries of other subscribers. For subscribers on DoT, on servers without dnstap, watch does not work: packet capture cannot see encrypted traffic.

Resolver health

What is happening on every server

Statistics with no changes to unbound

The source is dnstap or packet capture, so it works on FreeBSD too, where there's no dnstap. unbound counters have their own tab.

DoT, DoH and certificates

The agent warns ahead of time that a certificate is about to expire, and when it has been renewed on disk but the port still serves the old one. The server card shows queries and errors for every listener.

Applied settings

The panel shows whether the latest revision of the organization settings is in force on every server. If the config was edited by hand after applying, you get a warning listing the files.

Alerts

Server offline, list outdated, low disk space, a load spike or drop, SERVFAIL share, resolver did not come back after a restart, certificate expiring. Alerts in a messenger and in the panel.

Agent auto-update

A new version rolls out to servers by itself; if it doesn't come up, it's rolled back. Only the first install is manual.

Resolver checks

Every minute the organization servers check themselves and each other over plain DNS, DoT and DoH, certificate included. The core evaluates the result and alerts you about a failure.

Updates without interruption

On current unbound versions lists update without stopping answers to subscribers. Large zones reach servers one after another, not all at once.

Auto-restart and memory

If you enable it, the agent restarts a DNS service that stopped answering, or a service that grew past its memory limit, with a cap on attempts.

Compatibility

unbound 1.17 and newer, and other resolvers that work with RPZ files.