Pull to refresh
Logo
FCC forces carriers to start blocking “impossible” caller IDs—and own the blowback

FCC forces carriers to start blocking “impossible” caller IDs—and own the blowback

Rule Changes

Do-Not-Originate blocking goes mandatory nationwide, shifting robocall risk onto the network itself.

December 15th, 2025: DNO blocking goes mandatory nationwide

Overview

Updated May 15

The FCC's robocall fight just hit the part where the referees stop warning and start pulling players off the field. As of December 15, 2025, U.S. voice providers are required to block calls that claim to originate from numbers that should never place outbound calls.

This is a governance shift. The phone network is now designed to distrust "bad identity" by default. Carriers carry more operational and regulatory risk either way: under-block and fraud gets through; over-block and legitimate calls get dropped.

Questions about this story

Free account needed to ask — your question is kept and asked for you right after sign-up. Answers are public.

No questions yet — be the first to ask.

Key Indicators

2025-12-15
Nationwide DNO blocking compliance date
Rule for 47 CFR 64.1200(o) takes effect across domestic voice providers.
3060-1306
OMB control number for the DNO collection
OMB approval triggered the FCC’s 90-day countdown to the effective date.
$13.5B
Estimated annual consumer harm from illegal/unwanted calls
FCC estimate cited in GAO’s review of the rule’s cost-benefit rationale.
6,493
Estimated respondents touched by related FCC robocall info collections
Scale signal: compliance burden spreads far beyond the biggest carriers.

Voices

Curated perspectives — historical figures and your fellow readers.

Ever wondered what historical figures would say about today's headlines?

Sign up to generate historical perspectives on this story.

People Involved

Organizations Involved

Timeline

December 2019 December 2025

11 events Latest: December 15th, 2025 · 9 months ago Showing 8 of 11
Tap a bar to jump to that date
  1. DNO blocking goes mandatory nationwide

    Latest Rule Changes

    Domestic voice providers must block calls using numbers that should not originate calls.

  2. Carriers warn customers about disruptions

    Industry

    Providers flag misconfigured caller ID and private numbering plans as blocking risks.

  3. Federal Register sets the deadline

    Rule Changes

    FCC publishes notice: 47 CFR 64.1200(o) effective December 15, 2025.

  4. OMB approval starts the clock

    Administrative

    OMB approves the DNO information collection required to trigger the effective date.

  5. GAO formalizes the rule’s stakes

    Oversight

    GAO cites FCC’s $13.5B annual harm estimate from illegal and unwanted calls.

  6. FCC adopts “Advanced Methods” order

    Rule Changes

    FCC 25-15 expands DNO-based blocking across domestic voice providers.

  7. FCC proposes wider DNO blocking

    Rule Changes

    Rulemaking tees up expanding DNO obligations to more providers in the call path.

  8. Gateway providers face DNO blocking

    Rule Changes

    Foreign-call entry points must block calls using numbers on reasonable DNO lists.

  9. STIR/SHAKEN mandate accelerates

    Rule Changes

    FCC moves caller-ID authentication from industry idea to compliance requirement.

Scenarios

1

FCC Turns DNO Into a Compliance Tripwire: More Providers Get Isolated

Likely

Discussed by: Telecom law firms tracking FCC enforcement; carrier compliance advisories; trade press covering RMD removals

The most straightforward next chapter is enforcement by consequence: providers that can’t show credible mitigation (or can’t demonstrate “reasonable” DNO practice) get targeted through the FCC’s broader network-access toolchain—database actions, downstream blocking obligations, and rapid “fix it or lose traffic” pressure. Trigger: high-profile scam bursts traced to noncompliant networks, paired with public FCC messaging that the deadline is now live.

2

Overblocking Backlash: Legitimate Callers Demand a Faster “Unblock Me” System

Possible

Discussed by: Enterprise telecom teams, CPaaS providers, and compliance counsel watching post-cutover incident rates

As DNO blocking spreads across routes, edge cases surface: malformed caller-ID headers, private dialing plans, and legacy configurations that “worked” until the network stopped trusting them. A wave of blocked business calls forces carriers to formalize quicker remediation playbooks and pushes the FCC to clarify what “reasonable” means in practice, especially around updating lists and handling disputes.

3

Industry Pushes for a Central DNO List—and the FCC Says No (For Now)

Uncertain

Discussed by: Carrier coalitions and numbering/analytics vendors arguing for standardization

Providers want fewer inconsistent blocks and cleaner interoperability, so they lobby for a more standardized, shared DNO mechanism. The FCC resists because a centralized list creates governance problems: who updates it, how fast, and who gets blamed when it’s wrong. Trigger: measurable inter-carrier inconsistency becomes a public reliability issue, not just a compliance discussion.

Historical Context

3 moments from history that rhyme with this story — and how they unfolded.

2017

FCC’s 2017 shift toward permissive call blocking

The FCC moved from treating blocking as risky discrimination to treating it as consumer protection. Carriers were encouraged to stop “obviously bogus” caller IDs and use analytics, even at the risk of occasional false positives.

Then

Carriers began broader blocking pilots and analytics-based filtering.

Now

Set the precedent that networks can police identity, not just carry traffic.

Why this matters now

Today’s DNO rule is the permissive era turning into a mandate with enforcement teeth.

2020-2023

STIR/SHAKEN rollout and the authentication arms race

Caller-ID authentication became a national compliance project with phased deadlines. It improved traceability but didn’t eliminate scams, because bad actors adapted—using gaps, smaller providers, and non-IP corners of the network.

Then

Authentication coverage expanded, especially among large carriers.

Now

Enforcement focus shifted from “deploy the tech” to “police the ecosystem.”

Why this matters now

DNO blocking complements authentication by targeting identities that are invalid on their face.

2022-2023

Gateway-provider crackdowns and the “border control” model

The FCC targeted the U.S. entry points for foreign-originated robocalls, requiring gateway providers to block certain illegal traffic and respond to tracebacks faster. It treated upstream access like a controlled border, not an open on-ramp.

Then

Gateway providers faced explicit new blocking and reporting obligations.

Now

Created a template for expanding mandatory blocking deeper into domestic call paths.

Why this matters now

The December 15, 2025 effective date extends that “border control” logic across the whole network.

Sources

(14)