URL Shortener for India: TRAI, 2s.ms and Branded Short Links Guide

SMS marketing in India operates under one of the most specific regulatory frameworks for commercial messaging anywhere in the world. TRAI — the Telecom Regulatory Authority of India — introduced the Distributed Ledger Technology (DLT) platform requirement for commercial SMS. The regulations require commercial SMS senders to register on the DLT platform, register their sender IDs (headers), pre-register message templates, and — for SMS messages containing URLs — use URL formats that include the registered header as a static prefix. Businesses using generic URL shorteners whose domain and link format do not comply with this requirement face SMS delivery failures: Indian telecom carriers block non-compliant shortened links from delivery. This guide covers the complete operational picture: how TRAI's URL requirements work in practice, how Cuttly's 2s.ms domain and Tracking Header feature address them, how branded custom domains with headers provide a superior alternative for established businesses, the exact setup process, API integration for automated SMS campaigns, plan limits, and how to scale TRAI-compliant link management across multiple brands and campaigns.

---

TRAI DLT Framework: What It Is and Why It Affects URL Shorteners

The Telecom Regulatory Authority of India's DLT (Distributed Ledger Technology) platform requirement for commercial SMS was introduced to combat SMS spam and fraud at the infrastructure level. The framework requires every commercial SMS sender in India to: register their entity on the DLT platform, register their sender headers (the identifier that appears as the SMS "from" name), pre-register all message templates used in commercial SMS, and ensure that all links included in SMS messages conform to specific format requirements.

For URL shorteners specifically, the DLT framework requires that shortened URLs in commercial SMS messages contain a registered, static prefix (the "header" in Cuttly's terminology) that was pre-registered on the DLT platform. The static part of the URL — the domain and the header prefix — must match the registered URL on the DLT system. Only the dynamic part of the URL (the short link alias, typically 9 characters in the 2s.ms format) is variable.

The practical consequence: a standard short link in the format https://cutt.ly/aBcDeF does not comply with the DLT requirement because the entire URL after the domain is dynamic (the alias changes per link). The telecom carrier's DLT validation system cannot match a dynamically varying alias against a pre-registered static URL pattern. Links in this format are blocked from delivery by Indian carriers.

The TRAI-compliant URL format: https://domain/HEADER/alias, where domain/HEADER/ is the static part registered on DLT (e.g., 2s.ms/ABCDEF/ or yourbrnd.link/ABCDEF/) and alias is the dynamic short link alias that varies per link. The static prefix is validated against the DLT registration; the dynamic alias passes through once the static prefix is verified.

Important compliance note: Cuttly provides the URL shortening infrastructure and the Tracking Header feature. It is the user's responsibility to register their entity, sender header, and static URL on the DLT platform. Cuttly does not interact with the DLT platform and cannot guarantee regulatory compliance on the sender's behalf. Businesses sending commercial SMS in India must confirm their DLT compliance requirements with their SMS service provider and legal advisors.

The URL Format Requirement: Why Generic Short Links Fail

To understand exactly why standard URL shortener links fail DLT validation, it helps to understand what the DLT validation process checks. When a commercial SMS message is processed by an Indian telecom carrier, the carrier's DLT system checks the message against the sender's registered templates and verifies that any URLs in the message match the registered URL patterns.

A registered URL pattern in the DLT system looks like: https://2s.ms/ABCDEF/ — where ABCDEF is the sender's registered 6-character header. The DLT system checks that any shortened URL in an SMS from this sender starts with this exact static prefix. Only the characters after the final slash are allowed to be dynamic.

A standard short link — https://cutt.ly/aBcDeF — does not match the required format because: (1) there is no registered static header between the domain and the alias, and (2) the alias itself is the entire variable part without a static prefix. The carrier's DLT validation sees an unknown URL pattern and blocks the message.

The same problem applies to all URL shortener platforms that do not support the header/alias format. Any link that is simply domain/alias without a registered static header prefix will fail DLT validation for commercial SMS in India, regardless of which URL shortener platform generates it.

Two Compliant Approaches: 2s.ms vs Branded Custom Domain with Header

Cuttly supports two approaches for TRAI-compliant SMS links in India. Both produce the required domain/HEADER/alias URL format. The choice between them depends on whether the sender has their own branded domain.

For businesses that do not yet have a branded short domain, the 2s.ms approach provides immediate TRAI-compliant SMS link capability at the cost of using a public domain rather than their own brand. For established businesses with their own domain infrastructure, the branded custom domain with header provides the same TRAI compliance while also presenting the brand's own domain in every SMS link — improving recipient trust and click rates.

The 2s.ms Domain: How It Works

The 2s.ms domain is a public domain developed and maintained by Cuttly specifically for TRAI-compliant SMS in India. It is available to all Cuttly users on the Single plan and above. The domain is not a generic URL shortener — it is exclusively for SMS link shortening with TRAI headers.

The Character Budget

The 2s.ms format has a specific character constraint: https://2s.ms/HEADER/ uses exactly 21 characters. Since the total shortened URL must fit within the overall SMS message character limit alongside the message content, and the HEADER is always 6 characters, the alias portion has 9 characters available.

This 9-character alias limit is tight but workable for most SMS campaigns — a 9-character alphanumeric alias provides over 100 billion unique combinations, more than sufficient for any campaign volume. The alias can be a custom alias of up to 9 characters (set at link creation) or an auto-generated alias that Cuttly creates within the 9-character limit.

Full 2s.ms link example: https://2s.ms/ABCDEF/summr26 — where ABCDEF is the sender's registered DLT header and summr26 (7 characters) is the short alias for the summer 2026 campaign landing page. Total URL length: 28 characters.

Step-by-Step: Adding the 2s.ms Domain to Your Cuttly Account

Prerequisites: you must have a Single plan subscription or above, and you must have a 6-character header registered on the DLT platform with your SMS service provider.

Step 1: Log in to your Cuttly account. Navigate to Edit Account.

Step 2: In the Custom Domain section, click Add New Domain.

Step 3: Enter the domain in the exact format: 2s.ms/HEADER/ — replacing HEADER with your 6-character DLT-registered header identifier. For example: 2s.ms/ABCDEF/. Include the trailing slash.

Step 4: Accept the declaration of responsibility for TRAI compliance. This declaration confirms that you are responsible for DLT registration and that Cuttly is providing only the URL shortening infrastructure.

Step 5: Click Add New Domain. Unlike regular custom domains, no DNS configuration is required for 2s.ms — the domain configures itself automatically. Wait for Cuttly to approve the domain (typically within a few hours).

Step 6: Once approved, the 2s.ms/HEADER/ domain is available in the domain selector when creating short links. All links created under this domain will follow the 2s.ms/HEADER/alias format.

Adding multiple headers: you can add multiple 2s.ms/HEADER/ instances to the same account for different headers — each header requires a separate domain entry. Plan limits apply: Single plan allows up to 5 headers on 2s.ms; Team plan up to 10; Enterprise up to 99.

Branded Custom Domains with Tracking Headers: The Professional Approach

For businesses with an established brand, a branded custom domain with a Tracking Header provides the same TRAI compliance as 2s.ms with the additional benefit of the brand's own domain in every SMS link. A recipient in India who receives an SMS from a major bank, e-commerce platform, or FMCG brand with a link on the brand's own domain — yourbrnd.link/ABCDEF/campaign — has a significantly different trust experience from receiving a link on a public domain.

The trust dimension is particularly relevant in the Indian SMS marketing context, where SMS phishing (smishing) is a documented fraud vector. A link on the brand's own registered domain — a domain consumers can verify belongs to the brand — is unambiguously legitimate. The DLT registration requirement reinforces this: the brand's registered header on DLT is another layer of legitimacy verification. Branded domain + registered header together create a strong, verifiable trust signal in SMS communications.

The resulting link format: https://yourbrnd.link/ABCDEF/alias — where yourbrnd.link is the brand's registered branded domain, ABCDEF is the 6-character DLT-registered header, and alias is the dynamic short link alias.

The total character usage: the branded domain length + 1 (slash) + 6 (header) + 1 (slash) + alias length. For a branded domain of 15 characters (yourbrnd.link = 13 characters + https:// = 21 total): 21 + 7 (header + slash) + alias. A 6-character alias produces a 35-character total URL — workable within SMS character budget constraints.

Step-by-Step: Setting Up a Tracking Header for a Custom Domain

Prerequisites: you must have a Single plan subscription, a branded domain already added and verified in Cuttly (follow the branded domain setup process described in the branded short link setup guide), and a 6-character header registered on the DLT platform.

Step 1: Log in to Cuttly and go to Edit Account.

Step 2: In the Custom Domain section, locate your verified branded domain. Click Tracking HEADER Settings for that domain.

Step 3: The Tracking Header settings panel opens. Click to add a new header and enter your 6-character DLT-registered header identifier. Save by clicking SAVE.

Step 4: The header appears in the list for that domain. You can add multiple headers (within plan limits: 1 on Single, 5 on Team, 15 on Enterprise). Each header must be separately registered on the DLT platform.

Step 5: When creating short links, select the branded domain and the desired header from the dropdown. All links created with this configuration will follow the yourbrnd.link/HEADER/alias format.

TRAI Header Limits by Cuttly Plan

Most businesses sending SMS campaigns in India with a single brand and a handful of campaigns will find the Single plan's header limits sufficient. Businesses with multiple brands, multiple product lines, or high-frequency campaign rotation requiring more than one active header simultaneously should upgrade to Team or Enterprise.

The header limit applies to how many distinct registered headers can be configured per domain — not to how many links can be created per header. Once a header is configured, you can create an unlimited number of short links under that header (subject to the account's monthly link creation limit).

API Integration for Automated TRAI-Compliant Link Creation

For businesses that generate SMS campaign links programmatically — e-commerce platforms sending per-order notification links, banks generating per-customer personalised OTP links, logistics companies creating per-shipment tracking links — API-based automated link creation with the correct header format is essential.

In the Cuttly Regular API, the parameters for creating a TRAI-compliant link are:

• domain=1 — specifies that a custom domain should be used
• header=1 — specifies that the Tracking Header should be applied
• short — the destination URL
• name — the custom alias (up to 9 characters for 2s.ms, more for branded domains)

Full API request example for creating a 2s.ms TRAI-compliant link:

const params = new URLSearchParams({
  key: API_KEY,
  short: destinationUrl,
  domain: '1',      // use configured custom domain/2s.ms
  header: '1',      // apply the registered Tracking Header
  name: 'summr26'  // custom alias (max 9 chars for 2s.ms)
});
 
const response = await fetch(
  `https://cutt.ly/api/api.php?${params.toString()}`
);
const data = await response.json();
// data.url.shortLink: https://2s.ms/ABCDEF/summr26

In the Team API, the header parameter is hheader={your_HEADER}. Use this when operating through a team workspace with the Team API key rather than the personal Regular API key:

// Team API — TRAI header parameter
const params = new URLSearchParams({
  key: TEAM_API_KEY,
  short: destinationUrl,
  userDomain: 'yourbrnd.link',
  hheader: 'ABCDEF',  // your registered 6-char header
  name: 'alias'
});

For the full API parameter reference and endpoint specifications, see the official Cuttly API documentation at cutt.ly/api-documentation and the API developer guide. The TRAI header parameters are documented in the API reference alongside the standard shortening parameters.

Team Dashboard: Managing Headers Across Multiple Brands

Large enterprises operating multiple brands in India — a conglomerate with FMCG, banking, insurance, and telecom divisions, each with their own DLT registrations and SMS campaigns — need a multi-brand link management architecture. Cuttly's Team plan workspace model, described in detail in the agency architecture guide, maps directly to this multi-brand use case.

Each brand gets its own team workspace, with its own branded domain and its own headers configured. Links created in Brand A's workspace use Brand A's domain and header; links created in Brand B's workspace use Brand B's domain and header. No cross-contamination of brand links, analytics, or header configurations.

In the Team Dashboard, the Tracking Header setup follows the same process as for individual accounts, but the header is configured at the team level. Any team member with Admin or Owner role can manage headers for the team's domain. The Team API key (tied to the workspace, not to any individual) uses the hheader parameter for TRAI-compliant link creation — ensuring that automated pipeline integrations do not depend on any specific individual's account.

For adding and using 2s.ms/HEADER/ in a Team Dashboard, the process mirrors the individual account process but is performed in the Team Settings section. See the Cuttly support article on Adding and Using 2s.ms/HEADER/ in Cuttly's Team Dashboard for the exact steps.

Managing Multiple Campaigns with Multiple Headers

The header in a TRAI-compliant link is a static prefix registered on DLT — it is part of the URL pattern registered for the sender. In practice, a single brand may have different headers registered for different business purposes: a transactional header for OTPs and order confirmations, a promotional header for marketing campaigns, and an informational header for service updates.

Cuttly's multiple header support (5 per custom domain on Team, 15 on Enterprise) allows all of these DLT-registered headers to be configured under the same branded domain in Cuttly. When creating a link, select the appropriate header for the link's intended use — transactional links use the transactional header, promotional links use the promotional header.

Tagging in Cuttly adds an organisational layer: tag all transactional links with type-transactional, all promotional links with type-promotional. Cuttly Campaigns (Team plan+) aggregates analytics per tag, giving visibility into the combined performance of all links in each category — independent of the specific header used.

Analytics on TRAI-Compliant Links

TRAI-compliant links created through Cuttly — whether via 2s.ms/HEADER/ or branded domain with header — provide the same full analytics as all other Cuttly short links: total clicks, unique clicks, geographic distribution (highly relevant for India-market SMS campaigns — state-level geographic data shows which regions are responding to the campaign), device type, OS, browser, referrer, and time patterns.

For Indian SMS campaigns specifically, the geographic analytics dimension is valuable for regional campaign optimisation. An SMS campaign for a product with strong regional distribution can use per-state click analytics to identify whether the campaign is generating proportional engagement from target states. Significantly lower engagement from a target state despite high SMS delivery rates may indicate message relevance or language issues rather than delivery problems.

Time-of-day analytics — available in the hourly heat map from the Single plan — show when Indian recipients are most actively engaging with SMS campaign links. Peak click activity times for consumer SMS in India typically cluster in morning (8–10am IST), early afternoon (1–2pm IST), and evening (7–9pm IST) — but per-campaign data may reveal different patterns for specific audiences and message types.

What Cuttly Is and Is Not Responsible For

This distinction is important for compliance planning. Cuttly provides: the URL shortening infrastructure (the 2s.ms domain, the Tracking Header feature, the analytics), the technical format required for TRAI-compliant links (domain/HEADER/alias), and the tools to create and manage compliant links at scale.

Cuttly does not provide: DLT platform registration services, sender header registration assistance, message template registration, SMS delivery services, or any guarantee of regulatory compliance for the sender's specific use case. The business remains responsible for: registering on the DLT platform, registering their headers and static URL patterns, pre-registering message templates, and ensuring their SMS campaigns comply with all applicable TRAI regulations.

Cuttly explicitly requires users to accept a declaration of responsibility when adding a 2s.ms/HEADER/ or Tracking Header — confirming that the DLT registration is the user's responsibility. Businesses should work with their SMS service provider (aggregator) and DLT platform to confirm that their Cuttly-generated TRAI-compliant links meet all registration requirements before deploying in live campaigns.

Which Cuttly Plan Is Right for Indian SMS Marketing

The Single plan ($25/month) is the minimum plan that supports TRAI compliance features and the entry point for most Indian businesses. It provides: 1 Tracking Header per custom domain, up to 5 headers on 2s.ms, 5,000 links/month, 1 year of analytics history, and Let's Encrypt SSL for branded domains. Adequate for small to mid-size businesses running 1 to 5 regular SMS campaigns with a single header per domain.

The Team plan ($99/month) is appropriate for larger enterprises running multiple campaigns across multiple header categories, businesses requiring the Team API for automated pipeline integration, and organisations managing multiple brands requiring separate team workspaces with isolated headers and analytics. 5 headers per custom domain, up to 10 on 2s.ms, 20,000 links/month per workspace.

The Enterprise plan ($149/month) is appropriate for high-volume SMS operations with extensive header management needs: 15 headers per custom domain, up to 99 on 2s.ms, 50,000 links/month. Suitable for telecom-adjacent businesses, large FMCG brands, and major financial services companies running high-frequency, high-volume SMS campaigns across many registered headers.

Start with Cuttly's Single plan to access TRAI compliance features — create your account and add your 2s.ms/HEADER/ or configure your branded domain's Tracking Header. Registration required. DLT registration with TRAI's platform must be completed separately through your SMS service provider before using TRAI-compliant links in live campaigns.

Industries and Use Cases: Who Needs TRAI-Compliant Links in India

TRAI's DLT framework applies to all commercial SMS senders in India — not just specific industries. But certain sectors send particularly high volumes of SMS with embedded links, making TRAI-compliant link infrastructure operationally critical rather than merely desirable.

E-Commerce and Retail

Indian e-commerce platforms — from large marketplaces to independent D2C brands — send extensive SMS communications: order confirmations with tracking links, delivery notifications with live tracking URLs, promotional campaign links for flash sales and seasonal offers, cart abandonment reminders with return links, and customer satisfaction survey links post-delivery. Each of these link types requires a TRAI-compliant format with the appropriate DLT-registered header for the message category (transactional vs promotional).

For high-volume e-commerce operations generating thousands of unique links per day (per-order tracking links, personalised campaign links), the Team plan API with programmatic TRAI-compliant link creation is the appropriate infrastructure. Each order notification generates a unique alias under the same header, creating a scalable, compliant link architecture without manual link creation.

Banking, Financial Services, and Insurance (BFSI)

BFSI businesses in India send some of the highest-sensitivity SMS communications — OTP messages, transaction confirmation links, KYC completion links, insurance renewal reminders, and investment update notifications. Trust in these communications is paramount; a link that does not appear on the brand's own registered domain in an OTP or transaction SMS creates immediate recipient suspicion.

Branded custom domain with header is particularly important for BFSI SMS — go.hdfc.bank/ABCDEF/otp-confirm is far more trustworthy than a generic short domain link for sensitive financial communications. The DLT requirement for BFSI transactional messages is strictly enforced; delivery failures from non-compliant links directly affect customer experience at critical transaction moments.

Logistics and Courier Services

Logistics companies generating shipment tracking link notifications — "Your package is out for delivery. Track here: domain/HEADER/trackXYZ" — require per-shipment unique links within a standard TRAI-compliant format. The high frequency of these links (a mid-size logistics operation generates thousands of unique tracking links per day) makes API-based automated link creation essential. Static header with dynamic per-shipment alias is exactly the architecture that 2s.ms/HEADER/alias or branded-domain/HEADER/alias provides.

Telecom and Utility Services

Indian telecom operators and utility service companies send bill payment reminder links, service activation links, recharge offer links, and complaint status update links at very high volumes. For telecom companies operating under TRAI's own regulatory framework, TRAI compliance for SMS links is a direct regulatory obligation rather than a general best practice. Multiple headers for different service categories (billing vs promotional vs service notifications) require the Team or Enterprise plan header limits.

Healthcare and Pharmaceuticals

Appointment reminder links, prescription refill reminders, healthcare platform registration links, and wellness programme promotion links in India all require TRAI-compliant SMS format. Healthcare SMS links carry additional trust weight — a patient receiving an appointment reminder with a healthcare provider's branded domain link has higher click confidence than one receiving a generic short link. The branded domain + header combination is the recommended approach for healthcare SMS in India.

Designing TRAI-Compliant Links for Maximum Effectiveness

Within the TRAI format constraints, there is still meaningful room for link design decisions that affect click rates and campaign effectiveness.

Alias design within the 9-character 2s.ms limit: with only 9 characters available for the alias in the 2s.ms format, meaningful human-readable aliases are possible but require careful economy. A 7-character alias like track-1 (7 chars), summr26 (7 chars), confirm (7 chars), or payhere (7 chars) communicates the link's purpose within the character budget. For 2s.ms links, auto-generated 6 to 7-character alphanumeric aliases are also acceptable since the header already provides brand identification — the 2s.ms link includes the brand's registered header, which is the primary trust signal.

Alias design for branded domain links: branded domain links do not have the 9-character alias restriction — the domain itself is longer but the alias can be more descriptive. yourbrnd.link/ABCDEF/summer-offer uses a 12-character descriptive alias. For branded domain TRAI links, apply the same slug design principles as any other branded link — descriptive, lowercase, hyphen-separated, consistent with the campaign naming convention.

UTM parameters for campaign attribution: add UTM parameters to the destination URL (not to the short link's alias, which is within the TRAI format) for GA4 attribution. The destination URL for a summer campaign link: https://yourshop.com/summer?utm_source=sms&utm_medium=sms&utm_campaign=summer-india-2026. This passes campaign attribution through the TRAI-compliant short link to the destination's analytics system.

Unique clicks for per-recipient analytics: enable unique click counting on TRAI-compliant links to understand how many individual recipients engaged with the SMS link — distinct from total clicks (which may include the same recipient clicking multiple times). For personalised SMS campaigns where each recipient receives a unique link alias, total clicks and unique clicks are equivalent by definition; for shared campaign links, unique click counting provides a more accurate reach metric.

Monitoring and Maintaining TRAI-Compliant Link Infrastructure

TRAI-compliant link infrastructure requires periodic maintenance to remain effective. Key maintenance activities:

DLT registration renewals: DLT registrations (entity, header, template) have validity periods that require renewal. Confirm renewal schedules with your DLT platform and SMS aggregator. An expired DLT header registration causes SMS delivery failures — even if the Cuttly Tracking Header configuration is unchanged. The DLT expiry is external to Cuttly and must be monitored independently.

Domain renewal for branded links: the branded custom domain used in TRAI-compliant SMS links must be renewed before expiry. An expired domain causes all links on that domain to fail — a high-severity incident for any business with active SMS campaigns relying on those links. Enable auto-renewal for TRAI-linked branded domains and document them in the organisation's domain asset register as described in the URL shortener security guide.

Template-URL alignment: the TRAI DLT framework requires that message templates and URL patterns remain consistent. If the domain or header in the short link changes (following a domain migration, a brand refresh, or a header reassignment), the DLT template registration must be updated to reflect the new static URL prefix. Campaign links using the old domain or header will continue to work through Cuttly (the redirect is maintained) but new templates for new messages must use the updated registration.

Practical Example: Full TRAI-Compliant SMS Campaign Setup

A concrete end-to-end example of how an Indian e-commerce company sets up a TRAI-compliant promotional SMS campaign using Cuttly:

Context: ShopFresh India (fictional) is running a Summer Sale promotion. They have registered on the DLT platform with entity name "ShopFresh India". They have registered the header SFRESH for promotional messages. They have connected go.shopfresh.in as their branded domain in Cuttly (Single plan). They have configured the SFRESH header as the Tracking Header for go.shopfresh.in.

Link creation: for each promotional message category, they create a short link:

• Email marketing channel: go.shopfresh.in/SFRESH/summl26 (destination: summer sale page + utm_source=sms&utm_medium=sms)
• Push notification channel: separate link go.shopfresh.in/SFRESH/summp26

DLT template registration: they register the message template on DLT: "Dear {customer_name}, Shop our Summer Sale! Upto 50% off. Shop now: go.shopfresh.in/SFRESH/ {#var#}. Reply STOP to opt-out." The static part go.shopfresh.in/SFRESH/ is the registered URL pattern; the dynamic part {#var#} is the alias.

SMS sending: their SMS aggregator sends the messages with the registered sender header and template. The carrier's DLT system validates the URL pattern against the registration. Messages are delivered. Recipients see links on ShopFresh's own domain, trust them, and click through.

Analytics: Cuttly's analytics on each link show total clicks, geographic distribution (which states are most responsive to the summer sale), device breakdown (predominantly mobile as expected for SMS), and time patterns (peak engagement hours in IST).