All insights
TCPA & Consent

The Reassigned Numbers Database: How the TCPA Safe Harbor Protects Callers, and What It Requires

Phone numbers are disconnected and given to new people every day, and the new subscriber never agreed to your calls. The FCC's Reassigned Numbers Database lets callers check whether a number has changed hands, and offers a safe harbor from TCPA liability to callers who use it correctly.

Who should read thisCompliance and operations leaders at enterprises, contact centers, and messaging programs that call or text customers

First page of the source: FCC 18-177 (Second Report and Order) FCC 18-177 (Second Report and Order) Wrong-number risk$500–$1,500per call to a reassigned number
Primary source · Dec 13, 2018 Open the FCC 18-177 (Second Report and Order)
The bottom line
  • When a number is permanently disconnected and reassigned, the new subscriber has not consented to your calls. Each unlawful call or text can cost $500 to $1,500 in statutory damages.
  • The Reassigned Numbers Database answers one question: has this number been permanently disconnected since a given date? It returns yes, no, or no data.
  • A caller that checks the most recent data, receives "no," and still reaches a new subscriber because the database was wrong is protected by the FCC's safe harbor.
  • The safe harbor covers only the FCC's database, not other commercial sources, and the caller carries the burden of proof.

The problem: numbers change hands

When a customer gives up a phone number, the provider ages it and then assigns it to someone else. FCC rules set the waiting period: at least 45 days and no more than 90 days for residential numbers, and up to 365 days for business numbers. The new subscriber never consented to your calls or texts.

Why it matters. An automated call or text to a reassigned number is made without the recipient’s consent. The TCPA lets consumers sue for $500 per violation, and a court may increase that to $1,500 if the violation was willful or knowing. A list collected years ago can contain many numbers that now belong to strangers.

How the database works

The FCC created the Reassigned Numbers Database in December 2018 (FCC 18-177), and it went live on November 1, 2021. SomosGov, Inc. is the administrator.

  • What goes in. Each month, providers report the most recent date each of their numbers was permanently disconnected. A ported number is not “disconnected.” The database holds no subscriber information beyond that date.
  • What comes out. A caller submits a number and a date, such as when consent was obtained, and receives “yes” (disconnected since then), “no” (not disconnected), or “no data.”
  • Who can query. Callers who agree to use it solely for this purpose, and third parties acting as their agents.

The safe harbor, and its limits

Under 47 CFR 64.1200(m), a caller is not liable for a call to a reassigned number if it shows, “bearing the burden of proof and persuasion,” that:

  1. it checked the FCC’s database, using the most recent update, and received a response of “no”; and
  2. the call happened because the database returned “no” in error.

The limits matter as much as the protection. The FCC declined to extend the safe harbor to other commercial databases, so a check elsewhere does not qualify. The caller must be able to prove the check. And the FCC continues to point callers to the database: in its October 2026 TCPA order, covered in our analysis of the November 25 opt-out rules, it encouraged financial institutions to use it so fraud alerts do not reach a number’s previous holder.

Questions to answer now

Compliance and operations leaders should be able to answer the following with confidence:

Answering these questions takes records, not assumptions. The VoiceAlerts Compliance Team can review where you stand in a free 30-minute briefing.

Key dates

How VoiceAlerts helps

VoiceAlerts is a Somos-registered Reassigned Numbers Database Service Provider Agent. We run RND checks on your behalf and keep the query records you need to rely on the safe harbor.

  • Reassigned Numbers Database checks run as your agent
  • Query records that support the TCPA safe harbor
  • Numbers from older or secondary sources
Book a free 30-minute briefing Explore Compliance & Identity

Get FCC & voice-security alerts

Not ready for a briefing? We’ll send you the next rule change or attack that affects your calls.

By signing up you agree to be contacted by VoiceAlerts. See our Privacy Policy.

Common questions

What is the Reassigned Numbers Database?

A database created by the FCC (FCC 18-177) in which providers report the most recent date each number was permanently disconnected. Callers query a number and a date, and receive "yes," "no," or "no data." It went live on November 1, 2021, and SomosGov, Inc. is the administrator.

How does the Reassigned Numbers Database safe harbor work?

Under 47 CFR 64.1200(m), a caller is not liable for a call to a reassigned number if it shows that it queried the database using the most recent data, received a response of "no," and the call resulted from the database erroneously returning "no." The caller bears the burden of proof.

Can a third party check the database for a caller?

Yes. The FCC provided that third-party contractors can use the database as the agent of their client callers.

How can VoiceAlerts help with Reassigned Numbers Database checks?

VoiceAlerts is a Somos-registered Reassigned Numbers Database Service Provider Agent. It runs checks on a caller's behalf and keeps the query records needed to rely on the safe harbor.

Sources

  1. docs.fcc.govFCC 18-177: Advanced Methods to Target and Eliminate Unlawful Robocalls, Second Report and Order (Reassigned Numbers Database)Released December 13, 2018
  2. docs.fcc.govFCC Public Notice DA 21-67: Reassigned Numbers Database reporting (SomosGov, Inc. as Administrator)January 15, 2021
  3. docs.fcc.govFCC Public Notice DA 21-1649: Reassigned Numbers DatabaseDecember 29, 2021
  4. docs.fcc.govFCC 26-67: TCPA Report and Order and Further Notice of Proposed RulemakingReleased October 1, 2026
  5. ecfr.goveCFR: 47 CFR 64.1200, Delivery restrictions (paragraphs (l) and (m))
  6. ecfr.goveCFR: 47 CFR 52.15, Central office code administration (aging of numbers)
  7. law.cornell.edu47 U.S.C. 227(b)(3): Telephone Consumer Protection Act, private right of action

This article is for general information and is not legal advice. Proposed rules can change before adoption; check the FCC record for the final text.

Free 30-minute TCPA briefing

Could you prove you checked before you called?

Book a briefing with the VoiceAlerts Compliance Team. We review how you confirm that the numbers you call still belong to the people who consented.

  • Reassigned Numbers Database checks run as your agent
  • Query records that support the TCPA safe harbor
  • Numbers from older or secondary sources
Want the details first? Compliance & Identity
Explore the service

Book a 30-minute briefing

Tell us a bit about you. We'll reply within one business day.

By submitting, you agree to our Privacy Policy. We never share your information.

More insights

View all
First page of the source: FCC Report and Order (FCC 26-67) FCC Report and Order (FCC 26-67) TCPA damages$500–$1,500per unlawful call or text
TCPA & Consent

New TCPA Opt-Out Rules Take Effect November 25: What Changes for Callers and Texters

New FCC opt-out rules take effect Nov. 25, 2026: narrower revocations, a designated opt-out method, and wider fraud alerts. What callers should change.

VoiceAlerts Compliance Team Source date · 4 min read
Image from the source: U.S. Attorney's Office, Southern District of New York U.S. Attorney's Office, Southern District of New York Alleged losses$129Mwired by deceived employees
Voice Security

$129 Million Through Cloned Voices: What the Federal Case Against an AI Executive-Impersonation Ring Means for Finance Teams

Prosecutors say three men used AI to clone executives' and lawyers' voices and got companies to wire $129 million. What it means for payment controls.

VoiceAlerts Compliance Team Source date · 4 min read
Image from the source: FBI IC3 public service announcement I-091726-PSA FBI IC3 public service announcement I-091726-PSA Reported losses$1.6BJan 2025 to Jul 2026, FBI
Voice Security

Scammers Are Calling From Government Numbers: $1.6 Billion Lost to Fake Agents, and What Agencies, Banks, and Carriers Can Do

The FBI counts 61,000 government-impersonation complaints and $1.6 billion lost in 19 months, often from spoofed agency numbers. What organizations can do.

VoiceAlerts Compliance Team Source date · 3 min read