How to check if a phone number was reassigned

The FCC's Reassigned Numbers Database (RND) answers one question: has this phone number been permanently disconnected since a date you give it? If the answer is no and you had valid consent, you get a safe harbor from TCPA liability if the database turns out to be wrong. That is narrower than most teams assume. The RND does not tell you who holds the number today, and it says nothing about numbers you never had consent for. This post walks through how the database works, what each answer means, and a pre-dial workflow that closes the gap. General information, not legal advice.

Key takeaways

• Query the RND with the phone number and the date you last knew it belonged to your contact, usually the consent date.
• "Yes" means the number was permanently disconnected on or after that date: do not call on the old consent.
• "No" is the only answer that can support the safe harbor, and only for calls you had consent to make.
• The RND never names the current holder, so a current phone-to-person check is a separate step.

Why reassigned phone numbers cause wrong number calls

TCPA consent attaches to a person, not to a phone number. When a carrier disconnects a number, it holds the number out of service for an aging period (at least 45 days for residential numbers, up to 90) and can then assign it to a new subscriber. Your records still say "consent on file". The person answering never gave it.

That is how careful teams end up making wrong number calls: the process was fine, the data went stale. For autodialed or prerecorded calls and texts to a cell phone, each call to someone who never consented can carry statutory damages of $500, or up to $1,500 if willful. In collections there is a second cost. Calling a stranger about someone else's debt risks disclosing the debt to a third party, which the FDCPA restricts separately from the TCPA.

What the Reassigned Numbers Database tells you

Every phone provider must report permanent disconnections to the database administrator by the 15th of each month. You register as a caller (or use a caller agent), then query with two inputs:

• The 10-digit phone number.
• A date: when you obtained consent, or the last date you could confirm the person was reachable at that number.

The database returns one of three answers:

Queries can be single or bulk, and the database is subscription-priced by query volume. Check the administrator's current price list rather than relying on a figure from an old blog post.

How the TCPA safe harbor works

Under 47 CFR 64.1200(m), a caller is not liable for a call to a reassigned number if it can show all of these:

• It had the appropriate prior express consent from the person it meant to reach.
• It queried the database, using the most recent data the administrator had, before the call.
• The database answered "no".
• The call reached the wrong person because the database was wrong.

The burden of proof is on you. That makes the query record the asset: the number, the date you submitted, the response, and the timestamp, stored against the contact and the call. A safe harbor you cannot document is one you do not have.

Note what the safe harbor does not cover. It protects you from the database's errors, not your own. If you query with a date later than your real consent date, if you call after a "yes", or if you never had consent in the first place, there is no harbor. The TCPA compliance guide covers consent types and penalties in more depth.

A pre-dial workflow for reassigned numbers

The RND tells you a number changed hands; it cannot tell you whether the number in your file is the right person's number today. A practical workflow uses both kinds of check, in this order:

• Permission first. Check consent, internal Do-Not-Call, cease-communication, and attorney flags. If any of these stops the call, the rest does not matter.
• Query the RND. Submit the number with your consent date or last-confirmed-contact date. Store the response.
• Act on the answer. "Yes" removes the number from autodialed and prerecorded campaigns. "No data" routes it to manual verification.
• Check current ownership. For numbers that pass, look up who the number is associated with now and compare the name to your contact. A mismatch is a reason to hold the number even after a "no".
• Re-query on a schedule. Disconnections are reported monthly, so a result from 90 days ago tells you little. Re-check before each campaign and before calling any number that has gone quiet.

Step 4 is where a consumer-records lookup fits. CoverFi supports searching by phone alone and returns candidate people with a 0-100 match-confidence score, so a mismatch between the name on file and the current holder shows up before the dial rather than after. Use it as contact-data hygiene, never as a substitute for the RND query or for consent; the pre-contact checklist for collections shows where both checks sit among the other pre-call steps.

Frequently asked questions

Does a "no" from the Reassigned Numbers Database mean the number still belongs to my contact?

Not exactly. It means no permanent disconnection was reported since your date. It can support a safe harbor if you had consent, but it does not confirm who answers the phone.

What date should I use in an RND query?

The date you obtained consent from the person, or the most recent date you confirmed they were reachable at that number. Using a later date than you can document weakens the safe harbor.

Do I need to query the RND for manual calls?

The safe harbor matters most for autodialed and prerecorded calls and texts, where TCPA consent rules apply. Many teams query every number anyway, because wrong-party calls cause FDCPA and complaint problems regardless of how they were dialed.