Overview
Mobile Commons shortlinks (for example, lil.ms/abc1) send people to a destination you’ve set up, such as a donation page, a petition, or a form. Occasionally, someone who taps a shortlink sees a browser message saying the connection or site is “Not secure” before reaching the page. This can happen even when the destination itself is fully secure.
Why this happens
Our default shared short domains are served over HTTP. When someone taps the link, their browser first opens the HTTP short URL, which then redirects to your destination page. If your destination uses HTTPS, as most donation and sign-up pages do, the page itself still loads securely.
Most browsers and devices handle this redirect without any message. However, some browsers, device settings, and network security tools (for example, on workplace or school networks) treat HTTP links more strictly and show a warning first. That’s why the warning appears for some recipients and not others, and why it isn’t caused by the destination page.
How to tell if this is what you’re seeing
- Send yourself a test message with the shortlink and tap it.
- If a warning appears, note which address the browser says isn’t secure.
- If the warning names the short domain (such as
lil.ms) rather than your destination page, it’s caused by the HTTP short link. - If the warning names your destination page, contact that site’s owner, because the issue is with the page itself.
How to fix it: use your own short domain
The recommended fix is to set up a custom short domain for your account. Your links will use your own domain instead of the shared one, with an SSL certificate so they open securely over HTTPS. All link shortening and click tracking will keep working as they do today. A recognizable, branded domain can also help supporters trust the links they receive.
-
Purchase a short domain from any registrar. You can also use a subdomain of a domain you already own, such as
m.yourdomain.org. -
Create a CNAME record pointing the domain to
lil.ms. For a root domain, set the record name to@. If your provider doesn’t allow a CNAME on the root domain, create it on a subdomain instead. Your IT team or domain provider can help with this step. -
Contact Technical Support and include:
- the domain or subdomain
- a screenshot of the CNAME record
- if you’re using a root domain, the page visitors should land on if they go to the domain directly (for example, your homepage)
- We complete the setup. We’ll add the domain to your account and generate and manage the SSL certificate for you. You don’t need to buy or upload a certificate yourself.
Good to know
- There’s no cost from Mobile Commons to set up or use a custom short domain. The domain itself is the only expense.
- The DNS record must stay in place. If it’s removed or changed, links already sent on that domain will stop working.
- For more on custom short domains, see Tracking Clicks with Vanity URLs and Other Link Shortening Tools.