What the FCC Robocall Mitigation Database is and how to look up a carrier

What is the Robocall Mitigation Database?

The Robocall Mitigation Database (RMD) is a public database on the Federal Communications Commission (FCC) website that lists every provider that has filed a robocall-mitigation certification under 47 CFR 64.6305. Koda Voice LLC is listed in it. This guide explains who must file, what a filing contains, and how to look up any carrier and read the entry.

The definition is written into the FCC’s own rules. 47 CFR 64.6300 defines the Robocall Mitigation Database as a database accessible through the Commission’s website that lists all entities that make filings under section 64.6305. The database sits inside the FCC rules that followed the Pallone-Thune TRACED Act. That Act added 47 U.S.C. 227b, which directed the FCC to require voice service providers to implement the STIR/SHAKEN caller-ID authentication framework in their IP networks. The RMD is where each provider goes on record about that implementation and about the program it runs to keep illegal calls off its network.

For a vetting analyst, the entry is a place where the provider has certified facts to a federal regulator under its own legal name, alongside its Form 499 and CORES records.

Who has to file in the RMD?

Voice service providers must file. Under 47 CFR 64.6305(d), a voice service provider certifies that all of the calls it originates on its network are subject to a robocall mitigation program that meets the rule’s requirements. The same section covers the other providers in the call path, so a company that carries other providers’ calls rather than originating its own should read the rule for its own role. The rule speaks in terms of role in the call path, not company size.

A provider needs the listing before another carrier may accept its calls directly and before the STI Policy Administrator (STI-PA) will clear it for STI certificates, so the listing comes early in a new carrier’s build.

What does an RMD certification contain?

An RMD certification contains a certification statement, a traceback commitment, and the provider’s identity and program details. The first two are quoted below from 47 CFR 64.6305; the rule lists the rest:

• The certification. A statement that all calls the provider originates on its network are subject to a robocall mitigation program.
• The traceback commitment. A statement of the provider’s commitment to respond within 24 hours to all traceback requests from the Commission, law enforcement and the industry traceback consortium.
• Identity, program and status details. The remaining required elements, including the provider’s identity, its Operating Company Number (OCN) if it has one, and a description of its mitigation program, are listed in the rule text. The entry also records what the provider certified to the FCC about implementing STIR/SHAKEN; that field is easy to misread and has its own section below.

The Industry Traceback Group (ITG) has been the FCC-designated traceback consortium since July 2020, and its own account states that it has been re-designated each year since. The RMD certification is where the provider commits to answer traceback requests; the 24-hour clock is the standard the provider signed up to.

What happens to a provider that is not listed in the RMD?

A domestic voice service provider that is not listed in the RMD cannot lawfully have its calls accepted directly by a downstream provider, because the FCC’s rules say so expressly. 47 CFR 64.6305(g)(1) states that intermediate providers and voice service providers shall accept calls directly from a domestic voice service provider only if that provider’s filing appears in the Robocall Mitigation Database and has not been de-listed under an enforcement action. The obligation sits on the receiving carrier, which is why its vetting team checks the database.

A second consequence makes the listing a precondition rather than a formality. The Secure Telephone Identity Governance Authority (STI-GA) sets the eligibility rules for STIR/SHAKEN certificates, and its SPC Token Access Policy requires a current FCC Form 499-A, an assigned OCN, and an FCC certification with a listing in the Robocall Mitigation Database before the STI Policy Administrator (STI-PA) will clear a provider for STI certificates. A provider outside the RMD is not cleared for STI certificates, so it cannot sign calls under its own identity within the SHAKEN framework.

How do you look up a carrier in the RMD?

The lookup takes a few minutes and needs no account. Follow these steps:

1. Get the exact legal name. Take the entity name from the provider’s website footer, terms of service or about page, not the brand name. “Koda Voice LLC”, for example, not “Koda”.
2. Open the listings. Search the FCC’s public Robocall Mitigation Database listings, the same portal the Trust Center links for Koda’s own entry. The portal renders in a browser, not in a plain fetch.
3. Search the legal name and open the entry. If nothing matches, try a prior name or the parent entity. A provider may file under a name that differs from its brand.
4. Read the entry field by field. Use the table below; note the filing status and the STIR/SHAKEN field in particular.
5. Cross-check the identifiers off-site. Confirm the FRN in the FCC’s CORES public search, the Form 499 record in the FCC Form 499 Filer Database, built from filings with the Universal Service Administrative Company (USAC), and, for signing, the STI-PA’s list of authorized service providers.
6. Record what you saw and when. Entries change as providers update them. Note the date, the status field and the STIR/SHAKEN field for the next reviewer.

How to read an RMD listing

An RMD listing rewards a field-by-field read. Each field has a source outside the database to compare it with.

The STIR/SHAKEN implementation field is the one most often misread. It records what the provider certified when it filed or last updated the entry; it is not a live feed from the signing infrastructure. A provider that filed before it obtained its STI certificate shows its earlier status until it updates the entry. The live test of whether a provider can sign under its own identity is the STI-PA’s authorized-provider list, and the attestation a call carries is decided call by call under the A, B and C attestation levels.

What an RMD listing does not prove

An RMD listing proves that a certification was filed. It does not prove several things a vetting team still needs to know:

• That the program is run as described. The certification is the provider’s own statement. The database records it; it does not audit it.
• That the provider signs its own calls. Signing requires an STI-PA authorization and a certificate from an approved STI Certification Authority. The STI-PA list is the check.
• What attestation level calls carry. Attestation is decided per call by the signing provider according to what it knows about the customer and the number.
• That the provider is a carrier rather than a reseller. A reseller can file in the RMD. The FRN, the Form 499 filer record, the OCN and the STI-PA authorization, read together, show whether the company holds its own carrier credentials and signs under its own certificate or under someone else’s.

Our checklist for verifying a VoIP carrier puts the RMD check in sequence with the other registry checks a vetting team runs.

When does an RMD entry change?

An RMD entry reflects what the provider certified when it filed or last updated the listing. The rule text at 47 CFR 64.6305 sets out when a provider must update its filing, and the current text is the authority on the deadlines. A listing that was accurate when filed can lag a newly assigned OCN, a newly issued certificate or a change of ownership until the provider updates it, so record the date you read it.

How this applies to Koda Voice

Koda Voice LLC is listed in the FCC Robocall Mitigation Database. The listing was filed in July 2026 and sits alongside the other identifiers in the Trust Center: FCC Registration Number 0038517058, USAC Form 499 Filer ID 839032, Operating Company Number 583H assigned by NECA in September 2026, and STI-PA authorization under Service Provider Code 583H with an STI certificate issued by an approved STI Certification Authority.

Koda’s RMD listing (July 2026) predates its OCN (September 2026) and its STI certificate (September 2026). The STI-GA policy makes an RMD listing a prerequisite for the certificate, so that order is built into the process. It is also why this article insists on two checks: the RMD entry for the mitigation program and traceback commitment, and the STI-PA’s authorized-provider list for signing status. Calls originated on Koda’s network are signed under Koda’s own Service Provider Code (583H), not a reseller’s certificate; the mechanics are on the STIR/SHAKEN page.

The program behind Koda’s certification is summarized on the robocall mitigation page: Know-Your-Customer review at onboarding, a published acceptable-use policy, traffic-quality monitoring per customer and per route, and cooperation with the Industry Traceback Group. Traceback requests and KYC documentation go to compliance@kodavoice.com.

This article summarizes public rules for a general reader. It is not legal advice.