What is redirect.name?
Updated
redirect.name is a DNS-based URL redirect service: you point a hostname at its server with a CNAME (or an A record), then describe the destination in a TXT record. There is no server to run, no signup, and no dashboard — your DNS provider holds the redirect rules, and redirect.name reads the TXT record at request time to issue the redirect. It suits anyone who controls DNS for a domain and wants simple, versionable redirects without deploying or maintaining anything.
How it works
Two DNS records describe one redirect:
- A CNAME (or A record) that points your hostname at redirect.name's server.
- A TXT record at
_redirect.that describes where to send visitors.
At request time, redirect.name reads the TXT record and returns the redirect. Because DNS is the source of truth, changing a redirect means editing a DNS record — nothing to log into on the redirect side.
Setup
Point your hostname at alias.redirect.name:
| Type | Name | Value |
|---|---|---|
| CNAME | go.example.com. | alias.redirect.name. |
If your DNS provider doesn't support CNAME flattening at the apex (sometimes offered as an ALIAS or ANAME record), use an A record pointing to 45.55.126.223 instead.
Then add a TXT record at _redirect.:
| Type | Name | Value |
|---|---|---|
| TXT | _redirect.go.example.com. | Redirects to https://example.com/ |
The _redirect. prefix is required because TXT and CNAME records can't coexist at the same name.
Wait for DNS to propagate (usually a minute or two), then visit your hostname.
Redirect rules
The TXT record value is the rule, written in plain English:
| TXT record value | Behavior |
|---|---|
Redirects to |
302 to the destination |
Redirects permanently to |
301 to the destination |
Redirects from … to … |
302 when the request path matches |
Redirects from … to … with 308 |
Same, with an explicit status: 301, 302, 307, or 308 |
Redirects from /path/* to https://example.com/* |
Wildcard: whatever * matches in the path replaces * in the destination |
Destinations can use http://, https://, ftp://, mailto:, magnet:, or an absolute path.
You can add multiple TXT records at the same name. Path-specific rules (Redirects from …) are tried first; catch-all rules (Redirects to …) only apply if no path rule matches.
Examples
Simple redirect — send all traffic to one URL:
| Type | Name | Value |
|---|---|---|
| TXT | _redirect.go.example.com. | Redirects to https://www.example.com/ |
Permanent redirect — for moves that won't be undone:
| Type | Name | Value |
|---|---|---|
| TXT | _redirect.old.example.com. | Redirects permanently to https://new.example.com/ |
Path routing — redirect one path, send the rest elsewhere:
| Type | Name | Value |
|---|---|---|
| TXT | _redirect.docs.example.com. | Redirects from /api to https://api-docs.example.com/ |
| TXT | _redirect.docs.example.com. | Redirects to https://docs.example.com/ |
Wildcard forwarding — whatever * matches in the path replaces * in the destination:
| Type | Name | Value |
|---|---|---|
| TXT | _redirect.links.example.com. | Redirects from /blog/* to https://blog.example.com/posts/* |
Other schemes — redirect to mail, magnet links, etc.:
| Type | Name | Value |
|---|---|---|
| TXT | _redirect.hi.example.com. | Redirects to mailto:… |
When to use it
Choose redirect.name when you already manage DNS for the domain and want redirects that are simple, declarative, and require no hosting. It fits short links, domain moves, path routing, and forwarding to non-HTTP schemes.
It is a poorer fit if you need redirect logic that depends on request headers, cookies, geo, or A/B testing — the rule language here is deliberately limited to paths and destinations. It's also worth checking your DNS provider's support for CNAME flattening (or ALIAS/ANAME) if you need redirects at the apex, since that determines whether you use a CNAME or the A record fallback.