https://arstechnica.com/tech-policy/2023/03/fcc-orders-phone-companies-to-block-scam-text-messages/ Skip to main content * Biz & IT * Tech * Science * Policy * Cars * Gaming & Culture * Store * Forums Subscribe [ ] Close Navigate * Store * Subscribe * Videos * Features * Reviews * RSS Feeds * Mobile Site * About Ars * Staff Directory * Contact Us * Advertise with Ars * Reprints Filter by topic * Biz & IT * Tech * Science * Policy * Cars * Gaming & Culture * Store * Forums Settings Front page layout Grid List Site theme light dark Sign in Blocking robotexts -- FCC orders phone companies to block scam text messages First robotext rule requires blocking of texts from invalid and unused numbers. Jon Brodkin - Mar 16, 2023 6:40 pm UTC A man viewing a text message with a Enlarge Getty Images | B4LLS reader comments 51 with Share this story * Share on Facebook * Share on Twitter * Share on Reddit The Federal Communications Commission today finalized rules requiring mobile carriers to block robotext messages that are likely to be illegal. The FCC described the rules as the agency's "first regulations specifically targeting the increasing problem of scam text messages sent to consumers." Carriers will be required to block text messages that come from "invalid, unallocated, or unused numbers." Carriers must also block texts from "numbers that the subscriber to the number has self-identified as never sending text messages, and numbers that government agencies and other well-known entities identify as not used for texting," the FCC said. Carriers will have to establish a point of contact for text senders so the senders can inquire about blocked texts. The FCC already requires similar blocking of voice calls from these types of numbers. The FCC still has a 2-2 partisan deadlock more than two years into Joe Biden's presidency, but the robotext order was approved 4-0. The FCC sought public comment on the rules in September 2022 before finalizing them today. The order will take effect 30 days after it is published in the Federal Register, according to a draft of the order released before the meeting. More robotext rules on the way More robotext rules may be on the way because today's "action also seeks public comment on further proposals to require providers to block texts from entities the FCC has cited as illegal robotexters," the FCC said. For example, the FCC proposes to clarify that Do Not Call Registry protections apply to text messaging. Advertisement The FCC said it's further proposing to close the "lead generator loophole" that "allows companies to use a single consumer consent to deliver robocalls and text messages from multiple--perhaps thousands--of marketers on subjects that may not be what the consumer had in mind." The FCC "will also take further public comment on text authentication measures and other proposals to continue to fight illegal scam robotexts." Complaints about robotexts to the FCC rose from 3,300 to 18,900 per year between 2015 and 2022, the FCC said. Many of these robotexts "promote links to phishing websites or websites that can install malware on a consumer's phone," the FCC said. FCC closes gap in Caller ID authentication The FCC separately voted today to close another gap in its Caller ID authentication rules that target illegal robocalls. The rules already required phone companies to implement the caller ID authentication technologies known as STIR and SHAKEN. But the rules don't apply in every possible scenario, so the FCC has periodically strengthened them. In June 2022, for example, the FCC required carriers with 100,000 or fewer customers to comply a year earlier than these small carriers were originally required to. The FCC said today's vote closes another loophole as follows: The new rules will require intermediate providers that receive unauthenticated IP calls directly from domestic originating providers to use STIR/SHAKEN to authenticate those calls. Although STIR/SHAKEN has been widely implemented under FCC rules, some originating providers are not capable of using the framework. In other cases, unscrupulous originating providers may deliberately fail to authenticate calls. By requiring the next provider in the call path to authenticate those calls, the FCC closes a gap in the caller ID authentication regime and facilitates government and industry efforts to identify and block illegal robocalls. reader comments 51 with Share this story * Share on Facebook * Share on Twitter * Share on Reddit Jon Brodkin Jon is Ars Technica's senior IT reporter, covering the FCC and broadband, telecommunications, tech policy, and more. Email jon.brodkin@arstechnica.com // Twitter @JBrodkin Advertisement Channel Ars Technica - Previous story Next story - Related Stories Today on Ars * Store * Subscribe * About Us * RSS Feeds * View Mobile Site * Contact Us * Staff * Advertise with us * Reprints Newsletter Signup Join the Ars Orbital Transmission mailing list to get weekly updates delivered to your inbox. Sign me up - CNMN Collection WIRED Media Group (c) 2023 Conde Nast. All rights reserved. Use of and/or registration on any portion of this site constitutes acceptance of our User Agreement (updated 1/1/20) and Privacy Policy and Cookie Statement (updated 1/1 /20) and Ars Technica Addendum (effective 8/21/2018). Ars may earn compensation on sales from links on this site. Read our affiliate link policy. Your California Privacy Rights | Do Not Sell My Personal Information The material on this site may not be reproduced, distributed, transmitted, cached or otherwise used, except with the prior written permission of Conde Nast. Ad Choices