How to Keep Old Short Links from Being Hijacked: Good, Better, Best

The safest link to print is a plain redirect on a domain you own, kept in your own repo. A short domain you run yourself comes next. A public shortener like Bitly is the weakest option, because the vendor decides where the link goes for as long as it exists.

In Old Bitly links hijacked in Burger King, McDonald’s and Trump tweets, the Ransomnews Research Team shows how 15-year-old tweets started sending readers somewhere new without anyone touching the brands’ accounts. Here are three levels for publishing links, and what each costs.

Table of Contents

On 24 July 2011, Burger King tweeted a Bitly link to its restaurant locator. Bitly’s own information page, Ransomnews found, shows that the same link was created again at 05:32 UTC on 15 November 2026. It now pointed at Wikipedia’s list of Nazi concentration camps. A McDonald’s link from June 2011 had been re-created 18 minutes earlier and pointed at the article on the 9⁄11 attacks.

Nobody posted from either account. The part after the slash, which Bitly calls the back-half, was registered a second time, and its new owner chose the destination.

Ransomnews then checked 97 Bitly links from Donald Trump’s tweets between 2009 and 2013. 56 had been created after the tweets they sit in. Most still led where the tweet suggested, but seven pointed somewhere else. Bitly confirmed the issue on X the same day, suspended the accounts involved and started disabling the links.

Good: a public shortener

Bitly’s help pages say a back-half can’t be reused, even after the account behind it is deleted. Another page says Bitly deletes accounts that have been inactive for three years. The creation dates Ransomnews collected show the first promise didn’t hold, and a similar bug was reported fixed in February 2025.

  • Buys: short links in seconds, click stats, no infrastructure.
  • Costs: the vendor owns the redirect table. A bug, a policy change or a shutdown changes every tweet, PDF and printed QR code that carries the link.

Running the shortener on a domain you own keeps the name yours. Self-hosted tools like YOURLS, Shlink or Kutt do this without a vendor in the middle.

  • Buys: nobody else can re-issue your codes.
  • Costs: you now run a service and must renew a second domain.
  • Misses: stale DNS. Two developers in the discussion described old CNAME records that pointed at a domain someone let lapse. Spammers bought it and served malware under a trusted name. One of them had made exactly that mistake.

Best: plain redirects on your main site

Use readable paths on the site you already run, like yoursite.com/locator, and keep the redirect list in your repo next to your web server or CDN config. One commenter made the same point about QR codes: a code printed on a poster should hold a direct URL to something you own.

  • Buys: every hop is yours and reviewed like code. The URL also tells readers where they’re going.
  • Costs: slightly longer links, and marketing loses the one-click shortener. Another developer pointed out that most long URLs come from UTM tags nobody trimmed.
  • Misses: your domain. Let it lapse and every printed link goes with it, so put it on auto-renew.
Situation Level Why
Throwaway link in a chat or a one-day campaign Good Nothing lasting points at it
Links in a product, docs or many social posts Better You keep the codes and the stats
Anything printed: packaging, posters, books, QR codes Best You can’t reprint it when the link breaks
Old posts full of public short links Audit now Add a + to a Bitly link to see its creation date

What to do this week: search your old posts and docs for bit.ly, check each link’s creation date, and move the ones that matter to redirects you own.

Is a vendor really less stable than you

The strongest pushback in the discussion: it’s a bet on stability either way. Bitly has outlived many startups that used it, and their links kept working after the company was gone. I think that’s fair for links you don’t control after printing. For your own brand’s links, though, I’d rather own the failure than discover it from a screenshot with two million views.

FAQ

Was Burger King’s account hacked?

No. Ransomnews found nothing posted from the account. The Bitly link in the old tweet was registered again by someone else.

Add a plus sign to the end of the link. Bitly’s information page shows the destination and the creation date.

Bitly’s help pages say no. Ransomnews found links from 2009 to 2012 tweets with creation dates between 2023 and 2026, and Bitly confirmed the issue.

What is a dangling CNAME?

A DNS record that still points at a domain or service you no longer control. Whoever takes that target can serve content under your name.

Only one you run on your own domain. A printed code can’t be updated, so its link should point at something you own.

Sources