Spain SMS Guide: Alias Registration

At a glance

A quick operational read on Spain. Anything marked route-dependent is set by the supplier and operator path your traffic uses. Anything marked law applies whichever supplier you pick.

SMS to mobile: Supported
Number format: +34 followed by nine national digits with no domestic trunk zero; interpersonal mobile numbering uses range 6 and part of range 7
Number validation: Confirm the destination is Spanish, messaging-capable mobile and resolve the current operator before sending
Registered alphanumeric alias: An alphanumeric alias must be registered in the CNMC Alias Register before it is used, and blocking of unregistered or unauthorised aliases begins on 15 September 2026
Alias preservation: Supported on selected routes and normally preserved where the route confirms it; presentation is validated per supplier, not assumed
Domestic long code: Supported on selected local routes; at least one major provider limits its Spanish domestic long code to domestic messaging
International numeric sender: Provider- and route-dependent; preservation must be tested on the exact purchased path
Dedicated short code: Supported through selected programmes
Two-way SMS: Supported on selected inbound-capable numeric or short-code services; it is not a universal property of every Spanish route
Number portability: Available — the original prefix is not proof of the current operator
Concatenation: Supported on selected routes including major provider paths, but test the exact sender, encoding and path
MMS: At least one major provider converts MMS into an SMS containing a URL; other paths may behave differently
SMS to fixed lines: Not supported on standard provider routes — validate line type before sending
M2M numbering: Spain uses a separate M2M range beginning 59 with longer numbering; it is not ordinary consumer mobile A2P
Marketing: LSSI, the GDPR, LOPDGDD and applicable advertising-exclusion duties all apply to promotional SMS
Promotional identification: Commercial electronic communications must identify the advertiser and, for email or equivalent electronic media, begin with the word publicidad under LSSI Article 20 — the AEPD treats SMS as equivalent electronic media
Promotional identification format: We render it as uppercase PUBLICIDAD at the very beginning of the message for clarity and consistent campaign operations; the statute prescribes the word, not the casing
Last reviewed: 1 August 2026

Route-dependent: “Route-dependent” means the behaviour is decided by the supplier and operator path your traffic takes, not by Spanish law. Two providers can behave differently on the same day and a route can change its policy without notice. Alias registration, by contrast, is regulation and applies to every route.

Law, route policy and recommendation

Spain in 2026 is the clearest example of why these three layers must stay apart. The Alias Register is regulation, sender preservation is route behaviour, and the way you evidence permission is largely our own standard. Mixing them is how a Spanish launch gets blocked.

Law / regulation
Law and regulation
Binding obligations from Spanish and EU law: Law 34/2002 (LSSI) Articles 20 to 22 for commercial electronic communications, the GDPR and Organic Law 3/2018 (LOPDGDD) for processing the mobile number, CNMC numbering administration, and the Alias Register created under Order TDF/149/2025 and regulated by CNMC Circular 1/2026 as amended by Circular 2/2026.
Carrier or route policy
Carrier or route policy
Rules applied by operators, aggregators or your provider on the specific path your traffic takes — whether a registered alias is actually preserved, whether a domestic long code is limited to domestic traffic, whether inbound replies exist, concatenation behaviour, MMS conversion and category acceptance. Route-dependent, supplier-specific and subject to change.
Flowstates recommendation
Flowstates operational recommendation
What we ask customers to do because it protects deliverability and keeps you comfortably inside both of the above — attributable permission evidence, brand and purpose in the body, separated templates, branded link domains, a working opt-out even where the sender cannot receive replies, and conservative recipient-local scheduling.

Numbering and networks

The basics your validation layer and templates need to get right before the first send.

Law / regulationNumber format
Spanish national telephone numbers contain nine digits and there is no domestic trunk zero to remove. In E.164 the destination is +34 followed by the nine national digits exactly as dialled domestically.
Law / regulationMobile ranges
Interpersonal mobile numbering uses range 6 and part of range 7, so ordinary consumer mobile destinations begin with 6 or with one of the mobile 7 ranges. Nine digits alone does not prove a number is mobile.
Law / regulationDialling code
Country calling code +34. Mobile country code 214.
Law / regulationM2M numbering
Spain’s machine-to-machine numbering is separate from ordinary consumer mobile numbering: the dedicated range begins with 59 and uses longer numbering. M2M destinations are not ordinary consumer mobile A2P.
Flowstates recommendationM2M handling
Validate M2M destinations out of consumer A2P campaigns unless the contracted use case and the selected route expressly support them.
Law / regulationNumber portability
Mobile number portability is available in Spain, so subscribers keep their number when they change operator. The original prefix is therefore not evidence of the current network.
Flowstates recommendationValidation before sending
Run live validation of Spanish jurisdiction, line type and messaging capability, and current operator. Route, reporting and per-operator quality analysis all depend on the current operator rather than the original range.
Carrier or route policyNetworks to plan for
The primary carrier and brand paths relevant to operational testing are Movistar, the MASORANGE group brands, Vodafone and DIGI, plus representative MVNO-hosted destinations. We publish no market-share claims and we do not assume every supplier has equal direct coverage.
Carrier or route policyShort codes
Spanish short codes are available through selected programmes. Availability, reply behaviour and programme eligibility are confirmed privately for the specific traffic, never assumed from a coverage table.

E.164 examples

+34 6XX XXX XXX / +34 7XX XXX XXX

Country code 34, then the nine national digits with no trunk zero. These are masked illustrative patterns for the mobile 6 and mobile 7 ranges — not real subscriber numbers, and not a substitute for live line-type validation.

SenderID options

Spain changed materially in 2026 and several provider country tables have not caught up. A registered alphanumeric alias is normally the best one-way branded option where the selected route preserves it, but registration in the CNMC Alias Register is now a legal prerequisite rather than an optional provider step. Preservation, operator support and route availability remain route policy. Provider documentation also disagrees: one major provider reports two-way support and preserved domestic and international long codes while limiting its Spanish domestic long code to domestic messages, and others describe different inbound behaviour and different numeric-sender handling. Treat replies and numeric preservation as route-dependent and validate the exact purchased service.

Carrier or route policy

This whole comparison — best for, what the recipient sees and replies — describes carrier and provider route behaviour and programme availability on current A2P paths into Spain. The one exception is regulatory: an alphanumeric alias must be registered before it is used in Spain. Registration status is handled privately during route assessment and is deliberately not a column in this table.

Registered alphanumeric alias

Best for: One-way branded OTP, transactional, service and permissioned marketing traffic
What the recipient sees: The registered brand or alias where the selected route preserves it
Replies: No

Spanish domestic long code

Best for: Local support, conversational and selected transactional programmes using a Spanish number
What the recipient sees: The Spanish +34 number assigned to the service
Replies: Supported only when inbound SMS is explicitly configured

International numeric sender

Best for: Selected transactional traffic where the supplier confirms support and preservation
What the recipient sees: The submitted international number on a validated route, otherwise a route-assigned or replaced sender
Replies: Only where an inbound-capable service is configured and tested

Dedicated short code

Best for: Selected high-scale branded programmes
What the recipient sees: The approved short code
Replies: Route- and programme-dependent

SenderID options
Option	Best for	What the recipient sees	Replies
Registered alphanumeric alias	One-way branded OTP, transactional, service and permissioned marketing traffic	The registered brand or alias where the selected route preserves it	No
Spanish domestic long code	Local support, conversational and selected transactional programmes using a Spanish number	The Spanish +34 number assigned to the service	Supported only when inbound SMS is explicitly configured
International numeric sender	Selected transactional traffic where the supplier confirms support and preservation	The submitted international number on a validated route, otherwise a route-assigned or replaced sender	Only where an inbound-capable service is configured and tested
Dedicated short code	Selected high-scale branded programmes	The approved short code	Route- and programme-dependent

Flowstates recommendation: put a recognisable brand and the purpose of the message in the body even when the visible sender is expected to remain stable. Do not rely on replies unless inbound messaging is expressly configured and tested on the purchased service. Confirm the live sender and route with us privately before you build against either.

What changes by traffic type

Spain is not one rulebook. The same destination behaves differently depending on the category you send, the sender you use and the route it takes.

OTP / authentication

Suitable on a registered and preserved alias route, or on a validated numeric sender selected for authentication.

Flowstates recommendation
Keep the copy purely transactional and concise, ideally inside a single segment.
Flowstates recommendation
Identify the brand and the purpose, and include an appropriate code-expiry cue.
Flowstates recommendation
No promotional content in OTP templates.
Flowstates recommendation
Use a branded domain only where a link is genuinely necessary.
Flowstates recommendation
Document the user action or context that caused the OTP. That context is not permission for unrelated promotion.
Flowstates recommendation
Monitor delivery, latency, completed-verification conversion and per-route and per-operator performance.
Flowstates recommendation
Configure carrier-grade failover, and make sure every fallback alias or sender is itself valid for Spain and for the traffic being sent.
Carrier or route policy
Do not depend on replies unless an inbound path is explicitly configured on the purchased route.
Law / regulation
A fallback sender is not exempt from alias registration. Any alphanumeric identifier used towards Spanish numbers must itself be registered before use.

Transactional / service

Suitable for alerts, confirmations, account updates and expected service communications.

Flowstates recommendation
Keep the content within the purpose for which the number was provided.
Flowstates recommendation
Identify the brand and the purpose in the message body, and use branded links.
Flowstates recommendation
Test concatenation, Unicode behaviour and numeric-sender presentation on the exact path before relying on any of them.
Flowstates recommendation
Maintain an appropriate revocation and suppression process for recurring service programmes.
Carrier or route policy
Enable replies and HELP-style handling only on an explicitly configured inbound service.
Law / regulation
A service opt-in or a service template does not create permission for promotional messaging. The category follows the content and purpose, not the template name.

Marketing / promotional

Prior permission by default, identification with the word publicidad, a free way to stop and prompt suppression.

Law / regulation
Under LSSI Article 21, unsolicited promotional or commercial electronic communications are prohibited unless previously requested or expressly authorised by the recipient.
Law / regulation
LSSI Article 21 contains a prior-contract exception where the contact details were lawfully obtained in the course of a previous contractual relationship and the same business advertises its own products or services similar to those originally contracted.
Law / regulation
Under LSSI Article 20 the commercial nature of the message must be clearly identifiable, the person or entity on whose behalf it is sent must be identified, and for email or equivalent electronic media the message must begin with the word publicidad. The AEPD expressly treats SMS as an equivalent electronic medium.
Flowstates recommendation
Render that word as uppercase PUBLICIDAD at the very start of the message. The statute prescribes the word rather than its casing, but uppercase is unambiguous for recipients and easier to operate consistently across campaigns.
Law / regulation
A simple and free means of objecting or withdrawing must be available both at the point of data collection and in every promotional communication.
Law / regulation
Consent must be an affirmative act. Silence, inactivity or pre-ticked boxes are not valid consent.
Law / regulation
Under GDPR Article 21 the recipient can object to direct marketing at any time, and processing for that purpose must then stop.
Law / regulation
LOPDGDD Article 23 requires the applicable advertising-exclusion systems to be consulted and registered objectors excluded, except where the person has given valid consent to that specific sender. Lista Robinson and Lista Stop Publicidad are current AEPD-listed examples rather than a permanently fixed list.
Flowstates recommendation
Our launch standard is prior affirmative, attributable, purpose-specific and SMS-channel-specific permission for promotional SMS, unless qualified Spanish counsel documents another lawful basis or exception and the selected route accepts the traffic.
Flowstates recommendation
Where an alphanumeric alias cannot receive replies, provide a simple free alternative such as a clear link, a designated email address or a freephone mechanism.
Flowstates recommendation
Support natural Spanish opt-out expressions such as BAJA, SALIR, CANCELAR, STOP and NO. No single keyword is the exclusive statutory method, so recognise the intent.
Flowstates recommendation
Do not use bought or rented lists.
Flowstates recommendation
Schedule promotional traffic between 09:00 and 20:00 recipient-local time as our conservative default, with any stricter sector or customer rule taking precedence. This is a recommendation, not a statutory SMS window.
Carrier or route policy
Use a registered alias or a validated numeric programme and a branded domain. Category acceptance remains route-specific and is confirmed privately.

Spain's LSSI, GDPR and advertising-exclusion rules

Spain separates three questions that are routinely confused: may you use this channel for advertising at all, may you process the personal data behind it, and may this sender identity be used towards Spanish numbers. LSSI answers the first, the GDPR and LOPDGDD answer the second, and the CNMC Alias Register answers the third. You need all three.

Law / regulation
LSSI Article 20: commercial communications sent by electronic means must be clearly identifiable as such, and must identify the natural or legal person on whose behalf they are sent.
Law / regulation
LSSI Article 20 requires promotional communications sent by email or equivalent electronic communication media to begin with the word publicidad, and the AEPD identifies SMS as an equivalent medium for this purpose. The statute prescribes the word, not a particular casing.
Flowstates recommendation
We render it as uppercase PUBLICIDAD at the very beginning of the message body for clarity to the recipient and consistent campaign operations, treating casing as our own standard rather than a statutory requirement.
Law / regulation
LSSI Article 21 prohibits sending promotional or commercial communications by email or equivalent electronic media that were not previously requested or expressly authorised by the recipient.
Law / regulation
The Article 21 exception is narrow: it applies where a previous contractual relationship exists, the contact details were lawfully obtained in that context, and the sender advertises its own products or services similar to those originally contracted.
Law / regulation
A simple and free means of objecting to the processing of data for promotional purposes must be offered both when the data is collected and in each commercial communication.
Law / regulation
LSSI permission analysis is a separate question from sender or route registration. Neither one substitutes for the other.
Law / regulation
Where consent is the lawful basis under the GDPR, it must be an unambiguous affirmative act. Silence, inactivity and pre-ticked boxes do not amount to consent.
Law / regulation
The GDPR requires purpose limitation, transparency, data minimisation, accuracy, security and sensible retention for the mobile number and every related record.
Law / regulation
Under GDPR Article 21 the recipient can object to processing for direct-marketing purposes at any time, and processing for that purpose must stop after the objection.
Law / regulation
LOPDGDD Article 23 governs advertising-exclusion systems: where such systems apply, they must be consulted and registered objectors excluded from the campaign, except where the person concerned has given valid consent to that specific sender.
Flowstates recommendation
Keep evidence of the purpose, source, notice shown, consent or documented exception, exclusion-system check, objection and suppression for as long as you may need to demonstrate compliance.
Law / regulation
The CNMC Alias Register is live. Alphanumeric identifiers used as senders in SMS, MMS or RCS towards Spanish numbers may not be used until they are effectively registered, and the registered alias must be linked to its legitimate holder and to the authorised origin provider or providers.
Law / regulation
The obligations to block unregistered aliases, unauthorised aliases, aliases sent from unregistered providers and foreign-company aliases not registered in Spain take effect on 15 September 2026, subject to the roaming exception set out in the official rule. That date follows the extension made by Order TDF/558/2026 and reflected in CNMC Circular 2/2026.
Law / regulation
Companies established outside Spain must also comply when they send to Spanish numbers using an alias, subject to the same official roaming exception.
Law / regulation
Registration is not consent and consent is not registration. Passing the register does not make an unpermitted promotional SMS lawful, and holding permission does not make an unregistered alias usable.
Flowstates recommendation
We do not publish the documentary or procedural detail of alias registration. We confirm the live registration and route position with you privately during onboarding.
Flowstates recommendation
The AEPD telephone-call rules and their time windows are scoped to calls, so we do not apply those call-specific windows to SMS without a separate legal basis for SMS. This is our reading of the scope of those rules, not a statutory statement about text messaging.
Flowstates recommendation
Our 09:00 to 20:00 recipient-local sending window for promotional SMS is a Flowstates recommendation designed to be defensible and low-complaint, not a statutory SMS window.

Operational compliance checklist

The controls we expect to see in place before Spanish traffic goes live, and the records we expect you to be able to produce afterwards.

Law / regulation
Store destinations as +34 plus nine national digits, with no trunk zero added or removed.
Flowstates recommendation
Validate Spanish jurisdiction, line type and messaging capability, and resolve the current operator before sending.
Flowstates recommendation
Validate ordinary mobile 6 and 7 ranges separately from M2M destinations in the 59 range.
Carrier or route policy
Select the sender deliberately: registered alias, validated Spanish long code, supported international numeric route or approved short code.
Law / regulation
Any alias used towards Spanish numbers must be effectively registered and linked to an authorised origin provider, and the blocking obligations begin on 15 September 2026.
Flowstates recommendation
Confirm that registration and provider association are in place before launch, and plan fallback senders accordingly.
Flowstates recommendation
Keep the alias or brand, the website, the use case, the opt-in journey, the sample templates and the live traffic materially aligned with each other.
Flowstates recommendation
Keep OTP, service and marketing purposes, templates and permission records separate.
Flowstates recommendation
Retain the recipient, timestamp, source, notice or disclosure version, purpose, channel and the evidence of the permission or reviewed exception relied on.
Law / regulation
For marketing, begin the message with the word publicidad and identify the brand or entity on whose behalf it is sent.
Flowstates recommendation
Render that word as uppercase PUBLICIDAD at the very start of the message for clarity and consistent campaign operations.
Law / regulation
Provide a simple and free opt-out in every promotional message, including a workable alternative where the sender cannot receive replies.
Flowstates recommendation
Recognise BAJA, SALIR, CANCELAR, STOP, NO and reasonable natural-language equivalents as opt-out requests.
Flowstates recommendation
Suppress immediately across every sending system, including separate campaign or CRM tooling.
Law / regulation
Apply GDPR objection handling and, where applicable, the LOPDGDD Article 23 advertising-exclusion checks before each promotional send.
Flowstates recommendation
Do not use bought or rented lists.
Flowstates recommendation
Use 09:00 to 20:00 recipient-local time as the default promotional window, with any stricter sector or customer rule taking precedence.
Flowstates recommendation
Use branded short domains rather than public or shared shorteners.
Carrier or route policy
Test the Movistar, MASORANGE group, Vodafone and DIGI paths plus representative MVNO-hosted destinations before you scale.
Carrier or route policy
Test MMS handling and any SMS conversion, Unicode, concatenation, sender preservation, inbound replies and opt-out handling on the exact purchased route.
Flowstates recommendation
Keep template, notice, permission or exception, advertising-exclusion, alias-registration, route-approval, opt-out and suppression evidence.
Carrier or route policy
Confirm category acceptance privately with us for the specific traffic rather than assuming a coverage table applies to your use case.

Encoding and delivery

Segment maths, Spanish-language pitfalls and what to test on the live route before launch.

GSM-7 single segment: Normally 160 characters
GSM-7 concatenated: Normally 153 characters per segment
Unicode / UCS-2 single segment: Normally 70 characters
Unicode / UCS-2 concatenated: Normally 67 characters per segment
E.164 examples: +34 6XX XXX XXX / +34 7XX XXX XXX

Flowstates recommendation
Spanish copy does not automatically force UCS-2. ñ, ¿, ¡ and é are available in the GSM-7 basic alphabet, but characters such as á, í, ó, ú, smart quotation marks and emoji can force UCS-2 unless they are replaced or transliterated. Test the actual encoded template and its segment count rather than trusting a character count in a document.
Flowstates recommendation
Test the final Spanish and English copy end to end on the actual sender type and on the operator paths you intend to use.
Flowstates recommendation
Keep OTP messages within a single segment wherever practical. Do not treat a provider’s maximum segment count as a copy target.
Law / regulation
Spanish national numbers have nine digits and no trunk zero, so do not strip or add a leading zero when normalising to E.164.
Law / regulation
Portability is active, so the original prefix is not proof of the current operator.
Flowstates recommendation
Run a live current-operator lookup for routing and per-operator quality analysis rather than inferring from the range.
Carrier or route policy
MMS conversion, media limits and sender preservation are route policy. At least one major provider converts MMS into an SMS containing a URL, and other paths may differ.

A country guide is only useful when the route follows it.

Country rules only help if the route your traffic actually takes respects them. That is the part we operate.

Per-country and per-category routing
Multi-vendor routing decided per country and per traffic category, so OTP, service and marketing traffic into Spain do not share one compromise route.
SenderID management
We manage sender presentation per route and per category, including registered Spanish aliases and validated numeric senders, and we check what the recipient actually sees before launch.
Carrier-grade failover
Automatic failover between vendors, with fallback senders that are themselves valid for Spain rather than a route that quietly breaks your sender.
Per-route visibility
Delivery, latency and OTP-conversion visibility per route, so a quality change on one Spanish operator path is visible while it is still small.
24/7 vendor escalation
We chase the vendor. Escalation runs around the clock rather than waiting for a support queue in another time zone.
BYOV / BYOG
Bring your own vendors or gateway and keep your commercial relationships while we operate the routing, sender policy and monitoring.
Branded short links
Branded short domains instead of public shorteners, so Spanish recipients see a link that matches the sender they trust.

Developer docs Branded short links

What we need to validate your Spain route

What we need from you so we can validate senders, alias position, routes and category acceptance on the live Spanish path before you launch.

Company or legal entity and website
Customer-facing brand or alias
Traffic category and use case
English and Spanish sample templates for each distinct use case
Expected monthly volume and peak sending rate
Preferred sender type
Existing Spain sender inventory and provider, at a high level
Alias-registration status, at a high level only
Opt-in journey, supporting evidence and the exact disclosure wording
Privacy notice and terms URLs
Marketing basis or exception relied on, and the owner of the legal review
Advertising-exclusion check and its owner
Internal objection, opt-out and suppression process, and its owner
Link domains you intend to use
Whether you need replies or two-way messaging
MMS and multi-segment requirements
How numbers are collected, normalised and validated, including M2M handling
Target launch date

Validate my Spain route Book a messaging review

Frequently asked questions about SMS in Spain

Can I send SMS to mobile numbers in Spain?

A quick operational read on Spain. Anything marked route-dependent is set by the supplier and operator path your traffic uses. Anything marked law applies whichever supplier you pick. SMS to mobile: Supported. Number format: +34 followed by nine national digits with no domestic trunk zero; interpersonal mobile numbering uses range 6 and part of range 7. Number validation: Confirm the destination is Spanish, messaging-capable mobile and resolve the current operator before sending. Registered alphanumeric alias: An alphanumeric alias must be registered in the CNMC Alias Register before it is used, and blocking of unregistered or unauthorised aliases begins on 15 September 2026.

Which sender ID options work for SMS in Spain?

Spain changed materially in 2026 and several provider country tables have not caught up. Registered alphanumeric alias — Best for: One-way branded OTP, transactional, service and permissioned marketing traffic. Spanish domestic long code — Best for: Local support, conversational and selected transactional programmes using a Spanish number. International numeric sender — Best for: Selected transactional traffic where the supplier confirms support and preservation. Dedicated short code — Best for: Selected high-scale branded programmes.

What are the consent and opt-out requirements for SMS in Spain?

Spain separates three questions that are routinely confused: may you use this channel for advertising at all, may you process the personal data behind it, and may this sender identity be used towards Spanish numbers. LSSI Article 20: commercial communications sent by electronic means must be clearly identifiable as such, and must identify the natural or legal person on whose behalf they are sent. LSSI Article 20 requires promotional communications sent by email or equivalent electronic communication media to begin with the word publicidad, and the AEPD identifies SMS as an equivalent medium for this purpose. The statute prescribes the word, not a particular casing. We render it as uppercase PUBLICIDAD at the very beginning of the message body for clarity to the recipient and consistent campaign operations, treating casing as our own standard rather than a statutory requirement.

How many characters fit in an SMS to Spain?

Segment maths, Spanish-language pitfalls and what to test on the live route before launch. GSM-7 single segment: Normally 160 characters. GSM-7 concatenated: Normally 153 characters per segment. Unicode / UCS-2 single segment: Normally 70 characters. Unicode / UCS-2 concatenated: Normally 67 characters per segment.

Sources and change control

Official Spanish and EU sources control the law, the Alias Register, numbering and data-protection wording. Provider sources describe only their own current route. Where a provider page conflicts with the official position, we follow the official source and say so.

Provider route policy
Twilio — Spain SMS guidelines
Describes its own Spanish route: alphanumeric, domestic and international long code and short code support with preservation, two-way messaging, concatenation with sender and encoding qualifications, MMS converted to SMS with a URL and no landline SMS. Its country table still frames dynamic alphanumeric senders as needing no preregistration, which is no longer a safe summary now that the CNMC Alias Register is live.
Regulator
CNMC — Registro de alias
The official Alias Register: scope, who must register an alias, association with the legitimate holder and the authorised origin providers, and the current implementation position.
Regulation
BOE — CNMC Circular 2/2026 amending Circular 1/2026
Confirms the extension of the start of the blocking obligations to 15 September 2026 under Order TDF/558/2026 and adjusts the related reporting deadlines.
Regulation
BOE — CNMC Circular 1/2026 regulating the Alias Register
Official reference BOE-A-2026-7043. The circular that regulates registration, modification and cancellation of aliases in the register. Read together with Circular 2/2026.
Regulation
BOE — Order TDF/149/2025 and its amendment Order TDF/558/2026
The anti-spoofing order that creates the messaging identification and blocking measures, and the June 2026 amendment that moved the start of the blocking obligations to 15 September 2026.
Statute
BOE — Law 34/2002 (LSSI), Articles 20 to 22
Identification of commercial communications and the PUBLICIDAD requirement for email and equivalent electronic media, the prior request or express authorisation rule with its previous-contract exception, and the free objection and withdrawal duty.
Regulator
AEPD — Publicidad no deseada
Spanish data-protection authority guidance on unwanted advertising, including the treatment of SMS as an electronic medium equivalent to email and the interaction between LSSI permission and data-protection duties.
Statute
BOE — Organic Law 3/2018 (LOPDGDD), Article 23
Advertising-exclusion systems: the duty to consult applicable systems and exclude registered objectors, with the exception where the person has consented to that specific sender.
Regulation
EUR-Lex — GDPR Article 21
The right to object to processing for direct-marketing purposes at any time, and the requirement to stop that processing after an objection.
Official numbering
CNMC — national numbering plan resources
Spanish numbering administration: nine-digit national numbers with no trunk zero, mobile ranges 6 and 7, and the separate M2M range beginning 59.
Official numbering
CNMC — mobile number portability and current-operator lookup
Confirms active mobile portability and provides the official lookup, which is why the original prefix cannot be used to infer the current operator.
Official market data
CNMC — telecoms market and operator data
Official market data used only to confirm which operator and brand paths to plan for in route testing. We publish no market-share claims.
Provider route policy
Vonage — Spain SMS features and restrictions
Cited only to show that provider descriptions of Spanish sender and inbound behaviour disagree with each other. Its own route only.
Provider route policy
Plivo — Spain SMS coverage
Cited only to show provider disagreement on sender presentation, two-way capability and concatenation behaviour into Spain. Its own route only.

Change log

1 August 2026 — Initial publication; corrected the older dynamic-sender summary for Spain, incorporated the live CNMC Alias Register and 15 September 2026 blocking date, and separated LSSI/GDPR duties from live route policy.

Last reviewed 1 August 2026

Disclaimer

This page is operational guidance, not legal advice. Requirements vary by law, message purpose, sender, alias registration, provider, carrier route, recipient context and customer setup, and they change. Flowstates confirms the live route with you during onboarding, and you should take your own Spanish legal advice on marketing and data-protection obligations.

Spain SMS guide