STIR/SHAKEN, explained in plain English.
The system carriers use to authenticate caller ID doesn't stop spoofing outright and doesn't label spam calls. Here's exactly what it checks, the attestation levels explained plainly, and where the rules stand today.
Last verified September 20, 2026
What STIR/SHAKEN actually does
STIR/SHAKEN is a caller ID authentication framework: a set of technical standards that let the carrier a call originates on cryptographically "sign" it, and let the carrier delivering it to you check that signature before your phone rings. It runs on IP-based call paths. In the FCC's own words, it "consists of a set of technical standards and protocols that allow for the authentication and verification of caller ID information for calls carried over Internet Protocol (IP) networks."
What it does not do: the FCC is explicit that STIR/SHAKEN "can help consumers identify when the number displayed for an incoming call may be spoofed... but it does not let them know who is calling." It does not label a call as a scam, and a Scam Likely tag "might not be related to" a call's attestation level at all — they are two separate systems.
The three attestation levels, in plain English
| Level | What it means |
|---|---|
| A — Full attestation | The carrier originated the call, knows its customer, and has verified that customer's right to use the number shown. The strongest signal the number wasn't spoofed. |
| B — Partial attestation | The carrier originated the call and knows its customer, but has not verified the customer's right to that specific number. |
| C — Gateway attestation | The carrier is only the entry point for a call that started elsewhere (for example, an international gateway) and has no relationship with whoever placed it. |
The FCC's own framing: calls with A-level attestation "carry the best available assurance that the number has not been spoofed." B and C-level calls "are not necessarily spoofed, but they lack the assurance of the highest attestation level." Some phones and carrier apps show a checkmark or shield icon for A-level calls; the FCC cautions that icon means the number wasn't altered in transit, not that the caller is trustworthy.
Is it actually required today?
Mostly, yes, with a shrinking list of exceptions. The mandate, driven by the 2019 TRACED Act, required implementation on IP networks starting June 30, 2021, and was later extended to cover nearly all voice service providers. Small providers had extensions, but those have expired: the extension for non-facilities-based small providers ended June 30, 2022, and for facilities-based small providers on June 30, 2023.
| Date | What happened |
|---|---|
| 2019 | The TRACED Act becomes law, directing the FCC to mandate caller ID authentication. |
| June 30, 2021 | Implementation deadline for STIR/SHAKEN on IP-based portions of major carriers' networks. |
| Sept 28, 2021 | Robocall Mitigation Database filing requirement takes effect; carriers may no longer accept traffic from unlisted providers. |
| June 30, 2022 | Extension for non-facilities-based small providers expires. |
| June 30, 2023 | Extension for facilities-based small providers expires; a narrower satellite-specific hardship extension is added the same year. |
| Oct 7, 2025 | FCC proposes (not yet adopted) requiring a verified caller name on fully authenticated calls. |
| May 21, 2026 | FCC proposes (not yet adopted) tightening "know your upstream provider" rules and repealing remaining hardship exemptions. |
As of today, four narrow categories can still be exempt or extended under FCC rule (47 CFR § 64.6304): providers on non-IP networks (STIR/SHAKEN only works on IP, so this is an ongoing structural extension, not a loophole), providers that can show "undue hardship" obtaining the security credential the system requires, the 2023 hardship extension specific to small providers using satellites for calls on US numbers, and providers that genuinely lack control over the infrastructure needed to implement it at all.
The two 2026 FCC proposals above — one on "knowing your upstream provider" (FCC 26-32) and a companion proposal tied to the Robocall Mitigation Database (FCC 26-49) — would repeal the two hardship-based exemptions and tighten the rules further. Both are still open proposals as of this guide's last verification, not adopted rules. The October 2025 verified-caller-name proposal is likewise still a proposal, not yet in effect.
One industry figure worth knowing, though it's a vendor statistic cited in an FCC filing rather than an FCC measurement: large carriers reportedly exchange STIR/SHAKEN-signed traffic on roughly 86% of the calls they pass between each other.
The Robocall Mitigation Database
Every voice service provider — originating, intermediate or terminating, including VoIP resellers and mobile virtual network operators — has to file a certification of its STIR/SHAKEN status and a robocall mitigation plan in the FCC's Robocall Mitigation Database (RMD). Since September 28, 2021, other carriers are not allowed to accept traffic from a provider that isn't listed, which is the actual enforcement mechanism behind the mandate: a provider that skips STIR/SHAKEN and skips filing a mitigation plan risks other carriers refusing its traffic outright, not just a fine. You can check the live filing status of a provider at the RMD portal. One quirk worth flagging: the FCC's own descriptive page about the RMD carries a banner saying it "has been archived and is no longer actively maintained," even though the filing requirement itself is very much active and central to the FCC's current rulemaking — use the live portal above, not that archived page, for current information.
Sources
FCC: Call Authentication · FCC Call Branding FNPRM Fact Sheet (attestation levels) · FCC “Know Your Upstream Provider” FNPRM Fact Sheet · FCC Robocall Mitigation Database FNPRM (FCC 26-49) · FCC Robocall Mitigation Database, live filing portal
STIR/SHAKEN questions, answered.
Does STIR/SHAKEN stop spam and scam calls?
What do the A, B and C attestation levels mean?
Is STIR/SHAKEN mandatory for all carriers now?
What does a checkmark or shield icon on a call mean?
What is the Robocall Mitigation Database?
Are there new STIR/SHAKEN rules coming?
What actually happens if a carrier skips STIR/SHAKEN?
When did STIR/SHAKEN actually become mandatory?
Wondering why a call still got flagged despite looking authenticated? See our Scam Likely guide. Want to know when a spoofed number crosses into illegal? See caller ID spoofing explained.