Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is redirect.name?
redirect.name is a DNS-based URL redirection service. Instead of running a web server, configuring nginx, or signing up for a link-management dashboard, you describe each redirect in two DNS records. Your DNS provider becomes the single source of truth, and the service reads your TXT record at request time to decide where to send the visitor.
How it works
Two records do the job:
- A CNAME points your hostname at
alias.redirect.name(or an A record to the published IP if your provider can't flatten a CNAME at the apex). - A TXT record at
_redirect.yourhostnamecontains the rule in near-plain English, for exampleRedirects to https://example.com/.
The _redirect. prefix exists because a CNAME and a TXT record can't sit at the same name. Once DNS propagates — usually a minute or two — visiting the hostname triggers the redirect.
What the rules can express
| TXT value | Behaviour |
|---|---|
Redirects to … |
302 temporary |
Redirects permanently to … |
301 permanent |
Redirects from /path to … |
Matches only that path |
Redirects from /path/* to …/* |
Wildcard, with * substituted into the destination |
… with 308 (or 301/302/307) |
Explicit status code |
Destinations can be http://, https://, ftp://, mailto:, magnet:, or an absolute path. You can stack multiple TXT records at one name: path-specific rules are evaluated first, and a catch-all only applies when nothing more specific matches.
Who it suits, and the trade-offs
This fits developers and small teams who already manage DNS and want redirects to live in the same place as the rest of their domain configuration — versionable, scriptable, no extra account to own. It's a natural fit for moving a docs subdomain, forwarding an old marketing hostname, or routing /api to separate documentation.
The trade-off is that everything you'd expect from a control panel is absent by design: no analytics on click volume, no per-link editing UI, no team permissions. Changing a redirect means editing a DNS record and waiting for propagation, which is fine for stable infrastructure and awkward for campaign links you tweak hourly. Also check that your DNS provider supports the record types you need at the apex before committing.
Next step: pick one throwaway subdomain, add the CNAME and a single Redirects to TXT record, and confirm the behaviour end to end before migrating anything that matters. If you'd rather manage redirects through a hosted interface with click tracking, a link shortener such as Bitly is the more conventional route.
How do I set up a redirect with redirect.name using DNS records?
Set up a redirect by pointing your hostname at redirect.name's server with a CNAME, then adding a TXT record at _redirect. that describes where to send visitors. There is no account or dashboard — your DNS provider holds the configuration.
The two records you need
| Record | Type | Name | Value |
|---|---|---|---|
| Pointer | CNAME | go.example.com. |
alias.redirect.name. |
| Rule | TXT | _redirect.go.example.com. |
Redirects to https://example.com/ |
The _redirect. prefix is required because a TXT record and a CNAME cannot sit at the same name. If your provider can't flatten a CNAME at the apex (sometimes called ALIAS or ANAME), use an A record pointing to 45.55.126.223 instead.
Writing the rule
The TXT value is the rule, written in plain English. Useful forms:
Redirects to https://example.com/— 302, catch-allRedirects permanently to https://new.example.com/— 301, for moves that won't be undoneRedirects from /api to https://api-docs.example.com/— path-specificRedirects from /blog/* to https://blog.example.com/posts/*— wildcard, where*in the path replaces*in the destination
You can add several TXT records at the same name. Path-specific rules are evaluated first; catch-all rules only apply when nothing else matches. Destinations may use http://, https://, ftp://, mailto:, magnet:, or an absolute path.
A concrete example
Suppose you run documentation at docs.example.com and want /api to send readers to a separate API reference while everything else goes to the main docs site:
- CNAME
docs.example.com.→alias.redirect.name. - 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/
Wait a minute or two for propagation, then visit the hostname to confirm.
Trade-offs to weigh
This approach suits people who already manage DNS and want redirects without hosting a server or creating an account — useful for short links, domain moves, and path routing. The cost is that rules live in DNS records, so editing means going through your provider, and propagation delay applies to every change. If you need logging, analytics, or many frequently edited rules, a hosted redirect service or a small web server will be easier to operate.
If you don't already control the domain's DNS, start by confirming your provider supports CNAME records at the subdomain you plan to use, and check whether it offers CNAME flattening for an apex domain before choosing between the CNAME and A record options.
What redirect rule syntax can I put in a TXT record?
Put a plain-English rule in the TXT record's value, and the service reads it at request time to decide where and how to send the visitor. The record name must live under _redirect. (for example, _redirect.go.example.com), because a TXT record can't coexist with the CNAME at the same name.
The rule patterns
| TXT value | Behavior |
|---|---|
Redirects to https://example.com/ |
302 (temporary) to that URL |
Redirects permanently to https://new.example.com/ |
301 (permanent) |
Redirects from /api to https://api-docs.example.com/ |
302 only when the request path matches |
Redirects from /api to https://api-docs.example.com/ with 308 |
Same match, explicit status |
Redirects from /blog/* to https://blog.example.com/posts/* |
Wildcard: what * captures in the path replaces * in the destination |
Status codes and destinations
You can name a status explicitly — 301, 302, 307, or 308 — instead of relying on the wording. Destinations accept http://, https://, ftp://, mailto:, magnet:, or an absolute path.
How multiple rules interact
You can add several TXT records at the same name. Path-specific rules (Redirects from …) are tried first; a catch-all rule (Redirects to …) applies only when no path rule matches. That makes the docs example work: /api goes to the API docs, and everything else falls through to the main docs site.
Practical decision points
- Use
301/308only for moves you won't undo, since browsers cache permanent redirects aggressively. For testing, start with302. - Prefer
308over301when the redirect must preserve the request method and body. - Wildcards are for path forwarding, not query strings — plan the destination path carefully.
Next step: write your rule, add it as a TXT record at _redirect.<your hostname>, wait for DNS to propagate, then test with curl -I to confirm the status code and Location header before announcing the change.
What is the difference between a permanent and temporary redirect on redirect.name?
On redirect.name, the difference is the HTTP status code the service returns, and that code tells browsers and search engines whether to treat the move as lasting.
- Temporary (302 by default): the redirect is not cached as permanent. Use it while testing, during maintenance, or for short campaigns where the destination may change.
- Permanent (301): browsers and search engines are told the move is lasting. Use it when an old URL will never serve content again, such as a rebranded domain or a retired path.
The service also supports explicit statuses: 301, 302, 307, and 308. The 307 and 308 variants preserve the original request method, which matters for non-GET traffic; 301 and 302 may be rewritten to GET by some clients.
| Rule wording | Status | Practical use |
|---|---|---|
Redirects to |
302 | Temporary catch-all, safe to change |
Redirects permanently to |
301 | Permanent moves, SEO consolidation |
Redirects from ... to ... with 308 |
308 | Permanent move that must keep POST/PUT methods |
A concrete scenario: you are migrating old.example.com to new.example.com. Start with Redirects to https://new.example.com/ while you verify links and analytics. Once the migration is stable, change the TXT record to Redirects permanently to https://new.example.com/. Because DNS is the source of truth, the change is just a TXT edit; no dashboard or account is involved. Note that permanent redirects can be cached aggressively by browsers, so test with a temporary rule first.
Next step: decide based on reversibility. If you might undo the move, use a 302. If the old address is gone for good, use a 301, or 308 when method preservation matters.
How do wildcard and path-specific redirects work on redirect.name?
Path-specific rules are checked first, and wildcard rules replace * in the destination with whatever * matched in the request path.
How the two rule types differ
| Rule type | TXT value shape | When it applies |
|---|---|---|
| Path-specific | Redirects from /path to https://... |
Only when the request path matches |
| Wildcard | Redirects from /path/* to https://.../* |
When the path matches the pattern; * is substituted into the destination |
| Catch-all | Redirects to https://... |
Only if no path-specific rule matches |
Because path-specific rules are tried first, a catch-all acts as a fallback rather than an override. Multiple TXT records at the same _redirect. name let you combine these: one rule for /api, another catch-all for everything else.
Concrete example
For docs.example.com, you could set:
_redirect.docs.example.com.→Redirects from /api to https://api-docs.example.com/_redirect.docs.example.com.→Redirects to https://docs.example.com/
A request to /api goes to the API docs; every other path goes to the main docs site. For wildcard forwarding, Redirects from /blog/* to https://blog.example.com/posts/* sends /blog/hello to https://blog.example.com/posts/hello.
Practical notes
- The
_redirect.prefix is required because TXT and CNAME records cannot share the same name. - Status codes are explicit when you use forms like
Redirects from ... with 308orRedirects permanently tofor a 301. - Destinations can include
http://,https://,ftp://,mailto:,magnet:, or an absolute path.
Next step: decide whether your redirect is a one-off path move or a pattern-based rewrite. If the destination needs to preserve part of the incoming path, use a wildcard; if only one exact path changes, use a path-specific rule and add a catch-all for everything else.
Can redirect.name handle redirects to mailto, magnet, or other non-HTTP destinations?
Yes. redirect.name's TXT-record rules explicitly allow destinations using http://, https://, ftp://, mailto:, magnet:, or an absolute path. So a rule like Redirects to mailto:[email protected] is a supported use, not a workaround.
H3 What this is practical for
- mailto: A hostname such as
hi.example.combecomes a short, memorable contact address that immediately opens the visitor's mail client, useful on business cards or slides where you don't want to print a full email address. - magnet: A short link can hand off to a BitTorrent client instead of a web page, which suits sharing a torrent identifier without pasting the long magnet URI.
- ftp: Legacy but still occasionally needed for pointing at an old file server.
- Absolute paths:
Redirects to /pricingkeeps the redirect on the same host, handy when you only want to change the path.
H3 Trade-offs to weigh
Non-HTTP destinations are only as reliable as the visitor's software. A mailto: link does nothing useful if no mail handler is registered; a magnet: link depends on a torrent client being installed and may show a browser prompt first. Because the redirect is issued by redirect.name's server based on your TXT record, the visitor's browser still has to hand off to the external application — you cannot control that step. Also note the _redirect. prefix is required, since a TXT record and the CNAME at the same name cannot coexist.
H3 A concrete next step
Decide whether you need a catch-all or a path rule first. Path rules (Redirects from /path to ...) are evaluated before catch-alls (Redirects to ...), so you can send /api to a set of API docs while everything else goes to your main site. Start with one TXT record, wait a minute or two for DNS to propagate, and test the hostname in a browser before adding more.
If you want to compare approaches, DNS-based redirects sit alongside services like Cloudflare (which offers redirect rules at the edge) and Namecheap (whose DNS panel supports similar records). The distinguishing point here is that redirect.name has no account or dashboard — your DNS provider remains the single source of truth.
User reviews (0)