CNMC sets 15 September deadline to register messaging aliases

The available documentation supports a specific telecommunications news story in Spain: in September 2026, the National Commission on Markets and Competition (CNMC) urged companies to register their aliases and respond to the regulator’s communications by the 15th. The warning concerned aliases used in SMS, MMS and RCS messages to communicate with customers. According to the CNMC announcement, failing to deal with this process could lead to interruptions to those communications. The deadline has now passed; it must therefore not be presented as a future date or as an obligation newly announced today.

The date also matters when describing the scope of the news accurately. The report does not claim that communications were interrupted, that every company failed to comply, or that users must now complete a procedure. The cited announcement addresses companies and links its request to registration and responses to the regulator’s communications. Without subsequent data on compliance or incidents, the risk communicated is not the same as a confirmed outcome. The information establishes the deadline and its purpose, but does not quantify consequences.

There is also a primary regulatory reference: on 12 September 2026, Spain’s Official State Gazette (Boletín Oficial del Estado, BOE) published CNMC Circular 3/2026, dated 8 September. The text states that it amends Circular 1/2026 of 18 March, which regulates the Alias Register. This connection places the September request within a specific regulatory framework, rather than treating it as an isolated warning or a general recommendation about messaging.

The BOE explains that Circular 3/2026 amends the earlier rule and cites Order TDF/149/2025 as background. That order concerns measures against identity-impersonation scams using fraudulent calls and messages, as well as the identification of numbers used for customer service and unsolicited commercial calls. This provides context for the aim of protecting against abuse, but it does not justify attributing every measure in that order to the new circular. To establish the precise legal scope, readers must consult the full text, identify the amended articles and distinguish them from rules cited as background.

The CNMC communication refers to companies that use aliases in SMS, MMS or RCS to contact customers. In this context, an alias is the alphanumeric identifier that may appear as the sender of certain messages instead of a conventional telephone number. This explanation helps clarify the issue, but the material provided does not specify which particular companies were required to act, what technical requirements applied in each case, or what exceptions may have existed. An institutional request directed at companies should not be turned into a universal rule for every organisation that sends messages.

For users, the announcement does not by itself establish a complaints procedure, a way to check whether a company completed registration, or instructions for blocking messages. Someone who receives a suspicious message may have good reason to act cautiously, but that general advice should not be confused with a specific instruction arising from the circular. The information established here concerns alias registration and communications between the CNMC and companies, not a consumer security guide.

As of the date of this article, 30 September 2026, the 15 September deadline has passed. The announcement supports reporting the cut-off date and the possible interruption risk communicated by the CNMC, but it does not establish what happened afterwards. The cited sources provide no tally of companies that completed registration, no list of suspended aliases and no figures for messages affected. Presenting any of those outcomes as fact would go beyond the evidence.

The CNMC’s request must also be distinguished from the rule published in the BOE. The former gives a date and describes a possible consequence as stated by the regulator; the circular is the legal document amending the previous regulation. When explaining an obligation precisely, the full official text carries more weight than a headline or summary. If an information notice and the rule differ, the final account should describe the rule and attribute to the notice only what it actually announces.

A robust update should check whether the CNMC issued instructions after 15 September, whether the register became operational and whether any interruption notices were published. It would also be useful to compare the circular with Circular 1/2026 to identify which articles changed and when the amendments took effect. The documentation reviewed establishes that a regulatory amendment and a time-limited request were made, but it does not, by itself, provide this subsequent follow-up.

The search materials provided include general CNMC and Usuarios Teleco portal pages, along with news and documentation on other telecommunications issues. Those general pages are no substitute for checking a dated announcement; in this case, the specific evidence comes from the alias notice and the BOE publication. The editorial conclusion is limited: there is a documented regulatory development, but these sources are not sufficient to claim that the expired deadline caused interruptions or to measure their extent. Distinguishing an announced risk from an observed outcome is essential to reporting without exaggeration.