DNC List Scrubbing 101: What to Check and How Often

DNC list scrubbing is the process of checking every number on an outbound calling list against Do Not Call suppression sources — the National DNC Registry, applicable state registries, and a company’s own internal do-not-call list — and removing any match before dialing. Federal rules require the National Registry check at least every 31 days, though many compliance teams scrub more often than the legal minimum.

That 31-day figure sounds simple until you look at the volume behind it. The National Do Not Call Registry added roughly 4.8 million new numbers in the last fiscal year alone, and the FTC received 2.6 million Do Not Call complaints in fiscal year 2025. A list scrubbed 30 days ago on a 100,000-number weekly campaign can already contain hundreds of numbers that became DNC-protected since the last scrub. This post breaks down exactly which lists to check, how often each one needs refreshing, and what documentation actually protects you if a complaint or audit happens — not just the legal penalties, which are covered in more depth in TCPA Fines in 2026: Real Cases and What They Cost. For the compliance tooling referenced throughout this post, see Belsmart’s outbound compliance tooling.

What Is DNC List Scrubbing?

DNC list scrubbing means comparing your outbound dial list against every applicable do-not-call suppression source, flagging matches, and suppressing — not deleting — those numbers so your dialer never calls them. A proper scrub normalizes phone number formats before matching, since a mismatch in formatting (extra digits, missing area code) can cause a suppressed number to slip through undetected.

The output of a real scrub isn’t just a cleaned list. It’s also a timestamped log showing what was checked, against which registry version, and when. That log is what separates “we probably scrubbed” from documented proof, which matters enormously if a complaint ever turns into a Telephone Consumer Protection Act (TCPA) claim.

What Lists Actually Get Scrubbed?

Most teams think of “the DNC list” as a single database. In practice, a complete scrub checks at least three separate suppression sources, and treating them as interchangeable is a common compliance gap.

How Often Do You Have to Scrub Against the DNC List?

At least every 31 days — that’s the maximum allowable gap under the FTC’s Telemarketing Sales Rule (16 CFR Part 310) and the FCC’s parallel rule at 47 CFR 64.1200(c). The 31-day window isn’t a suggested best practice; it’s a hard ceiling, and proof of scrubbing within that window is a condition of the rule’s safe harbor protection.

However, the legal minimum and a safe operational cadence aren’t the same thing. Because the Registry adds millions of numbers annually, many compliance teams scrub before every campaign launch or check in real time at the point of dial, rather than waiting for the 31-day deadline to approach. A list that’s technically compliant on day 30 is still calling numbers that became DNC-protected on day 29.

Takeaway: 31 days is the legal floor, not a target — teams running high-volume outbound should treat it as the outer boundary of an otherwise tighter cadence.

What’s the Difference Between the Federal DNC List and an Internal DNC List?

The National DNC Registry has exemptions; your internal DNC list does not. Numbers on the federal registry can still legally be called under the Established Business Relationship (EBR) exemption — generally, a purchase within the past 18 months or an inquiry within the past 3 months. An internal do-not-call request has no such exemption: once a consumer tells your company specifically to stop calling, that request applies regardless of any existing relationship, and it doesn’t expire.

This distinction matters because it’s a common source of accidental violations. A sales team might correctly confirm a lead is EBR-exempt from the federal registry, dial them anyway, and still violate the law if that same person had previously asked your company directly to stop calling. The internal list overrides the exemption every time.

What About Litigator Lists and Professional Plaintiffs?

A litigator list flags phone numbers associated with people who file TCPA lawsuits repeatedly, often registering numbers specifically to generate claims. Recent analysis of TCPA filings found that roughly 31% to 41% of 2024 lawsuits came from plaintiffs who had filed previous TCPA suits — a small, professionalized group responsible for a disproportionate share of litigation risk.

Scrubbing against a litigator list isn’t a federal requirement the way the National Registry check is. It’s a risk-management layer most high-volume outbound operations add voluntarily, because a single call to a known litigator’s number can trigger a lawsuit regardless of whether every other part of the campaign was compliant.

What Evidence Do You Need to Keep to Prove Compliance?

You need a timestamped log proving when each scrub happened, which registry version it ran against, and what was suppressed as a result — this is the core of the TSR’s safe harbor defense. Under 16 CFR 310.5, telemarketers must generally retain certain telemarketing records for 24 months, though a 2024 FTC rule amendment specifically extended retention for DNC-related and consent records to five years. Given that update, most compliance teams now treat five years as the safer standard for anything DNC- or consent-related, rather than relying on the older two-year figure.

At minimum, your evidence trail should include:

• Proof of National DNC Registry access for every area code you called, with the date of each access.
• Your internal DNC list, including the date and source of every opt-out request.
• A record of which state registries were checked and when, for every state you dial into.
• Written internal procedures for scrubbing, plus evidence that staff were trained on them — both required components of the safe harbor defense.
• Logs showing suppression results per campaign, not just a single “list was scrubbed” note.

Missing records isn’t a minor paperwork issue. Under the TSR’s recordkeeping rule, failing to produce records the FTC requests during an investigation can itself be treated as a separate violation, and the FTC has stated it may infer that missing records would have shown noncompliance.

A Scrub-Cadence Framework You Can Actually Follow

Use this sequence as an operational baseline, then adjust frequency upward based on your call volume:

1. Check internal DNC and litigator lists in real time, at the point of dial. This is the fastest-changing suppression source and the easiest to enforce continuously rather than in batches.
2. Refresh the National DNC Registry file weekly for every active area code, even though the legal requirement is 31 days — this narrows the gap between when a number registers and when your list catches it.
3. Run a full National Registry re-scrub at least every 31 days, timestamped and logged, as the non-negotiable compliance floor.
4. Reconcile state DNC lists quarterly, or more often in states with stricter or faster-changing rules.
5. Update the internal list immediately whenever an opt-out request comes in — the TCPA’s 10-business-day honor window is the outer limit, not the target.
6. Export and archive scrub logs on a fixed schedule (weekly or monthly) to a separate, durable location, so a single system failure doesn’t erase your evidence trail.

How AI-Handled Calls Fit Into This

Calls placed by an AI voice agent still have to pass the same DNC scrub as calls dialed by a live rep — the suppression requirement applies to the number being called, not to who or what places the call. As outbound teams add AI voice agents to handle initial outreach and qualification, the scrub step needs to sit upstream of both the AI system and any human dialer pulling from the same list, not duplicated separately for each.

How Scrub Results Should Flow Into Your CRM

Suppression results are only useful operationally if they’re visible where reps and campaign managers actually work. Syncing scrub outcomes into your CRM record — flagging a contact as suppressed, and why — prevents a rep from manually re-adding a number to a list next month without realizing it was scrubbed for cause. It also keeps your evidence trail centralized instead of scattered across spreadsheets. For teams also managing dialer pacing and abandoned-call risk alongside DNC compliance, Dialer Ratios Explained covers the related — but distinct — compliance lever of call pacing.

Takeaway: DNC list scrubbing isn’t one check — it’s a stack of federal, state, internal, and risk-mitigation lists, each with its own cadence, and the evidence you keep matters as much as the scrub itself.

Frequently Asked Questions