This article needs additional citations for verification. (July 2014)
URL shortening is a technique on the World Wide Web in which a Uniform Resource Locator (URL) may be made substantially shorter and still direct to the required page. This is achieved by using a redirect which links to the web page that has a long URL. For example, the URL "https://example.com/assets/category_B/subcategory_C/Foo/" can be shortened to "https://example.com/Foo", and the URL "https://en.wikipedia.org/wiki/URL_shortening" can be shortened to "https://w.wiki/U". Often the redirect domain name is shorter than the original one. A friendly URL may be desired for messaging technologies that limit the number of characters in a message (for example SMS), for reducing the amount of typing required if the reader is copying a URL from a print source, for making it easier for a person to remember, or for the intention of a permalink. In November 2009, the shortened links of the URL shortening service Bitly were accessed 2.1 billion times.
Other uses of URL shortening are to "beautify" a link, track clicks, or disguise the underlying address. Although disguising of the underlying address may be desired for legitimate business or personal reasons, it is open to abuse. Some URL shortening service providers have found themselves on spam blocklists, because of the use of their redirect services by sites trying to bypass those very same blocklists. Some websites prevent short, redirected URLs from being posted.
In addition, as the service delivery time increases, the length of the URL will also increase. For example, a page history about this page generated in 2022, the URL "https://en.wikipedia.org/w/index.php?title=URL_shortening&action=history" can be shortened to "https://w.wiki/4ozb".
There are several reasons to use URL shortening. Often regular unshortened links may be aesthetically unpleasing. Many web developers pass descriptive attributes in the URL to represent data hierarchies, command structures, transaction paths or session information. This can result in URLs that are hundreds of characters long and that contain complex character patterns. Such URLs are difficult to memorize, type out or distribute. As a result, long URLs must be copied and pasted for reliability. Thus, short URLs may be more convenient for websites or hard copy publications (e.g. a printed magazine or a book), the latter often requiring that very long strings be broken into multiple lines (as is the case with some e-mail software or internet forums) or truncated.
On Twitter and some instant messaging services, there is a limit to the number of characters a message can carry – however, Twitter now shortens links automatically using its own URL shortening service, t.co, so there is no need to use a separate URL shortening service just to shorten URLs in a tweet. On other such services, using a URL shortener can allow linking to web pages which would otherwise violate this constraint. Some shortening services, such as goo.gl, tinyurl.com, and bit.ly can generate URLs that are human-readable, although the resulting strings are longer than those generated by a length-optimized service. Finally, URL shortening sites provide detailed information on the clicks a link receives, which can be simpler than setting up an equally powerful server-side analytics engine, and unlike the latter, does not require any access to the server.
URLs encoded in two dimensional barcodes such as QR code are often shortened by a URL shortener in order to reduce the printed area of the code, or allow printing at lower density in order to improve scanning reliability.
Registering a short URL
Some websites create short links to make sharing links via instant messaging easier, and to make it cheaper to send them via SMS. This can be done online, at the web pages of a URL shortening service; to do it in batch or on demand may require the use of an API.
In URL shortening, every long URL is associated with a unique key, which is the part after its top-level domain name. For example, https://tinyurl.com/m3q2xt has a key of m3q2xt. Not all redirection is treated equally; the redirection instruction sent to a browser can contain in its header the HTTP status 301 (Moved Permanently), 302 (Found), 307 (Temporary Redirect) or 308 (Permanent Redirect).
There are several techniques to implement a URL shortening. Keys can be generated in base 36, assuming 26 letters and 10 numbers. In this case, each character in the sequence will be 0, 1, 2, ..., 9, a, b, c, ..., y, z. Alternatively, if uppercase and lowercase letters are differentiated, then each character can represent a single digit within a number of base 62 (26 + 26 + 10). In order to form the key, a hash function can be made, or a random number generated so that key sequence is not predictable. Or users may propose their own custom keys. For example, https://example.com/product?ref=01652&type=shirt can be shortened to https://tinyurl.com/exampleshirt.
Makers of URL shorteners usually register domain names with less popular or esoteric Top-level domains in order to achieve a short URL and a catchy name, often using domain hacks. This results in registration of different URL shorteners with a myriad of different countries, leaving no relation between the country where the domain has been registered and the URL shortener itself or the shortened links. Top-level domains of countries such as Libya (.ly), Samoa (.ws), Mongolia (.mn), Malaysia (.my) and Liechtenstein (.li) have been used as well as many others. In some cases, the political or cultural aspects of the country in charge of the top-level domain may become an issue for users and owners, but this is not usually the case.
Services may record inbound statistics, which may be viewed publicly by others.
Expiry and time-limited services
Many providers claim their shortened URLs won’t expire for as long as the service is provided. However, they may decide to discontinue the service at any time.
A permanent URL is not necessarily a good thing. There are security implications, and obsolete short URLs remain in existence and may be circulated long after they cease to point to a relevant or even extant destination. Sometimes a short URL is useful simply to give someone over a telephone conversation for a one-off access or file download, and no longer needed within a couple of minutes.
Some providers offer expirations on shortened URLs. This may include URLs that expire after a certain amount of time, on a certain date or after a certain number of usages.
A Microsoft Security Brief recommends the creation of short-lived URLs, but for reasons explicitly of security rather than convenience.
An early reference is US Patent 6957224, which describes
...a system, method and computer program product for providing links to remotely located information in a network of remotely connected computers. A uniform resource locator (URL) is registered with a server. A shorthand link is associated with the registered URL. The associated shorthand link and URL are logged in a registry database. When a request is received for a shorthand link, the registry database is searched for an associated URL. If the shorthand link is found to be associated with a URL, the URL is fetched, otherwise an error message is returned.
The patent was filed in September 2000; while the patent was issued in 2005, US patent applications are made public within 18 months of filing.
Another reference to URL shortening was in 2001. The first notable URL shortening service, TinyURL, was launched in 2002. Its popularity influenced the creation of at least 100 similar websites, although most are simply domain alternatives. Initially, Twitter automatically translated URLs longer than twenty-six characters using TinyURL, although it began using bit.ly instead in 2009 and later developed its own URL shortening service, t.co.
On 14 August 2009 WordPress announced the wp.me URL shortener for use when referring to any WordPress.com blog post. In November 2009, shortened links on bit.ly were accessed 2.1 billion times. Around that time, bit.ly and TinyURL were the most widely used URL-shortening services.
One service, tr.im, stopped generating short URLs in 2009, blaming a lack of revenue-generating mechanisms to cover costs and Twitter's default use of the bit.ly shortener, and questioning whether other shortening services could be profitable from URL shortening in the longer term. It resumed for a time, then closed.
The shortest possible long-term URLs were generated by NanoURL from December 2009 until about 2011, associated with the top-level .to (Tonga) domain, in the form http://to./xxxx, where xxxx represents a sequence of random numbers and letters.
On 14 December 2009 Google announced a service called Google URL Shortener at goo.gl, which originally was only available for use through Google products (such as Google Toolbar and FeedBurner) and extensions for Google Chrome. On 21 December 2009, Google introduced a YouTube URL Shortener, youtu.be. From September 2010 Google URL Shortener became available via a direct interface. The goo.gl service provides analytics details and a QR code generator. On 30 March 2018 Google announced that it is "turning down support for goo.gl over the coming weeks and replacing it with Firebase Dynamic Links" (although existing goo.gl links will continue to function).
The main advantage of a short link is its brevity. Depending on the transcription used, it might be more easily communicated and entered without error. To some extent it can obscure the destination of the URL; this may be advantageous, disadvantageous, or irrelevant.
Short URLs often circumvent the intended use of top-level domains for indicating the country of origin; domain registration in many countries requires proof of physical presence within that country, although a redirected URL has no such guarantee.
URL shortening may be utilized by spammers or for illicit internet activities. As a result, many have been removed from online registries or shut down by web hosts or internet service providers.
According to Tonic Corporation, the registry for .to domains, it is "very serious about keeping domains spam free" and may remove URL shortening services from their registry if the service is abused.
In addition, "u.nu" made the following announcement upon closing operations:
The last straw came on September 3, 2010, when the server was disconnected without notice by our hosting provider in response to reports of a number of links to child pornography sites. The disconnection of the server caused us serious problems, and to be honest, the level and nature of the abuse has become quite demoralizing. Given the choice between spending time and money to find a different home, or just giving up, the latter won out.
Google's url-shortener discussion group has frequently included messages from frustrated users reporting that specific shortened URLs have been disabled after they were reported as spam.
A study in May 2012 showed that 61% of URL shorteners had shut down (614 of 1002). The most common cause cited was abuse by spammers.
The convenience offered by URL shortening also introduces potential problems, which have led to criticism of the use of these services. Short URLs, for example, will be subject to linkrot if the shortening service stops working; all URLs related to the service will become broken. It is a legitimate concern that many existing URL shortening services may not have a sustainable business model in the long term. In late 2009, the Internet Archive started the "301 Works" projects, together with twenty collaborating companies (initially), whose short URLs will be preserved by the project.
Shortened internet links typically use ccTLD domains, and are therefore often under the jurisdiction of a nation other than where the service provider is located. Libya, for instance, exercised its control over the .ly domain in October 2010 to shut down vb.ly for violating Libyan pornography laws. Failure to predict such problems with URL shorteners and investment in URL shortening companies may reflect a lack of due diligence.
Blocking and banning
Some websites prevent short, redirected URLs from being posted.
In April 2009, TinyURL was reported to be blocked in Saudi Arabia. Yahoo! Answers blocks postings that contain TinyURLs, and Wikipedia does not accept links by any URL shortening services in its articles. The Reddit community strongly discourages – and in some subreddits, outright bans – URL shortening services for link submissions, because they disguise the origin domain name and whether the link has previously been submitted to Reddit, and there are few or no legitimate reasons to use link shorteners for Reddit link submissions.
Privacy and security
Some URL shortening services filter their links through bad-site screening services such as Google Safe Browsing. Many sites that accept user-submitted content block links, however, to certain domains in order to cut down on spam, and for this reason, known URL redirection services are often themselves added to spam blocklists.
Another privacy problem is that many services' shortened URL format is small enough that it is vulnerable to brute-force search. Many people use URL shorteners when they share links to private content, and in fact many web services like Google Maps have offered automatic generation of shortened links for driving directions that reveal personal information like home addresses and sensitive destinations like "clinics for specific diseases (including cancer and mental diseases), addiction treatment centers, abortion providers, correctional and juvenile detention facilities, payday and car-title lenders, gentlemen’s clubs, etc."
Additional layer of complexity
Short URLs, although making it easier to access what might otherwise be a very long URL or user-space on an ISP server, add an additional layer of complexity to the process of retrieving web pages. Every access requires more requests (at least one more DNS lookup, though it may be cached, and one more HTTP/HTTPS request), thereby increasing latency, the time taken to access the page, and also the risk of failure, since the shortening service may become unavailable. Another operational limitation of URL shortening services is that browsers do not resend POST bodies when a redirect is encountered. This can be overcome by making the service a reverse proxy, or by elaborate schemes involving cookies and buffered POST bodies, but such techniques present security and scaling challenges, and are therefore not used on extranets or Internet-scale services.[original research?]
|goo.gl||general public||n.a.||Replaced by FDL (uses Bitly)|
|ow.ly||Hootsuite Media||general public||yes||Now inside the Hootsuite dashboard|
|t.co||internal||n.a.||About Twitter's link service|
|w.wiki||Wikimedia Foundation||internal||n.a.||Users can generate links to Wikimedia Foundation projects only.|
|youtu.be||YouTube (Google)||internal||n.a.||Announcement of youtu.be Links|
Open source and commercial scripts are also available for redirecting and shortening links, usually written in PHP as a web application or a plugin for one of the popular applications such as WordPress. Such scripts avoid many issues with shortening services, keep the domain name as part of the shortened link, and can be made private.
- Goo.gl Challenges Bit.ly as King of the Short Archived 10 July 2011 at the Wayback Machine – New York Times, 14 December 2009
- Curtis, Sophie (8 August 2014). "Twitter's t.co URL shortener used to spread spam". The Daily Telegraph. Archived from the original on 3 April 2015. Retrieved 15 March 2015.
- "t.co links". developer.twitter.com. Retrieved 10 May 2022.
- "g.co". g.co. Retrieved 10 May 2022.
- "URL Shortener". shortener.godaddy.com. Retrieved 10 May 2022.
- "Spammers Storm URL Shortening Services". CertMag. 17 August 2009. Archived from the original on 1 November 2019.
- "#HootSuite Offers Choice of URL Shorteners ~ From Libya to Liechtenstein – HootSuite Social Media Management". Blog.hootsuite.com. Archived from the original on 14 June 2013. Retrieved 20 April 2013.
- Chapman, Stephen (28 August 2012). "How to spy on campaigns of competitors who use URL shorteners". ZDNet. Archived from the original on 2 September 2012. Retrieved 10 September 2012.
- Sullivan, Bryan (March 2009). "Protect Your Site With URL Rewriting – A Stateless Approach: Automatically Expiring URLs". Security Briefs. Microsoft MSDN Magazine. Archived from the original on 17 July 2013. Retrieved 1 August 2013.
- US patent 6957224, Nimrod Megiddo and Kevin S. McCurley; assigned to IBM corp., "Efficient retrieval of uniform resource locators", issued 2005-10-18
- "Comment thread 8916" Archived 5 September 2009 at the Wayback Machine. Metafilter. 10 June 2001; Announcement of URL shortening service available at makeashorterlink.com
- "URL Shortening Services" Archived 3 January 2010 at the Wayback Machine shortenurl – Supported URL shortening services
- Wortham, Jenna (7 May 2009) "Bit.ly Eclipses TinyURL on Twitter" Archived 23 November 2010 at the Wayback Machine Bits (blog at The New York Times). Retrieved 1 January 2011.
- "WP.me – Shorten Your Links" Archived 18 August 2009 at the Wayback Machine WordPress. 14 August 2009.
- Ahmed, Murad (7 December 2009). "New Project in Scramble To Save Vanishing Internet Links – The Internet Archive Is Fighting To Preserve Shortened Web Links Created by Free Online Services That May Be Running Out of Money" Archived 17 December 2013 at the Wayback Machine. The Times. Retrieved 1 January 2011.
- tr.im R.I.P. blog.tr.im
- tr.im Resurrected. blog.tr.im
- Michlick, Frank. ".TO ccTLD Becomes Worlds Shortest URL Shortener". Domainnamenews.com. Archived from the original on 3 May 2013. Retrieved 20 April 2013.
- Muthusrinivasan, Muthu (14 December 2009). "Making URLs Shorter for Google Toolbar and FeedBurner". Googleblog.blogspot.com. Archived from the original on 31 May 2013. Retrieved 20 April 2013.
- "goo.gl "URL Shortener – Google Chrome Extension Gallery"". Archived from the original on 12 April 2011. Retrieved 20 April 2013.
- "Official YouTube Blog: Make Way for youtu.be Links". Official YouTube Blog. Archived from the original on 25 December 2009. Retrieved 24 December 2009.
- Hermanto, Michael. "Transitioning Google URL Shortener to Firebase Dynamic Links". Google Developers. Archived from the original on 30 June 2018. Retrieved 1 April 2018.
- "Tonic Corporation Frequently asked questions". Tonic.to. Archived from the original on 19 July 2013. Retrieved 20 April 2013.
- http://u.nu/unu-discontinued "u.nu :: discontinued."
- "Google Discussiegroepen". Archived from the original on 8 July 2019. Retrieved 20 April 2013.
- "Ultimate list of URL shorteners". Yi.tl. 23 May 2012. Archived from the original on 18 April 2013. Retrieved 20 April 2013.
- "301Works.org : Free Software : Download & Streaming : Internet Archive". archive.org. Archived from the original on 1 October 2016. Retrieved 19 August 2016.
- Staff writer (14 October 2010). "Law, Politics and Internet Addresses – Tough.ly/Treated – Shortened Web Links Are Convenient, But They Come at a Price". The Economist. Archived from the original on 17 October 2010. Retrieved 1 January 2010.
- "TinyURL Blocked in Saudi Arabia". Committee to Protect Bloggers. 16 April 2009. Archived from the original on 19 April 2009.
- "Spam blacklist". meta.wikimedia.org. Meta, discussion about Wikimedia projects. Archived from the original on 20 March 2017. Retrieved 4 November 2016.
- "Rediquette". Archived from the original on 8 February 2017. Retrieved 9 February 2017.
- Krebs, Brian (13 June 2006). "Spam Spotted Using TinyURL". Security Fixes (blog at The Washington Post). Retrieved 1 January 2011.
- "Preview a TinyURL". Tinyurl.com. Archived from the original on 20 April 2013. Retrieved 20 April 2013.
- "the JoshMeister on Security: How to Preview Shortened URLs (TinyURL, bit.ly, is.gd, and more)". Security.thejoshmeister.com. 11 April 2009. Archived from the original on 25 March 2014. Retrieved 20 April 2013.
- University, Carnegie Mellon. "Shortened URL Security - Information Security Office - Computing Services - Carnegie Mellon University". www.cmu.edu. Retrieved 26 July 2022.
- "Updated: Cligs Got Hacked – Restoration from Backup Started" Blog at Cli.gs (16 June 2009).
- "Shmatikov, Vitaly, "Gone In Six Characters: Short URLs Considered Harmful for Cloud Services." Blog entry dated April 14, 2016; retrieved April 26, 2016". Archived from the original on 23 April 2016. Retrieved 26 April 2016.
- Georgiev, Martin; Shmatikov, Vitaly (2016). "Georgiev, Martin and Vitaly Shmatikov, "Gone In Six Characters: Short URLs Considered Harmful for Cloud Services." arXiv:1604.02734v1". arXiv:1604.02734v1 [cs.CR].
- "Firebase Extensions | Shorten URLs". Firebase. Retrieved 8 September 2020.
Shortens URLs written to a specified Cloud Firestore collection (uses Bitly).
- About Twitter's link service (http://t.co)
- Make Way for youtu.be Links