DNC scrubbing is the process of removing phone numbers that appear on the National Do Not Call Registry — plus any applicable state DNC lists and your own internal do-not-call list — from your dial lists before your dialer touches them. The National Registry is operated by the FTC, and under the Telemarketing Sales Rule, sellers and telemarketers must scrub against an updated version of the registry at least every 31 days. A list that was clean on the first of the month is legally stale by the second.
Most pages that rank for “dnc scrubbing” define the term and stop. This post covers what the definitions skip: the operational pipeline — what gets scrubbed, against what, how often, and what evidence you keep. SIPNEX is an FCC-licensed carrier serving call center operations and predictive dialer fleets. We do not scrub your lists — that is campaign-level work — but when operators get burned, the failure is almost always in the pipeline, not the intent.
The suppression sets: what you scrub against
A real DNC scrub runs against at least three suppression sets, and treating them as one list is the first mistake.
The National Do Not Call Registry. Operated by the FTC. Access is sold by area code on an annual subscription: for fiscal year 2026, the first five area codes are free, each additional runs $82 per year, capped at $22,626 nationwide. If you dial nationally, budget for the cap — an unsubscribed area code is one you are dialing blind. The FTC’s Q&A for telemarketers on the DNC provisions of the TSR is the primary source.
State DNC lists. Several states — Indiana, Pennsylvania, and Colorado among them — maintain their own registries with separate fees, update schedules, and exemption rules. A number can be absent from the National Registry and present on a state list. If you dial into those states, you scrub against both.
Your internal DNC list. Every consumer who tells you to stop calling — by any reasonable means — goes on your company-specific suppression list, and that entry overrides everything else, including any exemption you think you hold. No registry maintains this list for you. It must update in real time: when an agent hears “take me off your list,” the number gets flagged during the call, not batched at end of shift.
Some operations add a fourth set — known-litigator suppression files. Optional, but cheap insurance.
The DNC scrubbing pipeline, step by step
1. Normalize before you match. Every number in the lead file and every suppression entry gets normalized to a single format — ten digits, or full E.164 — before comparison. Mismatched formatting is the silent killer of DNC scrubs: a lead stored as “(214) 555-0134” sails past a suppression entry stored as “2145550134” under naive string comparison.
2. Scrub at load, not just at purchase. Lead vendors love to sell “pre-scrubbed” data. Treat that as marketing. The scrub that matters legally is yours, timestamped, against registry data current within 31 days of the dial date — regardless of what the vendor certified.
3. Re-scrub on the 31-day clock. The registry adds numbers continuously, so a list scrubbed 32 days ago contains numbers that were callable then and are violations now. Tag every list with its last-scrub timestamp and block the dialer from loading anything older than your cadence. Disciplined operations run the cycle every 24 to 48 hours rather than riding the 31-day limit.
4. Apply internal DNC continuously. Federal and state scrubs are batch processes. Your internal DNC list is not — it must suppress in real time across every campaign, not just the one that generated the request. A number blocked in only one campaign is a gap a plaintiff’s attorney will find.
5. Suppress, never delete. Scrubbed numbers get flagged and excluded, not removed. You need the record — which number was suppressed, by which suppression set, on which date, against which registry version. Deleting the row destroys your own evidence.
6. Keep the audit trail. The TSR’s safe harbor for inadvertent violations requires written DNC procedures, employee training, an internal suppression list, and records proving you accessed the registry at least every 31 days. Translation: retain scrub logs, registry access receipts, and list version history. Without that paper, the safe harbor is unavailable no matter how good the actual process was.
Choosing a DNC scrubber
The criteria are the same whether you buy a service or build in-house. We sell trunks, not scrubbers, so take this as a category-level checklist, not a vendor ranking.
Coverage. Federal registry, applicable state registries, and your internal suppression list in one pass. A scrubber that only handles the National Registry solves a third of the problem.
Data freshness. The legal maximum is 31 days; a good scrubber works from registry data that is days old, not weeks.
API versus batch. Batch scrubbing fits the list-load workflow. A real-time API lets you check numbers at dial time or lead capture — useful for inbound-generated leads sitting in a callback queue. High-volume operations want both: batch for hygiene, API for the edge cases.
Match logic. Confirm the scrubber normalizes formats before matching on the full ten-digit number, and ask what happens with malformed records — an unparseable number should be rejected, not silently passed to the dialer.
Audit output. Every job should produce a record: input count, suppressed count by source, registry data version, timestamp. That output is your safe-harbor evidence. A scrubber that returns a clean file with no log is a liability dressed up as a service.
Dialer integration. The scrub is worthless if the suppressed file and the dialed file can drift apart. The tighter the integration with your dialer’s lead loader, the smaller the window for loading the wrong file.
Where scrubbing sits in the compliance stack
DNC scrubbing is one layer of the stack. The TCPA compliance checklist covers the consent framework, calling-hour rules, and abandon-rate limits that sit alongside DNC obligations. The auto dialer laws guide covers the ATDS question that determines which consent standard applies to your dialer. If you record calls for compliance documentation, state recording consent laws add another layer. The full federal-state-carrier map lives in our call center compliance guide.
Your carrier owns a different layer: attestation, call signing, and CDRs. SIPNEX signs traffic with our own STIR/SHAKEN certificate at A-level attestation and provides real-time CDRs — the call-side half of your evidence chain. The scrub logs are the other half, and those are yours.
Scrubbing is necessary, not sufficient
An honest note the scrubbing industry rarely volunteers: a perfect DNC scrub does not make a campaign legal. Consent still governs. If you are dialing cell phones for telemarketing with an autodialer or prerecorded voice, you need prior express written consent — a number can be absent from every DNC list on earth while you still lack consent to call it. TCPA liability accrues per call, which is why consent defects, not DNC misses, drive most large class actions.
The exemption categories cut the other way too. An established business relationship — generally up to 18 months after a transaction or 3 months after an inquiry — can permit calls to a registry-listed number, and documented express consent can as well. But both exemptions collapse the moment the consumer makes a company-specific do-not-call request, and their scope varies by state. Map your exemption logic with your counsel before encoding it in the pipeline, not after a demand letter arrives.
Scrub every list, every cycle, with logs to prove it — and treat that as the floor of the program, not the program.
Frequently asked questions
What is DNC scrubbing?
DNC scrubbing is comparing your outbound dial lists against do-not-call suppression sets — the FTC’s National Do Not Call Registry, applicable state DNC lists, and your internal do-not-call list — and flagging every match so your dialer never calls it. A proper scrub normalizes formats before matching, suppresses rather than deletes, and produces a timestamped log showing what was scrubbed, against which registry version, and when.
How often do you have to scrub against the Do Not Call Registry?
At least every 31 days. The FTC’s Telemarketing Sales Rule requires sellers and telemarketers to scrub against an updated version of the National Registry on that cycle, and proof of 31-day access is a condition of the rule’s safe harbor. Disciplined operations scrub far more often — every 24 to 48 hours — since fresh registry data costs nothing beyond the subscription.
Do I need to scrub if my customers opted in?
Yes — run the scrub anyway. Express consent and established business relationships are recognized exemption categories for registry-listed numbers, but they are conditional: consent must be provable and current, EBR windows expire, and a company-specific do-not-call request overrides both. Scrubbing also enforces your internal DNC list, which no opt-in excuses. Suppress by default, and dial exempted numbers only where your counsel confirms the exemption applies to your traffic.
What happens if you call a number on the DNC list?
Each call is a separate violation, and exposure stacks: FTC enforcement under the Telemarketing Sales Rule, FCC rules, private TCPA lawsuits with per-call statutory damages, and state enforcement where state lists apply. The TSR’s safe harbor can protect a genuinely inadvertent miss, but only with documented procedures, training, an internal suppression list, and 31-day registry access. Our TCPA compliance checklist covers the damages framework in detail.
Does my carrier scrub my lists for me?
No, and be suspicious of any carrier that claims otherwise. Scrubbing is campaign-level work tied to your leads, consent records, and internal DNC list — data your carrier never sees. The carrier owns the infrastructure layer: call signing, attestation, and the CDRs documenting your dialing activity. SIPNEX provides A-level STIR/SHAKEN attestation and real-time CDR access; the scrub logs that pair with those records come from your side of the stack.
DNC scrubbing is one layer of the program mapped in our call center compliance guide. SIPNEX provides the carrier layer underneath it: A-level attestation, real-time CDRs, unlimited channels, and published rates for call center operations. Talk to an operator — (833) 665-2220.
Keep reading.
The carrier built by operators, for operators.
FCC-licensed carrier with its own STIR/SHAKEN SP certificate. Operator-owned. SIP trunks built for operators who dial at volume.