The FCC’s Reassigned Numbers Database — Safe-Harbor Mechanics and Pricing, as of July 2026

Reassigned Numbers Database (RND): The Caller’s Guide

The Reassigned Numbers Database answers one question: has this phone number been permanently disconnected — and possibly handed to someone new — since a date you specify? Consent-based calling lives or dies on who holds the number today, and the RND is the only database the FCC pairs with a TCPA safe harbor: query it correctly, receive a “no,” and 47 CFR 64.1200(m) shields the call even if the answer was wrong. Below: the database, the safe harbor, query pricing (from $8 a month), and the workflow — as of July 2026.

This page is education, not legal advice. A dialer is a tool — compliance depends on how you use it. Enzo does not query the RND or scrub lists against DNC registries — both steps happen before a list reaches any dialer. Consult a TCPA attorney about whether your program needs RND checks.

The Problem the RND Solves: Numbers Change Hands, Consent Doesn’t

Phone numbers get recycled: a subscriber cancels service, the carrier eventually reassigns the number, and the stranger who inherits it never gave you consent — but your CRM still shows a signed record on that number, so your campaign dials it. The legal basis for a call attaches to a person, and the number quietly stops belonging to that person. Under the TCPA, calls that needed consent and didn’t have it run $500 to $1,500 each — the damages math is in TCPA fines and penalties. The FCC’s answer was FCC 18-177 (CG Docket No. 17-59, adopted December 12, 2018) — the Second Report and Order that created the RND, which went live November 1, 2021.

What the FCC Reassigned Number Database Is

The RND is operated at reassigned.us by SomosGov, Inc., the independent Administrator the FCC selected through competitive procurement. Its data comes from the carriers under two FCC rules:

• Monthly reporting. Service providers must report their permanently disconnected numbers to the RND each month.
• The 45-day aging floor. Since July 27, 2020, providers must age a number at least 45 days after permanent disconnection before reassigning it (47 CFR 52.15(f)(8), 52.103(d)) — giving the database time to catch up before the number goes to anyone new.

The RND is not a do-not-call list — it says nothing about whether a number’s owner wants your call. It reports one fact, permanent disconnection since a date, and the safe harbor is built on it.

How a Query Works: Yes, No, or No Data

An RND query pairs a phone number with a date — typically when consent was captured or the subscriber was last confirmed. Three answers come back:

• “No” — the number has not been permanently disconnected since your date. This is the only response that carries the safe harbor.
• “Yes” — the number has been permanently disconnected since your date and may belong to someone your consent never covered — pull it and re-verify.
• “No data” — the database cannot verify the number against your date. Consent dates before January 27, 2021 return “no data,” and no safe harbor attaches. Treat it like a “yes”: unverified.

The Safe Harbor: 47 CFR 64.1200(m)

Under 47 CFR 64.1200(m), a caller avoids TCPA liability for a call to a reassigned number when three conditions hold:

1. The caller queried the most recent update of the database;
2. The database returned a “no” — not permanently disconnected since the date supplied; and
3. The call resulted from that erroneous response — the database was wrong, and the caller relied on it.

Condition three is the point: the protection exists precisely for the case where you did everything right and the database still missed a reassignment — the only TCPA safe harbor aimed squarely at wrong-party liability. Two disciplines follow: query the most recent update, and log every query, response, and date — an undocumented safe harbor is one you do not have.

What the Safe Harbor Does Not Cover

The RND defense is narrow on purpose. Two boundaries matter:

• It does not launder an otherwise unlawful call. A number on the National DNC Registry that you had no exemption to dial stays a violation whatever the RND said. DNC scrubbing is a separate obligation on its own 31-day cadence — see the DNC scrubber guide.
• Don’t confuse it with the ported-number safe harbor. A separate, narrower rule at 47 CFR 64.1200(a)(1)(iv) shields calls within 15 days of a wireline-to-wireless port — but only against the autodialed/prerecorded-call prohibition, and only if the number is on neither the national registry nor your internal list. It is not a general wrong-number defense.

RND Pricing: The Query Tiers

Access is subscription-based, priced by query volume. The schedule took effect April 28, 2025 — a 20% across-the-board cut that expanded the tiers from 6 to 10, plus 3A and 4A:

Annual options run from 12,000 queries for $86 at Tier 1 up to 600,000,000 for $285,600 at Tier 10, and Caller Agent discounts apply on Tiers 6–10. This is the current published pricing, but the FCC has adjusted it more than once (most recently the 2025 cut) — confirm the live schedule at reassigned.us before subscribing.

RND Scrubbing in a Real List Workflow

RND scrubbing is a pre-upload step. A workable sequence for a consent-based program:

1. DNC scrub first, every list, every cycle. Third-party scrub against the national registry and applicable state lists — the RND does not touch this obligation.
2. Flag the records whose lawful basis is person-specific — signed consent for autodialed or prerecorded calls, or an established business relationship that justifies calling a DNC-registered customer. These are the rows where reassignment creates legal exposure, not just waste.
3. Query those numbers against the RND with the consent or last-contact date, before the list reaches the dialer.
4. Route the responses: “no” → keep, dial, and log; “yes” or “no data” → pull and re-verify through another channel.
5. Keep the receipts and re-query stale segments. Store query dates, responses, and consent dates — the safe harbor rewards the most recent update, not last year’s.

Programs built entirely on live, manually dialed cold calls to non-DNC numbers have less exposure — those calls need no prior consent under federal law, so a reassigned number mostly wastes a dial. Where that baseline ends is covered in TCPA for cold callers.

Where Enzo Fits — and Where It Doesn’t

Enzo does not query the Reassigned Numbers Database and does not scrub lists against national or state DNC registries — run your third-party DNC scrub and any RND checks first, then upload the clean CSV. Enzo’s internal DNC is campaign-level only: mark a contact DNC and they stay excluded from that campaign, but marks do not carry across campaigns — keep your master suppression file and RND query logs outside the dialer and re-apply them to every new campaign. The dialer itself is compliant as a tool; compliance depends on how you use it — the consent you can prove, the scrubs you ran, and the query records you kept.

The RND is one of the cheaper compliance pieces to get right: one subscription, one query per at-risk record, three possible answers, and the only reassigned-number safe harbor the TCPA offers. Have counsel confirm which lists actually need it.

See how clean, pre-scrubbed lists flow into a real calling workflow — book a free discovery call.

Not legal advice. This guide is general information for outbound calling teams, not legal advice. Rules change and apply differently by state, industry, and call type — confirm your program with qualified telemarketing compliance counsel.

Rules and figures from FCC 18-177 (CG Docket No. 17-59), 47 C.F.R. §§ 64.1200 and 52.15, and the RND Administrator’s published materials and April 2025 pricing schedule at reassigned.us, as of July 2026 — educational only, not legal advice.