Trouble In Clever Domain Land: Bit.ly And Others Risk Losing Theirs Swift.ly
Bit.ly, HootSuite (with its Ow.ly service), Ad.ly and perhaps even Smel.ly could well be at risk of having their domain names sudden.ly taken away by the Libyan government. — Ben Metcalfe blogs …
Context & Ripple Effects
Bit.ly had been trying to turn its link service into a business, including a news-service revenue effort, while also adding safeguards through warnings about malicious links. The .ly concern introduces a separate dependency: control of the namespace underlying its product.
URL shortening's technical cost was also under scrutiny; testing of shortener-related web slowdowns put Facebook's FB.me in the same reliability conversation. The reported possibility of Libyan revocation is unconfirmed.
First-order effects
- The unconfirmed revocation risk leaves Bit.ly, HootSuite's Ow.ly, Ad.ly and Smel.ly exposed to disruption of the branded addresses on which their shortened links depend.
- For Bit.ly, the threat adds operational risk to a service already being positioned for revenue beyond basic link shortening.
Second-order effects
- Bit.ly and HootSuite would need to preserve link routing while establishing replacement addresses, making migration and user trust an immediate operating concern if the reported action occurs.
- Facebook's FB.me and other shorteners gain a new competitive comparison point: registry exposure alongside the speed and reliability concerns already associated with link routing.
Third-order effects
- If country-code registries can interrupt widely used services, domain hacks become an operational-dependency decision rather than a branding choice.
- The URL-shortener market's value proposition increasingly rests on durable routing and governance control, not only analytics, advertising, or link convenience.
The trend: Consumer web services built on country-code domain hacks are exposing how naming choices can create infrastructure and governance risk.