DNC registry tool: what it does, what it costs, and how to choose one

Last updated 2026-07-09

What is a DNC registry tool and what does it actually do?

A DNC registry tool compares the numbers you plan to call against one or more Do Not Call databases, then flags or strips the ones that show up. The output is a "scrubbed" list. The numbers left standing are, as far as the registry is concerned, safe to dial for covered telemarketing. It can be software, an API, or a plain web portal.

The main database it checks is the FTC's National Do Not Call Registry, where consumers sign up at donotcall.gov ^[1]. That registry holds more than 249 million phone numbers as of recent FTC reporting ^[2]. Better tools go past the federal list. They check state DNC registries (Florida, Indiana, and Pennsylvania each run their own, with rules that go beyond federal law), your internal suppression list built from opt-outs, and sometimes wireless-only lookup databases.

Here is what it does not do. It does not make you compliant on its own. The registry check is one layer. You still have to handle prior express written consent under the TCPA, honor company-specific do-not-call requests within 30 days, and train your team on the exemptions. A tool clears the obvious violations. The rest of the work is yours.

Read our explainer on the dnc registry for how the federal database is structured before you pick a tool to access it.

Who is legally required to use the National DNC Registry?

If you make telephone solicitations to residential numbers in interstate commerce, you are covered by the Telemarketing Sales Rule (TSR) and the TCPA ^[3]. Run an outbound team calling consumers at home, and you have to check the registry before each campaign. There is no small-business carve-out that lets you skip it.

The timing is specific. Telemarketers must access registry data no more than 31 days before making a call ^[4]. Let your list age past 31 days since the last fresh pull, and you are out of compliance, even if the scrub was perfectly accurate the day you ran it. This one trips up small teams constantly. They scrub once, then keep dialing that same list for months.

Exemptions exist. They are narrow. Calls under an existing business relationship (EBR) are partially exempt, but the federal EBR window is 18 months after a transaction or 3 months after an inquiry. Political calls, charitable solicitations, and pure survey calls with no sales pitch are also exempt from the registry rule, though the TCPA's autodialer and pre-recorded call restrictions can still catch them.

B2B calls to business numbers generally sit outside the National DNC Registry, because the registry protects residential subscribers ^[5]. But some states treat certain B2B calls differently, and your own internal DNC list has to cover anyone who asked not to be called, business or not.

How much does access to the DNC registry cost?

The FTC sets the subscription fees for commercial access and updates them every year ^[6]. For fiscal year 2025, here is the structure:

Access tier	Annual fee (FY2025)
First 5 area codes	Free
Each additional area code	$75
All area codes (unlimited national)	$18,044

A small team calling one metro often stays under five area codes and pays the FTC nothing. A regional team buying 15 to 20 area codes pays roughly $825 to $1,125 a year. A national dialer pays the flat $18,044.

Third-party scrubbing vendors charge on top of that. They run their own infrastructure and usually bundle state lists, wireless lookup, and litigator databases. Pricing swings a lot. Some charge per record (a common range is $0.001 to $0.01 per number scrubbed), others charge a monthly platform fee from a few hundred to several thousand dollars depending on volume. Per-record wins for small sporadic campaigns. Flat-rate usually wins above a few hundred thousand dials a month.

Want to check a small list yourself without a vendor? The FTC's registry portal lets organizations access the data directly after you create an account and pay the applicable fee. Our FTC Do Not Call list page walks through that process.

What features should a good DNC registry tool have?

The one feature you cannot skip is accurate, current registry data with a clear timestamp showing when the underlying list last synced with the FTC. If a vendor cannot tell you exactly when their data was pulled, walk away. The 31-day rule means stale data puts you at risk even while the tool hums along looking fine.

Past that baseline, here is what matters.

State DNC coverage. Federal data alone leaves you exposed in states like Florida (the Florida Do Not Call Program), Indiana, and Pennsylvania, all of which run stricter lists. See our Florida Do Not Call list and Indiana Do Not Call list articles if you dial into those states.

Internal suppression management. Every outbound team piles up numbers from people who called in and said stop. The TCPA makes you honor those within 30 days and keep them for at least 5 years ^[3]. Good tools let you upload and manage that internal list next to the registry data, so a single scrub catches both.

Litigator scrub. This is a separate, privately built database of numbers tied to serial TCPA plaintiffs. It is not a legal defense, and appearing on one does not make calling someone illegal. But a single TCPA suit can cost $500 to $1,500 per call in statutory damages, and class actions climb into seven or eight figures, so plenty of teams treat this as cheap insurance.

Audit trail and reporting. Face an FCC or FTC inquiry and you will need documented proof you scrubbed each campaign against data no more than 31 days old. Tools that log scrub timestamps and export compliance reports earn their price. Without that paper trail, "we scrubbed it" is just a sentence.

API access. This matters for teams running automated workflows. A REST API lets your dialer or CRM fire a scrub the moment a new lead lands, before it ever reaches an agent. Cleaner than a weekly batch job by a mile.

LeadCompliant's free number checker handles individual lookups fast, no vendor contract required. For ongoing campaign scrubbing at volume, you will want batch processing and a real subscription to the FTC data.

What is the penalty for calling a number on the DNC registry?

The TCPA (47 U.S.C. 227) gives consumers a private right of action: $500 per violation, or up to $1,500 per willful violation ^[7]. The statute states a person may bring "an action to recover for actual monetary loss from such a violation, or to receive up to $500 in damages for each such violation, whichever is greater." No proof of actual harm required.

The FTC and FCC both hold enforcement power on top of private suits. FTC civil penalties for TSR violations currently run up to $51,744 per violation per day. That figure is inflation-adjusted under the Federal Civil Penalties Inflation Adjustment Act and moves periodically, so confirm the current number at ftc.gov ^[8].

The math turns ugly fast. A campaign that dials 5,000 registered numbers without consent carries $2.5 million in TCPA exposure at $500 a call, or $7.5 million at the trebled willful rate. Class action lawyers actively recruit plaintiffs from big lists, which is why even a low error rate on a high-volume dialer is a real financial threat.

Our Do Not Call list report article shows how consumers file complaints and how that data reaches enforcement agencies.

How does the 31-day scrub rule work in practice?

The TSR requires that a seller or telemarketer access registry data no more than 31 days before making a covered call ^[4]. Scrub on January 1, call on February 1, and you are 31 days out and still covered. Call on February 3 and you are not. That is the whole rule in two sentences.

The practical read: for any ongoing campaign, re-scrub your active list at least every 30 days. Most compliance teams run weekly scrubs to keep a buffer. Some platforms scrub at the point of dial, which is the cleanest setup but needs API access to the registry or a vendor with real-time data.

New numbers hit the federal list continuously. The FTC processes additions on a rolling basis, but the effective date for telemarketing purposes is that 31-day window. So a number added today is protected from covered calls after 31 days. Most vendors refresh their copy of the registry monthly or more often.

Here is the mistake I see most. A team scrubs before a campaign launches, then keeps dialing the same list for weeks or months. The clock runs from the date you pulled the data, not the date the campaign kicked off.

Does a DNC registry tool cover cell phones too?

Yes and no. Cell numbers can be registered on the National Do Not Call Registry, and registration covers landlines and cell phones alike ^[9]. So if a consumer put their cell on the federal registry, a proper tool flags it.

But the TCPA's cell phone rules reach further than the registry. Under 47 U.S.C. 227(b), using an automatic telephone dialing system (ATDS) or a pre-recorded voice to call a cell without prior express consent is barred, whether or not the number sits on the DNC registry. The consent requirement for cells is separate from and stacked on top of the registry rule.

So a cell number that is NOT on the DNC registry can still be off-limits if you use an autodialer and lack consent. A DNC tool does nothing for you there. You need a separate consent process for mobile numbers.

Some vendors offer a wireless identification lookup that tells you whether a number is mobile or landline. Handy for deciding which rules apply. But that is a different job from DNC scrubbing. Our mobile phone Do Not Call list article covers this intersection.

What are the differences between federal and state DNC tools?

The National Do Not Call Registry covers residential numbers and is run by the FTC ^[1]. Check it and you satisfy federal requirements. But about a dozen states keep their own registries, often stricter, and federal registration does not automatically enroll anyone in a state list (though some states cross-reference federal data).

Here is a quick comparison:

Feature	Federal (FTC/FCC)	State (varies)
Who administers	FTC / FCC	State AG or consumer agency
Numbers covered	Residential (landline + cell)	Varies; some states include cell-only lists
Cost to access	Free (5 area codes) / up to $18,044/yr	Varies; some free, some nominal fee
Exemptions	EBR, political, charity	Vary by state; some narrower
Penalty per violation	$500-$1,500 (private) / up to $51,744 (FTC)	Can exceed federal; FL up to $10,000/call

Florida runs a state DNC law through the Florida Department of Agriculture and Consumer Services, with penalties up to $10,000 per violation for willful violations ^[10]. Indiana's list runs through the Indiana Attorney General. Pennsylvania has its own program too. See our articles on the Florida Do Not Call list, Indiana Do Not Call list, and Do Not Call list PA.

Call consumers in multiple states and you need either a vendor that bundles state lists or a multi-step scrub that hits each relevant state registry on its own. Missing a state list is one of the most common gaps in small outbound shops.

How do you actually use a DNC scrubbing tool in your workflow?

Four steps: acquire the data, format your list, run the scrub, document the results. That is the spine of it.

First, confirm you hold a current subscription to the FTC registry for the area codes you need, or that your vendor does and can prove their data sits inside the 31-day window. Do not skip this. A vendor's word is not documentation.

Second, prepare your list in the format the tool wants. Most take CSV files with columns for phone number, name, and optionally state. Normalize the numbers first (10-digit NANP, no special characters) or your match rate suffers.

Third, run the scrub. The tool hands back either a cleaned list with flagged numbers pulled, or a report showing which numbers matched. Some append a match reason (federal DNC, state DNC, internal suppression, litigator list). Read that output before you dial anything.

Fourth, save the scrub report with a timestamp. Store it where your compliance team can find it during a complaint or lawsuit. The TSR safe harbor (16 CFR Part 310) protects you if you can show you accessed the registry correctly and inside the required window ^[4].

Buying leads from a third party? Build the scrub into intake, not the pre-call step. Scrub at intake and you never build a pipeline around a number that is already off-limits.

The tools listed at how do I get the Do Not Call list help you understand the access process before you commit to a vendor.

What is a litigator scrub and should you bother?

A litigator scrub checks your list against privately built databases of numbers tied to people who have filed or threatened TCPA suits. Compliance vendors build and sell these, not the government. They are not a legal safe harbor.

Be honest about the value. Calling a number on a litigator database is not inherently illegal, and a plaintiff cannot win a TCPA case just because you dialed them, provided you had the right consent or a valid exemption. The scrub does not change your legal exposure. It changes your risk exposure by steering you away from people who are likely to sue.

For high-volume dialers running millions of calls a month, the cost (usually bundled into vendor pricing or a few hundred dollars a month as an add-on) is probably worth it. For a small team making a few hundred calls a week, the payoff shrinks. Spend that money on solid consent documentation instead.

Where it genuinely earns its keep is lead acquisition. Buying lists from vendors? Run a litigator scrub on incoming leads before you ever dial them. That filters high-litigation-risk numbers before you sink sales time into them.

How do free DNC tools compare to paid ones?

Free tools usually give you one of two things: single-number lookups, or a tiny batch scrub (sometimes capped at a few hundred records). The FTC's own registry portal is technically free for the first five area codes, but it needs an account and its interface is built for compliance verification, not campaign work.

Paid tools add batch processing at scale, API access, state list integration, audit reporting, and a UI built for marketing operations rather than compliance specialists. They usually handle the FTC subscription for you, baked into the price.

Here is my rule of thumb. Under 5,000 calls a month, a free or low-cost tool plus a direct FTC subscription is often plenty. Above that, the overhead of managing the FTC subscription yourself, formatting lists for the raw registry interface, and storing results by hand costs more in staff time than a mid-tier vendor charges.

LeadCompliant offers free number lookup for spot-checking individual numbers during compliance review. For ongoing campaign scrubbing, the compliance kit includes a workflow guide for setting up batch scrubbing with a registry vendor.

Our Do Not Call list number article covers how consumers register numbers, useful background for understanding what lands on the registry your tool checks.

What records do you need to keep after scrubbing?

The TSR requires sellers and telemarketers to keep records sufficient to demonstrate compliance, and the FTC has stated in enforcement actions that contemporaneous documentation is expected ^[4]. For each campaign, keep at least this.

The date the scrub ran. The vendor or registry version used. The count of records submitted and the count flagged. The cleaned list you actually dialed. And the date range the campaign ran.

Some FTC enforcement actions have cited failure to document that the seller accessed the registry inside the required window. "We used a scrubbing service" is not a defense without records showing when and against what data version.

Retention is the tricky part. The TSR does not set a minimum period for DNC scrub records specifically, but general recordkeeping under 16 CFR 310.5 calls for 24 months on most telemarketing records ^[12]. The TCPA carries a 4-year statute of limitations for private suits, so keeping scrub records for at least 4 years is the safer play ^[7].

Store these somewhere other than your CRM's call log. Those get purged on shorter cycles. A cloud folder organized by campaign name and date is fine. What matters is that it exists and you can produce it on demand.

Frequently asked questions

What is the difference between the DNC registry and a DNC list?

The National Do Not Call Registry is the federal database the FTC maintains, where consumers register their numbers. A DNC list is a generic term that can mean that federal registry, a state registry, or your company's internal suppression list of people who asked not to be called. A DNC registry tool checks your call list against one or more of these databases before you dial.

How often do I have to re-scrub my call list against the DNC registry?

At least every 31 days. The TSR requires you to access the registry no more than 31 days before making a covered call. Most compliance teams scrub weekly to stay well inside that window. Fresh registry data matters most if you work from lead lists that arrive on a rolling basis, since new numbers register on the DNC list continuously.

Does the DNC registry tool also handle the company-specific do-not-call list?

Some do, some do not. The TCPA requires every telemarketer to maintain its own internal do-not-call list of consumers who asked not to be called by that company. Good tools let you upload and manage this internal list alongside the federal and state registry data, so one scrub catches everything. If your tool only checks the federal registry, you need a separate process for your internal list.

Can I use a DNC registry tool for text message campaigns?

Partially. The registry was built for voice calls to residential numbers, but the FCC and many courts have held that SMS marketing falls under the TCPA's express consent rules too. A DNC scrub is still worth running before a text campaign to flag registered numbers, but it does not replace the consent requirement for texts. You need prior express written consent to send marketing texts, registry or not.

What happens if I call someone on the DNC list by mistake?

If it was a genuine mistake and you have documentation showing you scrubbed within 31 days using accurate registry data, the TSR safe harbor may protect you from FTC civil penalties. It does not erase TCPA lawsuit risk: the $500 per-call statutory damages under 47 U.S.C. 227 can still be pursued by the consumer. A single mistake on a documented scrub is far easier to defend than a systemic gap.

Are there DNC registry tools that check all state lists too?

Yes, some vendors bundle federal and state DNC data into one scrub. States with active separate registries include Florida, Indiana, Pennsylvania, Texas, Colorado, and several others. Coverage varies by vendor, so ask exactly which states are included before buying. If you dial into states with strict DNC laws, confirm the vendor updates state data on the same frequency as federal data.

How do I access the National DNC Registry directly from the FTC?

Create an account at the FTC's registry access portal (telemarketing.donotcall.gov). You get up to five area codes at no charge. Additional area codes cost $75 each, and full unlimited national access costs $18,044 per year (FY2025 pricing). The portal provides downloadable data files you load into your calling system, or you can use a third-party vendor who manages the subscription and gives you a cleaner batch interface.

What is the safe harbor for DNC registry compliance?

The TSR safe harbor, at 16 CFR Part 310, protects sellers from FTC civil penalties if they can show they accessed the registry within 31 days before the call, relied on the data in good faith, and had written procedures and training in place for DNC compliance. It does not protect against private TCPA suits, and it requires contemporaneous documentation, more than a claim that you ran a scrub.

Do I still need to scrub if I'm only calling existing customers?

Maybe not for existing customers inside the established business relationship (EBR) window: 18 months after a transaction or 3 months after an inquiry, under federal rules. But if that customer asked not to be called, the EBR exemption vanishes and your internal DNC list controls. Many teams scrub everyone anyway, because the EBR window is easy to miscalculate and a mistake is expensive.

What should I look for in a DNC vendor contract?

Look for a stated data refresh frequency (ideally monthly or more often), clear documentation of which registries are included (federal and which states), an audit log or exportable scrub report with timestamps, indemnification language, and what happens when the vendor's data is wrong. Ask whether the contract gives you the documentation you need to show safe harbor compliance during an FTC inquiry. Vendors who cannot answer clearly are not worth the risk.

Is there a free DNC registry tool I can use right now?

The FTC's registry portal is free for the first five area codes after account setup. Several compliance vendors offer free single-number lookups to demo their platform. These handle spot-checks or small lists fine. For batch scrubbing of a campaign list, even a modest one, you need a paid vendor or a direct FTC subscription plus a process for handling the data files they provide.

How does a DNC registry tool interact with my CRM or dialer?

Many tools offer a REST API that connects to CRMs like Salesforce or HubSpot, or dialers like Five9 or NICE. When a new lead enters the CRM, the API call fires, the number gets checked against the registry, and a field is populated with the result. This catches new leads at intake, cleaner than batch scrubbing. You still need periodic re-scrubs for numbers already in your pipeline as the 31-day clock advances.

Can a consumer sue me personally for calling their DNC-registered number?

Yes. The TCPA's private right of action under 47 U.S.C. 227 lets individual consumers sue in state court for $500 per violation or up to $1,500 for willful violations, without showing actual damages. Courts have held that individuals, including company officers, can be named personally in some circumstances. Class action suits aggregating thousands of such claims are common and drive most large TCPA settlements.

Sources

1. FTC, National Do Not Call Registry: Consumers register their phone numbers on the National Do Not Call Registry at donotcall.gov, which covers residential landlines and cell phones.
2. FTC, Do Not Call Registry Data Book: The National Do Not Call Registry holds more than 249 million registered phone numbers as of recent FTC reporting.
3. 47 U.S.C. 227, Telephone Consumer Protection Act: The TCPA requires telemarketers to honor do-not-call requests within 30 days and maintain internal DNC lists for at least 5 years; consumers may sue for $500 to $1,500 per violation.
4. FTC, Telemarketing Sales Rule 16 CFR Part 310: The TSR requires sellers and telemarketers to access the National DNC Registry no more than 31 days before making a covered call, and provides a safe harbor for documented good-faith compliance.
5. FTC, Complying with the Telemarketing Sales Rule: The National Do Not Call Registry covers residential subscribers; B2B calls to business numbers are generally not covered by the federal registry requirement.
6. FTC, National Do Not Call Registry Fees: The FTC sets and annually updates commercial subscription fees for access to the National Do Not Call Registry.
7. 47 U.S.C. 227(c)(5), TCPA private right of action: The TCPA statute states a person may bring an action to receive up to $500 in damages for each violation, or up to $1,500 for willful violations; the TCPA has a 4-year statute of limitations.
8. FTC, Civil Penalty Inflation Adjustments: FTC civil penalties for TSR violations are inflation-adjusted under the Federal Civil Penalties Inflation Adjustment Act and currently reach up to $51,744 per violation.
9. FTC, National Do Not Call Registry FAQs: Cellular numbers can be registered on the National Do Not Call Registry, and registration covers both landlines and cell phones.
10. Florida Department of Agriculture and Consumer Services, Florida Do Not Call Program: Florida's state DNC law carries penalties up to $10,000 per violation for willful violations, administered by the Florida Department of Agriculture and Consumer Services.
11. FTC, Telemarketing Sales Rule Recordkeeping Requirements, 16 CFR 310.5: TSR recordkeeping requirements under 16 CFR 310.5 specify 24 months retention for most telemarketing records.