R50 per seat per month, from 25 seats • Nothing to install on agent PCs • Starts in shadow mode

Your Agents Handle Card and ID Numbers All Day
Keep Them on the Floor

Call-centre agents read out and type card numbers and SA ID numbers on every shift. ZDNS stops card numbers, ID numbers and fake bank and courier sites at the network, for the whole floor, from one router setting. Nothing is installed on agent PCs, and work-from-home agents are covered too. Unlike filters that only block sites already known to be bad, ZDNS also looks inside every lookup, so a number heading for a brand-new domain is still stopped.

A working day at a 50-seat office
Every lookup is checked; the ring shows what was blocked, by kind.
SIMULATION
0lookups checked08:00
Blocked0
  • Card numbers0
  • SA ID numbers0
  • Mobile numbers0
  • Account numbers0
  • Scrambled codes0
waiting for the first block...

Simulated: one office day (08:00–17:00) replayed in a minute. Volumes and block counts are illustrative, not customer data. Customers see their own real numbers on their dashboard.

R50 per seat per month, from 25 seats. No long-term contract.

CHECKSUM-VERIFIED

Reads What's Inside the Lookup

Malware hides stolen data inside the name it looks up. ZDNS checks every name for card numbers and SA ID numbers, confirmed with the same checksum banks use, plus mobile and account numbers and scrambled codes, before the lookup is answered.

ONE ROUTER SETTING

Nothing to Install

No agents on PCs, softphones or laptops. Point your router or DHCP server at ZDNS and every device on the network is covered, served by two resolver addresses on two separate hosting providers.

RECORDS YOU CAN SHOW

Proof of What You Did

POPIA asks for reasonable security measures. ZDNS is one more, and it keeps the receipts: every block is recorded with the time and what was found, and a plain-English report explains each one.

Built to Run Quietly

Designed for busy call centres and the IT partners who look after them.

Three Servers, Two Providers

If the main resolver stops answering, a standby takes over the same address on its own (about 30 seconds in testing). The second address runs at a different hosting provider, so offices stay filtered even if one provider goes down.

Known Phishing Sites Blocked Too

Every site name is also checked against Google's list of suspected phishing, malware and unwanted-software sites (Google Web Risk), without telling Google who asked. Some risky sites may not be identified, and some safe sites may be identified in error.

Work-from-Home Agents Too

Remote agents are seats like any other: the same R50 a seat a month and the same dashboard as the floor. Each home laptop or phone gets its own private address, so protection follows it on home Wi-Fi and mobile data. How it works →

Fast Enough Not to Notice

Repeat lookups are answered in about 5 ms and first-time lookups in about 40 ms (medians, measured in the datacentre), with every check included.

Your Own Dashboard

See every block, whitelist a site in seconds, pause blocking in an emergency and trace a lookup back to the PC. Partners see all their clients in one place.

Tested Around the Clock

Fake card and ID lookups are fired at the resolver every few minutes to prove blocking still works, and an outside monitor checks the service every minute. Suspicious-but-uncertain lookups are held about four seconds, then blocked, so slow leaks grind to a halt.

Help When You Need It

An AI setup helper answers around the clock, alerts and unblock requests go through our Telegram bot, and emails to support@zdns.co.za are answered within one working day.

How a Leak Is Stopped

Firewalls let DNS lookups through, so malware uses them to carry data out. Here is what happens when a lookup carries a card number.

1

A PC Is Compromised

Malware on an agent's PC tucks a card number into a lookup for a server the attacker controls:4111111111111111.collect.example

2

ZDNS Checks the Name

Before answering, ZDNS spots a 16-digit number that passes the card checksum. Split with dots or dashes, or tucked inside a word, it's still found.

3

The Lookup Goes Nowhere

ZDNS answers "does not exist", so the lookup never reaches the attacker's server. The block appears on your dashboard with a button to find the PC.

Internal Call FloorSECURE
Workstation Agent [10.0.12.44]
4111111111111111.collect.example
NXDOMAIN
ZDNS ResolverCHECKING
Z
Number and pattern checks

Blocklists Check the Address. ZDNS Checks the Contents.

A blocklist only knows about bad domains someone has already reported. An attacker can register a fresh domain today and it sails through. ZDNS looks at what the lookup is carrying instead, and also checks Google's list of known phishing and malware sites.

What gets checked
Blocklist-only filters
The domain, against a list of known bad sites
ZDNS
What's inside every lookup
A brand-new attacker domain
Blocklist-only filters
Allowed until someone reports it
ZDNS
Blocked if it carries a card, ID or account number
SA ID and mobile numbers
Blocklist-only filters
Not looked for
ZDNS
Checked in every lookup, with the ID check digit verified
Before blocking starts
Blocklist-only filters
Usually blocks from day one
ZDNS
About a week in shadow mode: you see what would be blocked first
Price
Blocklist-only filters
Usually priced per user in US dollars
ZDNS
R50 a seat a month, from 25 seats, no contract

ZDNS also blocks sites on Google's list of suspected phishing, malware and unwanted-software sites, so you may not need a separate filter for those. Google cannot guarantee its list is complete or error-free: Some risky sites may not be identified, and some safe sites may be identified in error.

NOTHING IS BLOCKED IN WEEK ONE

Protected by the End of the Day

Start a free 7-day pilot, change one router setting and ZDNS starts watching your floor in shadow mode straight away. R50 per seat per month, from 25 seats. Prefer your IT provider to manage it? They can sign up as a ZDNS partner.