Checked
Improving the Effectiveness of the Robocall Mitigation Database; Call Authentication Trust Anchor; Advanced Methods To Target and Eliminate Unlawful Robocalls
Proposed rule · Federal Register document 2026-18366
- Published
- 09/09/2026
- Comments due
- 11/09/2026
- 10 days left
- Effective
- 10/09/2026
- Pages
- 36
Summary
Proposed rule.
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.
Details
- Type
- Proposed rule
- Docket
- WC Docket Nos. 24-213 and 17-97; CG Docket No. 17-59; FCC 26-49; FR ID 364473
- CFR parts
- 47 CFR 0, 47 CFR 1, 47 CFR 64
- Topics
- Administrative practice and procedure, Communications, Communications common carriers, Communications equipment, Penalties, Reporting and recordkeeping requirements, Security measures, Telecommunications, Telephone, Waivers
This page summarizes a Federal Register document. Only the official Federal Register text has legal effect. Comment deadlines can be extended or reopened by a later notice.
Source: Office of the Federal Register, via the Federal Register API · Last updated 09/09/2026