Does redirect.name support HTTPS and apex domains?
Updated
Yes to both, with one caveat on each. HTTPS works because redirect.name serves your redirect from its own server, so the TLS certificate belongs to that server rather than to your DNS provider. Apex domains work as long as your DNS provider supports CNAME flattening, or offers an ALIAS or ANAME record type; if it doesn't, you point an A record at 45.55.126.223 instead.
HTTPS: what actually happens
redirect.name is a DNS-based redirect service. You don't run a server, and there's no signup or dashboard — your DNS provider holds the configuration, and redirect.name reads it at request time.
That matters for HTTPS because the redirect is issued by redirect.name's server, not by your DNS host. Two practical consequences:
- Your hostname needs to resolve to redirect.name's server (via the CNAME to
alias.redirect.name). Once it does, visitors hittinghttps://go.example.comreach that server and get redirected. - You don't manage a certificate for the redirecting hostname yourself. The TLS termination happens on the redirecting side, so you're not provisioning a cert for
go.example.comjust to bounce traffic elsewhere.
The destination can be any of http://, https://, ftp://, mailto:, magnet:, or an absolute path — so an HTTPS source redirecting to an HTTPS destination is the ordinary case, not a special one.
Apex domains: CNAME flattening, ALIAS, or A record
The standard setup is a CNAME:
| Type | Name | Value |
|---|---|---|
| CNAME | go.example.com. | alias.redirect.name. |
That works cleanly on a subdomain like go.example.com. The problem is the apex — example.com itself. DNS rules generally don't allow a CNAME at the apex alongside the other records a zone needs (SOA, NS, and often MX).
Three ways out, in order of preference:
- CNAME flattening. Some DNS providers resolve the CNAME target themselves and serve the resulting address as if it were an A record. If your provider offers this, use the CNAME above at the apex and you're done.
- ALIAS or ANAME records. These are provider-specific record types that behave like a CNAME at the apex. If your provider offers one, it's the same idea — point it at
alias.redirect.name. - A record. If neither is available, point an A record at
45.55.126.223. This is the documented fallback and works anywhere, but it hardcodes an IP address, so if that address ever changes you'd have to update your record.
So the honest answer on apex support is: yes, but the mechanism depends on what your DNS provider allows. Check for flattening, ALIAS, or ANAME first; fall back to the A record only if none exist.
The TXT record is separate from all of this
Whichever way you point the hostname, the redirect rule itself lives in a TXT record at a _redirect. prefixed name:
| 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 — so the rule sits one level down from the hostname it governs.
This split is worth remembering when debugging: the CNAME (or A record) controls whether traffic reaches redirect.name at all, and the TXT record controls where it goes once it arrives. A redirect that isn't working is often a problem in the first half, not the rule syntax.
Setup steps and what to expect
- Add the CNAME (or ALIAS/ANAME, or the A record at the apex) pointing your hostname at
alias.redirect.name.or45.55.126.223. - Add a TXT record at
_redirect.<your-hostname>with a rule such asRedirects to https://example.com/. - Wait for DNS to propagate — typically a minute or two — then visit your hostname.
If the redirect doesn't fire, the usual culprits are propagation not finished, a missing _redirect. prefix, or an apex record type your provider silently rejected.
Rule syntax, briefly
The TXT value is written in plain English. Useful forms:
Redirects to <destination>— 302Redirects permanently to <destination>— 301Redirects from <path> to <destination>— 302, only when the request path matchesRedirects from <path> to <destination> with 308— explicit status; 301, 302, 307, and 308 are all availableRedirects from /path/* to https://example.com/*— wildcard, where whatever*matched in the path replaces*in the destination
You can add multiple TXT records at the same name. Path-specific rules are evaluated first; a catch-all rule only applies when no path rule matches. That ordering is what lets you send /api to one place and everything else to another:
| 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/ |
Choosing between the options
- Subdomain redirect, any provider: CNAME to
alias.redirect.name.— no tradeoffs. - Apex redirect, provider supports flattening/ALIAS/ANAME: use that record type; it stays portable if the underlying address changes.
- Apex redirect, no such support: A record to
45.55.126.223. Works everywhere, but you own the maintenance if the address moves. - Permanent move: use
Redirects permanently to(301) rather than the default 302, so browsers and crawlers treat it as permanent.