APIs
Most of the link shortening providers offer a possibility to preview the URL a short link will redirect to. Most times, it is sufficient to modify a little detail of the short link:
Bitly
Add a plus sign (+) to the short link:
https://bit.ly/3kwQV20 -> https://bit.ly/3kwQV20+
Or paste the link into Bitly's link checker.
Cuttly
Add an at sign (@) to the short link:
https://cutt.ly/YEh65VC -> https://cutt.ly/YEh65VC@
is.gd
Add a hyphen sign (-) to the short link:
https://is.gd/vzC7mi -> https://is.gd/vzC7mi-
Tinycc
Add an equal sign (=) to the short link:
https://tiny.cc/pijs001 -> https://tiny.cc/pijs001=
TinyURL
Add a plus sign (+) to the short link:
https://tinyurl.com/3yw559cj -> https://tinyurl.com/3yw559cj+
Or add preview as a subdomain to the short link:
https://tinyurl.com/3yw559cj -> https://preview.tinyurl.com/3yw559cj
Command line tools
Not all link shortening providers offer an API to preview a short link. Other link shortening providers in contrast might preview too much by not only displaying the expanded URL but also rendering a preview image of the URL which requires following the link already.
To circumvent this, you can use command line tools to get the expanded URL of a short link. Technically, every link shortening provider uses URL redirection to forward you to the expanded URL. This is a concise technical process, that is not as ambiguous as whatever happens, when you use the preview API of a link shortening provider.
You can instruct command line tools to access a short link in the most minimal way by only getting the HTTP headers and thus the info about the redirection, but not to follow any redirections. This way, you can get the expanded URL without visiting it, probably for all link shortening providers, independently of potentially existing preview APIs.
curl
curl does not follow redirections by default. Just add --head to only request the header and --silent to get a less verbose output:
curl --head --silent https://bit.ly/3kwQV20 | grep -i ^Location:
Example output:
location: https://security.stackexchange.com/q/255448/230952
--head and --silent can be abbreviated with -Is.
wget
Alternative with wget:
wget --max-redirect=0 --server-response --spider https://bit.ly/3kwQV20 2>&1 | grep -i '^\s*Location:'
wget will follow redirections by default, so you have to limit it with --max-redirect=0. Furthermore, it will write to the error stream, so you have to redirect that to be able to grep it. Example output:
Location: https://security.stackexchange.com/q/255448/230952
If the target looks like another redirection, then you can re-run the command, changing --max-redirect=0 to --max-redirect=1. This makes wget stop before the second redirect, etc.
PowerShell
Alternative with Invoke-WebRequest:
(Invoke-WebRequest -Uri https://bit.ly/3kwQV20 -Method Head -MaximumRedirection 0 -ErrorAction SilentlyContinue).Headers.Location
Or more abbreviated:
(iwr https://bit.ly/3kwQV20 -Me H -Ma 0 -EA Si).Headers.Location
Example output:
https://security.stackexchange.com/q/255448/230952
Be aware that Windows PowerShell probably uses curl and wget as aliases for Invoke-WebRequest. If you really want to call curl, write it out as curl.exe:
curl.exe --head --silent https://bit.ly/3kwQV20 | Select-String -Pattern '^Location:'
3rd party URL checkers
If you do not have access to the above command line tools and you do not know a preview API of a particular link shortening provider, you can also use online services to expand the URL for you. Be aware that you probably do not know how exactly they work. So they might even access the target URL, which might be undesirable in some threat models. Example websites:
Conclusion
While many link shortening providers offer APIs to expand a URL, you have to remember the correct API to actually do it. As not all link shortening providers even offer an API for previews, a more generic approach is to use command line tools. They are probably built-in tools of your OS anyway (curl/wget on Linux/Unix and PowerShell on Windows) and therefor quite easy to access.
Expanding the URL helps you to tackle the threat from URL obfuscation, but be aware that there is currently no way to querry the expanded URL from a link shortening provider without them noticing it. So usage statistics cannot be avoided, when interacting with a short link.