The FCC database where voice service, gateway, and intermediate providers certify their STIR/SHAKEN status and file a robocall mitigation plan, under 47 CFR 64.6305.
The RMD was created as part of the FCC's implementation of the TRACED Act. Each covered provider files a certification stating whether it has fully, partially, or not yet implemented STIR/SHAKEN, along with a robocall mitigation plan describing the specific steps it takes to avoid originating or carrying illegal robocalls. The obligations are codified at 47 CFR 64.6305.
The filing requirements were originally aimed at voice service providers and were later extended to gateway providers and non-gateway intermediate providers. Filings must include identifying details such as the provider's FCC Registration Number and contact information, and providers must update their submissions when the information changes. The FCC has also adopted rules requiring periodic recertification and providing for penalties when filings are false or not kept up to date.
The database has real teeth. Providers are prohibited from accepting traffic directly from providers that do not appear in the RMD, and the FCC has removed providers whose filings were deficient or whose conduct contradicted their plans. Removal effectively cuts a provider off from the U.S. voice network. Downstream providers are expected to check the database before accepting traffic, so a removal takes effect across the industry rather than with a single partner.
Why it matters to carriers
Your RMD listing is effectively your license to exchange traffic with other U.S. providers, and your downstream partners will check it. A vague or outdated mitigation plan is a common reason for FCC scrutiny. Keeping the filing accurate, specific to how your network actually operates, and current after any change is basic operational hygiene.