2026-18366Proposed RuleWallet

FCC Cracks Down on Robocall Database Abusers with New Rules

Published Date: 9/9/2026

Proposed Rule

Summary

In this document, the Federal Communications Commission (Commission) proposes steps to strengthen the reliability, integrity, and effectiveness of the Robocall Mitigation Database (RMD or Database) as a core component of its illegal-call prevention framework. The Commission proposed measures aim to ensure that RMD filings are accurate, complete, and current, and to safeguard the Database so that only legitimate, transparent, and accountable providers may enter or remain listed. Specifically, the Commission proposes and seeks comment on measures to clarify which entities are required to file in the RMD, enhance the accuracy and completeness of submitted information, and specify which portions of filings may be publicly disclosed. Additionally, the Commission proposes and seeks comment on new tools to prevent bad actors and noncompliant providers from accessing or remaining in the RMD, including strengthened screening procedures for new filers, improved mechanisms for identifying noncompliant providers, expedited removal processes, and safeguards to prevent unauthorized re- entry into the Database.

Analyzed Economic Effects

8 provisions identified: 1 benefits, 5 costs, 2 mixed.

More kinds of providers must file

The FCC proposes to clarify and codify which entities must submit Robocall Mitigation Database (RMD) filings. The proposal explicitly lists that in addition to traditional wireline, wireless, and VoIP providers, entities such as PBXs, dialing platforms, cloud service providers, over‑the‑top services, call centers, value‑added service providers, telephone number service providers (TNSP), VoIP resellers, and MVNOs meet the definition of "voice service" and therefore must file in the RMD if they provide voice service.

New certifications and 24‑hour traceback duty

The FCC proposes requiring RMD filers to make specific certifications, including attestation‑level STIR/SHAKEN certifications for providers that serve end users directly, a certification that they have not submitted false or misleading information, certification of compliance with illegal‑call rules, and a commitment to respond within 24 hours to traceback requests and to cooperate in investigations. The Commission also seeks comment on requiring participation in the Industry Traceback Group's automated traceback response process as a condition of being listed in the RMD.

Temporary SPC token exemption with OCN rule

The FCC proposes a new temporary exemption for providers that are in the process of obtaining an SPC token. To claim this temporary exemption, a filer would need to describe steps taken to obtain an SPC token and provide its Operating Company Number (OCN) on the RMD. The Commission also solicits comment on whether filings claiming the exemption should be suspended or removed automatically after a specified number of days if not updated. Providers must update RMD filings within 10 business days of any change to the information.

Stronger screening, removal, and re‑entry safeguards

The FCC proposes new tools to keep bad actors out of the RMD, including strengthened screening for new filers, improved ways to identify noncompliant providers, expedited removal procedures, and safeguards to prevent unauthorized re‑entry into the Database. The goals are to ensure RMD filings are accurate and that only legitimate, transparent, and accountable providers are listed.

Affiliates must each file separately

The FCC proposes to codify that parent companies, affiliates, and subsidiaries that independently meet the definition of a voice service provider must each submit a separate RMD filing. The rule aims to prevent filers from hiding relationships among entities in the Database.

New rules for third‑party filings and declarations

The FCC seeks comment on requiring greater transparency and accountability when a third party prepares or submits an RMD filing, including whether an officer of the provider must sign the declaration under penalty of perjury and whether third parties must provide contact information and their FCC Registration Number (FRN). The Commission also asks whether to permit or limit use of third‑party agents and whether to create safe harbors.

Tightening STIR/SHAKEN exemption claims

The FCC proposes to strengthen rules for claiming STIR/SHAKEN implementation exemptions by requiring providers to cite the exact exemption rule and to explain in detail the facts showing the exemption applies. The proposal would require providers to include facts about their network and any steps taken to confirm they cannot implement STIR/SHAKEN.

Foreign providers: RMD rules, STIR/SHAKEN status

The FCC proposes clarifications on how RMD filing requirements apply to foreign voice service providers. The proposal states foreign providers are subject to the same RMD filing, removal, and criteria requirements but are not required to implement STIR/SHAKEN, and it seeks comment on how foreign providers should indicate their STIR/SHAKEN implementation status (including in the context of Cross Border Call Authentication).

Personalized for You

How does this regulation affect your finances?

Personalize government policy and PRIA will tell you what this federal register document means for your household, plus every other regulation we track. PRIA reads each provision against your financial profile to show you exactly what matters to your wallet.

Key Dates

Published Date
Effective Date
Comments Due
9/9/2026
10/9/2026
11/9/2026

Department and Agencies

Department
Independent Agency
Agency
Federal Communications Commission
Source: View HTML

Related Federal Register Documents

Previous / Next Documents

Back to Federal Register