FCC proposed rules on robotexting and robocall prevention
The Federal Communications Commission (FCC) has proposed rules to prevent robotexting and robocalls to reassigned numbers. Here are the details.
Declaratory ruling on text messaging

This rule would clearly establish that text messaging services are information services, not telephone services. This distinction would allow carriers to continue to use robotext blocking and anti-spoofing measures to protect consumers from unwanted text messages, called robotexts.
“Americans rely on and trust text messaging,” said FCC Chairman Ajit Pai. “That’s why we need to act to prevent a deluge of spam texts and scam messages.”
Order to create database of reassigned numbers
This order would call for the creation of a single, comprehensive database of reassigned numbers. This information would be provided by phone companies that obtain North American Numbering Plan U.S. geographic numbers.
Millions of telephone numbers are reassigned each year. While reassigning numbers is an efficient use of the number pool, it can cause problems for everyone involved:
- Subscribers with reassigned numbers get unwanted calls intended for the previous telephone number holders.
- Subscribers miss calls from parties they forgot to notify after changing their phone numbers.
- Organizations with prior authorized consent are unable to contact their customers and inadvertently annoy new number holders instead.
The reassigned numbers database would enable legitimate callers to check whether a number has been reassigned and thereby avoid making unwanted calls.
Chairman Pai explained, “I’m also proposing new rules to help reduce robocalls to reassigned numbers by creating a database that will help legitimate businesses stop calling those numbers.”
The FCC will discuss these items at its Open Commission Meeting on December 12, 2018.
Feb 1, 2023
STIR/SHAKEN statistics from January 2023
Jan 25, 2023
Reply comments on FCC inquiry into non-IP call authentication
Jan 11, 2023
FCC sends STIR/SHAKEN report to U.S. Congress
Dec 21, 2022
Verizon seeks gateway provider deadline extensions
Dec 19, 2022
FCC decides on the small provider STIR/SHAKEN extension
Dec 14, 2022
Comments on the FCC inquiry into non-IP call authentication
Dec 14, 2022
Webinar recording — Get ready for STIR/SHAKEN
Nov 28, 2022
Webinar — Get ready for STIR/SHAKEN
Nov 21, 2022
ATIS Robocalling Testbed adds features
Nov 9, 2022
Legal Entity Identifiers and call authentication
Oct 26, 2022
Reply comments on SHAKEN extensions and effectiveness
Oct 19, 2022
NTCA suggestions for FCC non-IP SHAKEN inquiry
Oct 17, 2022
Proposed updates to SHAKEN governance standards
Oct 10, 2022
FCC to consider SHAKEN for TDM
Oct 5, 2022
Comments on SHAKEN extensions and effectiveness
Sep 29, 2022
Proposed updates to delegate certificate standards
Sep 19, 2022
Reply comments on proposed SHAKEN and robocall mitigation rules
Aug 29, 2022
Updated SHAKEN standard improves security
Aug 22, 2022
Comments on proposed SHAKEN and robocall mitigation rules
Jul 18, 2022
Final gateway provider SHAKEN rules published
Jul 13, 2022
Third-party signing undermines SHAKEN
May 31, 2022
Best practices for terminating providers using STIR/SHAKEN
May 23, 2022
New SHAKEN and robocall rules for gateway providers
Mar 30, 2022
Delegate certificate roles and benefits
Mar 7, 2022
The evolution of SHAKEN implementation claims
Feb 21, 2022
Impact of FCC challenges to robocall mitigation filings
Feb 14, 2022
FCC questions some SHAKEN implementation claims
Dec 13, 2021
FCC order accelerates SHAKEN deadline for some small providers
Nov 1, 2021
Canadian SHAKEN token access policy revised
Oct 20, 2021
STI-GA announces support for enhanced SHAKEN functionality
August 16, 2021
Canadian regulator changes service provider SHAKEN qualifications
July 15, 2021
ClearIP delivers the fastest, easiest, most-precise prevention of toll fraud, robocalls and TDoS attacks. It’s ready-to-go with STIR/SHAKEN.
Learn more