Here's a thing that trips up almost every team that texts cold lists: they scrub against the federal Do-Not-Call registry, mark the compliance box, and assume they're covered. Then they get a demand letter anyway. The scrub wasn't wrong — it was just measuring the wrong thing for a texting operation. A big chunk of the federal DNC registry is landlines, and you can't legally text a landline in the first place. So a lot of what you "scrubbed" was numbers you were never going to message.
Full disclosure: I work for Ready, and we sell a standalone litigator + DNC scrub at $0.005 per contact. That gives me a bias, but it also means I've watched a lot of lists get scrubbed and seen exactly where the federal registry alone leaves gaps. This post is about those gaps.
What the federal DNC registry actually does
The National Do Not Call Registry, run by the FTC, is a list of numbers whose owners have said "no telemarketing calls." That's the whole job. It's a consumer-opt-out list for sales calls.
A few things worth being precise about:
- It's telemarketing-scoped. It doesn't cover transactional or informational messages, and it doesn't cover contacts you have an established business relationship or prior express consent with.
- It's a mix of landlines and wireless numbers. People register both. There's no "wireless-only" view of it.
- It says nothing about whether a number has been reassigned to a different person since it was registered.
- It says nothing about whether the person behind the number is a known TCPA litigator — that's a separate database entirely (more on that below).
So the federal DNC is real and you should scrub against it. It's just narrow. For a texter, it answers one question — "did this person opt out of telemarketing calls?" — and leaves three or four other important questions unanswered.
Why landline coverage is nearly wasted on texters
You legally can't send SMS to a landline. It's not a delivery problem — it's a consent-and-line-type problem. Cold-texting a landline is both technically pointless and a compliance flag.
Which means a good portion of the DNC hits on your cold list are numbers you'd never have messaged anyway. That's fine — but it's also why "we scrubbed against DNC" gives false comfort. The scrub caught landline opt-outs. It didn't answer the questions that actually determine whether you get sued for a text.
The step that matters more, and that most teams skip, is a line-type scrub — splitting wireless from landline before you even get to DNC. I wrote more on that here: the line-type scrub that comes before DNC. For texters, that's the first pass, not the last.
The reassigned-number problem
This one costs people real money. When a phone number gets disconnected and reassigned, the new owner never gave you consent — but your records still say they did. You text them, they never opted in, and now you've messaged someone with no consent.
Rough industry framing: a list that's about 12 months old can be ~30% reassigned or disconnected by the time you use it. That's not a precise stat — it varies wildly by source — but it's the right order of magnitude, and it's enough that "we had consent when we collected it" stops being a defense.
The FCC maintains a Reassigned Numbers Database precisely because this is a known liability path. For a texter, the practical version is: scrub for line-type and reassignment before you re-engage an aging list, not after. The order matters for spend — you don't want to pay to message numbers that changed hands. There's a full breakdown of the sequencing in the scrub-then-reengage order that saves spend.
State DNC lists exist too
A handful of states run their own do-not-call registries with rules that can be stricter than federal — different scope, different time windows, sometimes covering message types the federal list doesn't. Florida's is the one that gets the most attention because its state statute has been aggressively litigated, but it's not the only one.
You don't need to memorize all of them. What you need is a scrub source that checks the ones that matter for where your contacts live, and a reminder that "federal DNC clean" and "state DNC clean" are not the same statement.
The list the DNC never touches: known litigators
This is the gap that turns into lawsuits. A number can be perfectly clean on the DNC — never registered, no opt-out — and still belong to someone who has sued companies over unsolicited texts before. TCPA litigators are a small, identifiable group of people who file these cases repeatedly, and they're tracked on litigator databases that are completely separate from the DNC.
A litigator flag doesn't mean "this number is on a do-not-call list." It means "this specific person has a history of suing over texts." If you want the distinction spelled out, a number can pass DNC and still sue you covers it directly. The short version: DNC and litigator lists are different questions, and scrubbing one does nothing for the other.
This matters because of the exposure math. A single TCPA violation runs $500–$1,500 per text. One litigator on a 20,000-contact blast, receiving one message, is a $500-plus problem before legal fees. Suppressing that number ahead of the send costs a fraction of a cent.
The scrub-layering guide (in order)
Here's how I'd sequence it for any outbound texter working a cold or aged list. Each layer answers a question the previous one doesn't:
| Layer | Question it answers | Why federal DNC alone misses it |
|---|---|---|
| 1. Line-type | Is this even a wireless number I can text? | DNC mixes landlines and wireless; doesn't tell you which |
| 2. Reassigned / disconnected | Does the current owner match my consent record? | DNC ignores reassignment entirely |
| 3. Federal DNC | Did this person opt out of telemarketing? | This is the one it does cover |
| 4. State DNC | Any stricter state-level opt-out? | Federal list is federal-scoped only |
| 5. Litigator / TCPA-complainer | Has this person sued over a text before? | Completely separate database from DNC |
| 6. Internal opt-out | Did this contact tell me to stop? | Regulators check your own list first |
That last row is the one people forget most. Your own internal do-not-call list — people who replied STOP or told you to quit — is the first thing regulators check, and it's entirely on you to maintain. More on why in the internal do-not-call list regulators check first.
How this works in Ready
Ready's standalone scrub checks each number against known TCPA-litigator lists and DNC-complainer lists and auto-suppresses matches before send, at $0.005 per contact. You pay only for what you scrub — no subscription. On a 100,000-contact list that's $500 total, against exposure that starts at $500 per text if you're wrong.
A few things it's honest to say plainly:
- The scrub is one layer, not immunity. Consent is still your responsibility, and no scrub makes a bad list legal to text.
- It pairs with the rest of the stack: automatic STOP handling propagates opt-outs across campaigns, and quiet-hours enforcement holds sends outside permitted local hours. Scrub + STOP + quiet-hours + real consent is the combination that actually reduces risk — the layering is covered in the three layers of TCPA risk reduction.
- You don't have to send SMS through us to use the scrub. It's standalone.
The practical takeaway
"We scrubbed against the federal DNC" and "we're covered" are two different sentences. The federal registry answers one narrow question — telemarketing-call opt-outs, landlines included — and stays silent on line type, reassignment, state rules, and the litigators who actually file the suits.
If you text cold or aged lists, layer your scrubs in order: line-type first, reassignment next, then DNC (federal and state), then litigator, then your own internal opt-outs. Each layer is cheap. The one violation any of them catches usually isn't.
If you want to run a list through the litigator + DNC layer before your next blast, you can start with Ready here — 2,500 free credits, no card. Or read scrub before you blast for the full cold-list workflow first.