How to Set Up a Redirect with redirect.name

Updated

To set up a redirect, you create two DNS records for your hostname: a CNAME pointing to alias.redirect.name (or an A record to 45.55.126.223 if your provider can't flatten a CNAME at the apex), and a TXT record at _redirect.<your-hostname> whose value is the redirect rule in plain English. Wait for DNS to propagate — usually a minute or two — then visit your hostname to confirm the redirect. There's no account, dashboard, or server to manage; your DNS provider is the source of truth, and redirect.name reads the TXT record at request time.

Before you start

You need:

  • Control over DNS records for the hostname you want to redirect.
  • A DNS provider that lets you add both a CNAME (or ALIAS/ANAME/A record) and a TXT record.
  • The destination URL you want visitors sent to.

No signup is required to use the service.

Step 1: Point the hostname at redirect.name

Add a CNAME record for the hostname you want to redirect:

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 instead:

Type Name Value
A example.com. 45.55.126.223

Step 2: Add the TXT record with your redirect rule

Add a TXT record at _redirect.<your-hostname>. The _redirect. prefix is required because TXT and CNAME records can't coexist at the same name.

Type Name Value
TXT _redirect.go.example.com. Redirects to https://example.com/

The TXT value is the rule. The syntax is plain English:

TXT record value Behavior
Redirects to 302 to the destination
Redirects permanently to 301 to the destination
Redirects from <path> to <destination> 302 when the request path matches
Redirects from <path> to <destination> 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.

Step 3: Wait for propagation and test

DNS propagation usually takes a minute or two. Once it's done, visit your hostname in a browser and confirm you land on the destination. If the redirect doesn't fire, check that the CNAME (or A record) and the TXT record are both present and that the TXT name includes the _redirect. prefix.

Common setups

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, and similar:

Type Name Value
TXT _redirect.hi.example.com. Redirects to mailto:...

Notes on HTTPS

The source material lists HTTPS as a topic but doesn't spell out the certificate behavior, so treat HTTPS handling as something to verify against your own hostname after setup rather than assume.