redirect.name

DNS-based URL redirects — no server, no signup, no dashboard.

How it works

Point a hostname at alias.redirect.name (or the IP), then add a TXT record with your redirect rule. That's it. The service reads your DNS and redirects visitors.

---

Setup

1. Add a DNS record pointing your hostname to redirect.name:

   # Preferred: CNAME or ALIAS record
   CNAME  yoursubdomain.example.com  alias.redirect.name
   
   # Fallback: A record (use if your DNS provider doesn't support CNAME at apex)
   A      yoursubdomain.example.com  45.55.126.223

2. Add a TXT record on the same hostname with your redirect rule:

   TXT  yoursubdomain.example.com  "Redirects to https://example.com/"

3. Wait for DNS to propagate (usually a few minutes), then visit your hostname.

---

Redirect rules

The TXT record value is your redirect rule. All matching is case-insensitive.

TXT record value	Behavior
Redirects to <url>	302 redirect to URL
Redirects permanently to <url>	301 redirect to URL
Redirects temporarily to <url>	302 redirect to URL (explicit)
Redirects from <path> to <url>	302 redirect when path matches
Redirects from <path> to <url> with 301	Redirect with specified status code (301, 302, 307, or 308)
Redirects from /path/* to https://example.com/*	Wildcard: * in destination is replaced with the matched portion

You can add multiple TXT records to the same hostname. Specific path matches take priority over catch-all rules. Rules are evaluated in order; the first match wins.

---

Examples

Simple redirect — send all traffic to a new URL:

TXT  go.example.com  "Redirects to https://www.example.com/"

Permanent redirect — tell browsers and search engines this is final:

TXT  old.example.com  "Redirects permanently to https://new.example.com/"

Path-based routing — redirect a specific path, let others fall through:

TXT  docs.example.com  "Redirects from /api to https://api-docs.example.com/"
TXT  docs.example.com  "Redirects to https://docs.example.com/"

Wildcard forwarding — preserve the path suffix:

TXT  links.example.com  "Redirects from /blog/* to https://blog.example.com/posts/*"

---

HTTPS

TLS certificates are provisioned automatically via Let's Encrypt on the first request to a new hostname. The very first HTTPS request may be slow (a few seconds) while the certificate is issued. Subsequent requests are fast.

---

Source

The server is open source: github.com/frolic/redirect.name