How it works?
Update three DNS records on the domain you want to forward, wait for the DNS to propagate — the SSL certificate will be issued automatically the first time your domain is reached — and it's live.
@ IN AAAA 2a01:4f8:c0c:b702::1
fwd.@ IN TXT forward-domain=https://example.com
Replace https://example.com with the destination you want visitors to be redirected to. Propagation is usually quick; the first request to your domain will trigger certificate issuance, so it can take a few extra seconds the very first time.
Why use it?
Common scenarios
- Redirect http: to https: without browser warnings
- Forward a non-www domain to www, or vice versa
- Forward an old or retired domain to its replacement
- Forward typo domains or alternate TLDs to the correct one
FAQ
Is it really free?
Yes. Point your domain to us using the A (IPv4), AAAA (IPv6) and TXT records above and the redirect just works — no plans, no limits on basic usage.
How does the HTTPS certificate get issued?
Once your DNS records are in place and your domain is visited for the first time, an SSL certificate is requested and stored in the background. Nothing to configure on your end.
Why does it load slowly the first time?
The very first request to a newly configured domain has to wait for the SSL certificate issuance to complete. Every request after that is fast.
How can I check my DNS records are configured correctly?
Use our DNS checker to validate your A, AAAA, and TXT records against Google's public DNS resolver, the same one this service checks against.
How about IPv4?
Update the A record shown above alongside your AAAA record and IPv4 traffic is handled automatically.
How about IPv6?
Add the AAAA record shown above alongside your A record and IPv6 traffic is handled the same way as IPv4.
Can I use a custom HTTP status code?
Yes. Add http-status=302 to your TXT record value for a temporary redirect instead of the default permanent (301) redirect — this matters for how search engines treat the change.
What data do you keep?
Only what's required to operate the service: a cache of the DNS records you've published and the matching SSL certificate stored on the server. We don't log traffic or collect visitor data.
Can you guarantee uptime?
We keep the service available on a voluntary and best-effort basis. As with any free service, uptime isn't contractually guaranteed and comes without warranty.