URL Shorteners in SMS: Why Carriers Filter bit.ly Links

Updated

Short answer: Spammers use shared public shorteners such as bit.ly and TinyURL so often that carriers treat them as high risk. Texts with these links are more likely to be filtered, and an A2P 10DLC campaign whose samples include one can be rejected. Use a full HTTPS link or a branded short domain that your business owns.

What the rules say

Twilio's help article on shortened links is direct: "Do not send links that have been shortened using shared public URL shorteners, such as free TinyUrl or Bitly links. US carrier policies strongly discourage the use of shared public URL shorteners, due to the frequency of use by spammers, scammers and other bad actors. The use of these public shared shorteners will result in higher risk of filtering, with no recourse if filtering does occur."

Twilio gives the same advice for toll-free numbers, where shared shorteners "are forbidden by US carriers and will result in filtering."

CTIA's Messaging Principles ask senders who shorten links to "use a shortener with a web address and IP address(es) dedicated to the exclusive use of the Message Sender."

Twilio also sums up T-Mobile's Code of Conduct and US carrier expectations in two tests. A short link should be proprietary, which Twilio defines as "a dedicated custom domain that belongs to your business, not a free shared public link shortener". It should also be properly branded, meaning "the domain aligns with the message sender identified in the text message itself".

HighLevel warns that public shorteners "can harm SMS deliverability" and that carriers, especially T-Mobile and AT&T, flag them "as high risk due to their association with spam and phishing." HighLevel also states that "AT&T outright blocks public shorteners" and that "T-Mobile prohibits URL cycling and multiple redirects". Those are HighLevel's statements, not the carriers' own documents.

Shorteners in A2P 10DLC registration

Shorteners also cause registration problems. The Campaign Registry's user guide says: "Note that public URL shorteners (bitly, tinyurl) are not accepted." Twilio has three rejection codes for links:

  • 30892: "Public shorteners such as bit.ly or TinyURL can cause the campaign to be rejected."
  • 30963: "Public URL shortening services such as bit.ly, tinyurl.com, goo.gl, and similar services are not permitted in A2P 10DLC campaigns because they mask the true destination URL." Your own domain does not help if it works as a redirect service. Twilio also flags a domain "that functions as a URL redirect service, behaving similarly to a public URL shortener even if it is a custom domain."
  • 30964: "All URLs included in A2P 10DLC campaigns, whether in sample messages, campaign descriptions, or opt-in flows, must use HTTPS to ensure encrypted communication between consumers and your website."

Links must also belong to you: "Links within the messaging content must represent the registered brand. Third-party redirects aren't permitted." A link with a bad reputation fails on its own too. Error 30961 applies when URLs "have a poor domain reputation or are flagged in threat intelligence databases."

Put your real links in your samples so reviewers can check them. Twilio: "Whenever possible, include example links in the message_samples so that links can be verified."

If you were rejected with 30963 or 30964, you can fix it. Twilio's rejection guide says that from September 15, 2026, these two "allow correction and resubmission once the affected URLs comply".

What to use instead

  1. A full HTTPS link on your own domain. HighLevel's advice: "When possible, include the full URL to boost transparency (even if it takes extra characters)." For campaign samples, it says: "Use full, direct HTTPS URLs when a URL is included."
  2. A branded short domain you own. Twilio: "use a dedicated, branded short domain that belongs to your business." Error 30963 notes that "Branded short domains owned and operated by your business (for example, yourcompany.link) are generally acceptable."
  3. No more than one redirect. HighLevel: "Limit redirects to no more than one, and avoid cloaking link destinations."
  4. A site that says who you are. CTIA: "Web addresses contained in messages as well as any websites to which they redirect should unambiguously identify the website owner (i.e., a person or legally registered business entity) and include contact information, such as a postal mailing address."

Twilio's own example shows the branding test. It compares one message from a group called Americans for Clean Air (ACA) with two links. The first, abcd.com/1234xyz, has no connection to the sender. The second, aca.com/1234xyz, matches the sender's name. Only the second is properly branded.

If you send through Twilio, its Link Shortening feature "allows you to send messages with shortened links using your own company-branded domain", and "You must own the domain you use for link shortening (just as Twilio owns twil.io)." Its short links expire after 90 days. After that, a click goes to a fallback URL.

This is not about getting past filters

The goal is a link that people and carriers can recognize, not a trick to slip past filtering. Twilio's Messaging Policy already bans misspellings and odd opt-out phrases "created to evade detection and prevention mechanisms". HighLevel tells you to "avoid cloaking link destinations."

The free A2P 10DLC sample checker flags public link shorteners in your samples. It also checks that each sample names your brand and that at least one has an opt-out instruction.

For the rest of the sample rules, see A2P 10DLC sample messages. For other causes of rejection, see why A2P 10DLC campaigns get rejected.

Sources

Not legal advice. Carrier rules and provider documentation change, so check the linked sources before you rely on them.