---
title: The sl. url
description: sl.shebang.pro/<code-or-alias> — resolved by resource id, and unaffected by the public-id change.
---

# The sl. url

A short link is served at:

```
sl.shebang.pro/<code>
```

or, once a custom alias is set (see
[short links and aliases](/sherlink/short-links-and-aliases)):

```
sl.shebang.pro/<alias>
```

## It serves the resource, not a redirect to it

`sl.` answers a plain `200` with the wrapped page or file's own content
directly. It does not `302` to the `p.` or `f.` address underneath —
visiting a short link is indistinguishable, from the response, from
visiting the resource's own address.

## Resolved by id, not by handle or slug

A short link resolves by its underlying resource's id, which is exactly
what makes it unaffected by the change described in
[public ids and urls](/concepts/public-ids-and-urls): where an old
`@handle/slug` address needed a `301` bridge once public ids landed, a
short link never needed one, since it was never built from a handle or
a slug to begin with.

## Looking one up

`link_get` accepts a code, a custom alias, or a link id interchangeably
— whichever you have on hand:

```
link_get({ code_or_id: "launch" })
```

## Next

[Tools](/sherlink/tools).
