ARTICLE
16 February 2026

All Robocall Mitigation Database Filers Must Recertify Their Submissions By March 1, 2026, Or Risk Removal And Blocked Traffic

RJ
Roth Jackson

Contributor

Roth Jackson and Marashlian & Donahue’s strategic alliance delivers premier regulatory, litigation,and transactional counsel in telecommunications, privacy, and AI—guiding global technology innovators with forward-thinking strategies that anticipate risk, support growth, and navigate complex government investigations and litigation challenges.
As discussed in our previous client advisory, the Federal Communications Commission (FCC) has adopted new rules requiring all Robocall Mitigation Database...
United States Corporate/Commercial Law
Diana James’s articles from Roth Jackson are most popular:
  • in United States
Roth Jackson are most popular:
  • within Technology topic(s)

As discussed in our previous client advisory, the Federal Communications Commission (FCC) has adopted new rules requiring all Robocall Mitigation Database (RMD) filers to recertify their filings on an annual basis. This initiative is part of the agency's continued effort to strengthen industry accountability and enhance consumer protection against illegal robocalls.

This year, providersmust recertify their RMD filings by March 1, 2026.

Risks for Noncompliance

Failure to recertify by the March 1 deadline may result in removal from the Robocall Mitigation Database, which would obligate other providers to block all traffic from the noncompliant entity. Providers removed from the RMD may face significant business disruption, as reinstatement requires a new filing, FCC review, and can take up to a year (or more) to complete. Noncompliance also exposes providers to potential enforcement action and monetary penalties.

Multi-Factor Authentication

The FCC has also implemented multi-factor authentication for RMD access. Specifically, the new rules require each filer to authenticate its identity, as opposed to simply providing a username and password, by one of two methods: (1) obtain and enter a temporary code generated from the Google Authenticator app; or (2) utilize the Okta Verify authenticator app. The RMD provides links to set up and activate those apps.

Key Action Items

  • Appoint a person to manage multi-factor authentication, with CORES credentials linked to their device.
  • Coordinate internally among legal, compliance, and technical teams to ensure consistency between the RMD filing and actual operational practices.
  • Review your existing RMD filing carefully. Verify that all fields, particularly corporate identifiers, contact details, and robocall mitigation plans, reflect current information and practices.
  • Update your robocall mitigation plan, if changes were made since your most recent filing.
  • Recertify the RMD filing through the FCC portal by March 1, 2026.
  • Engage outside counsel or compliance experts early to avoid last-minute issues.

Conclusion

Recertification is now a mandatory annual obligation for all RMD filers. Providers that fail to act promptly risk substantial operational and regulatory consequences. Our firm assists numerous clients with RMD recertification, STIR/SHAKEN compliance, and ongoing robocall mitigation strategy development.

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

[View Source]

Mondaq uses cookies on this website. By using our website you agree to our use of cookies as set out in our Privacy Policy.

Learn More