Why a link copied from X starts with t.co
X wraps every web address posted on the platform in its own t.co shortener. Its developer documentation says all URLs are wrapped with t.co and count as 23 characters in a post, however long the original is. The same docs show that the website field in a user profile is stored as a t.co link too.
You rarely see the t.co address itself. The post shows a friendlier display version, and the t.co link sits underneath it. That is why copying a link from a post can give you a t.co/... address that tells you nothing about where it goes.
The address shown in a post is not always where you land
X's data dictionary describes the pieces behind each link in a post. The url field is the t.co address. The expanded_url is the address the author posted. The display_url is what readers see, often cut short with an ellipsis. Some posts also carry an unwound_url, the final page after any further redirects.
X's own example shows why that last field matters. In it, the posted address is a feedback forum on uservoice.com, while the unwound address is a page on devcommunity.x.com. The text you read in the post showed where the author pointed the link, not where the link ended up. The same thing happens when someone posts a bit.ly or TinyURL address on X. You see the second shortener, not the destination.
Stacked shorteners and how many hops to expect
When someone posts a short link on X, the chain usually runs from t.co to the posted short link and then to the real page. That is two or three hops. Our expander follows up to 5 HTTP redirects and lists each one with its status code. A chain that keeps bouncing between shorteners and tracking domains is a reason to slow down, because legitimate shares rarely need that many steps.
There is a quieter clue too. Because X counts every link as 23 characters, a long address costs the author no more room than a short one. A second shortener inside a post was not needed to save space. It was added for some other purpose, such as counting clicks or hiding a long address.
Each hop gets a time limit of 10 seconds, and the whole chain has 15 seconds. If a server is slow on purpose, the expander reports the failure instead of waiting forever.
X's own checks, and why you might still expand
X's help centre says addresses converted by its link service are checked against a list of potentially dangerous sites, and that you see a warning before continuing when there is a match. That helps with known bad sites. A page set up an hour ago may not be on any list yet.
Expanding adds two things. You see the final domain before your browser loads anything, and our safety check also weighs the age of the domain and its HTTPS certificate. A destination registered last week that asks for a login deserves more caution than its post suggests. If a post links to something harmful, report the post on X and use the suspicious link checker guide for other places to report it.