Link Leads Blog · August 27, 2026
A phone number captured 60 days ago isn't guaranteed to belong to the same person today. The FCC built a database specifically to answer that question, and running a list through it before a campaign is a five-minute check most agents skip. Here's what it flags, how the safe harbor actually works, and where it fits next to a DNC scrub.
This is not legal advice. TCPA rules, safe harbor requirements, and FCC database pricing change over time — confirm current requirements with an attorney or compliance vendor before building a calling program around this post.
The Reassigned Numbers Database (RND) is an FCC-commissioned tool that's been live since November 2021. It answers one narrow question: has this phone number been permanently disconnected from its previous subscriber since a date you provide? Carriers report disconnections into it, and it now covers wireless, landline, and VOIP numbers. Query a number with the date your record was captured, and it comes back one of three ways: yes (reassigned since that date), no (not reassigned), or no data (the provider hasn't reported enough history to say). It doesn't tell you who owns the number now — only whether the person behind your record is still likely to be the one who answers.
Roughly 35 million wireless numbers get disconnected and freed up for reassignment every year in the US — about one in ten active numbers churning annually. That number resets and gets handed to a new subscriber faster than most agents assume. A fresh, same-day lead has almost no exposure to this. An aged data list is built the opposite way: the whole value proposition is a number that was valid 30 to 90 days ago, not a number guaranteed valid today. That gap is exactly the window where reassignment risk lives, which makes an RND check a natural pairing with an aged list rather than something aged data makes irrelevant.
The FCC's safe harbor protects a caller who checked the database and got a "no" or "no data" result, even if the number turns out to have been reassigned anyway — as long as the check happened within 30 days of the call. That 30-day clock is the operational detail that matters: it's not a one-time check at list purchase, it's a check that has to be current relative to when you actually dial. A list you bought 45 days ago and are calling for the first time today needs a fresh query, not the one you ran at purchase. Final Expense Calling Leads carry an added date on every record for exactly this kind of math — the further back that date sits, the more that specific record is due for a check before it gets dialed.
The database supports bulk lookups, which is the only realistic way to run this against a list of any size — nobody is querying one number at a time against a file with thousands of rows. The practical workflow: export the phone column with a "date to check from" for each record (purchase date works if you don't have a per-record date), run it through the FCC's bulk query process or a service that resells access to it, and get back a yes/no/no-data flag per number. Numbers flagged "yes" come out of the calling list entirely — that's not the person you have information on anymore. "No" and "no data" both qualify for the safe harbor and stay in, with the check timestamped so you can show it ran inside the 30-day window if it's ever questioned.
An RND check is a separate question from a DNC scrub or a landline/wireless check — one flags numbers that were reassigned, the others flag numbers you're not allowed to call or can't text. A list can pass one of these checks and still fail another, so all three belong in the same pre-campaign pass rather than treated as substitutes for each other. For the landline and DNC half of that stack, the tool we point buyers at is Landline Remover (disclosure: that's an affiliate link and we may earn a commission) — upload the CSV and it strips landlines, disconnected numbers, and DNC-listed contacts in one pass. The RND query runs as its own separate step, since it's checking a different registry entirely.
A "no data" response isn't a clean bill of health — it means the number's carrier hasn't reported enough disconnection history for the database to have an opinion, which happens more often with smaller carriers and MVNOs. It still qualifies for the safe harbor, but it's worth treating differently operationally: some agents route "no data" numbers to a lower-priority call block, or pair them with an opening line that confirms identity before any account-specific talk track starts, since the safe harbor covers legal exposure but doesn't guarantee the person on the line is who your record says.
The check costs a few minutes and a small per-query fee against a list that already costs real money to buy and dial — skipping it to save that step is a bad trade against the safe harbor it buys. Treat it the same way as the scrub timing described in the power dialer setup guide: run it at list load, log the date it ran, and re-run it if a list sits unworked past the 30-day window before the first dial goes out. Build a state-targeted order sized for how fast you can actually work it, or grab the free 100-row sample to see the fields a file ships with before setting up this check on your end.