For hosting guide See HOSTING.md and CHANGES.md
This service forwards domains using HTTP(s) redirects.
Example scenarios:
- Forward non-www to www domains or vice versa
- Forward old domains to new domains
Why using this service?
- No coding required
- No hosting required
- No registration required
- Completely anonymous
- Completely free
How does it works?
- Point your domain to us using CNAME or A/AAAA records
- Tell us where to forward using TXT records
- We handle HTTPS certificates for you
To forward from www.old.com to old.com, add these records to your DNS:
www.old.com IN CNAME r.forwarddomain.net
_.www.old.com IN TXT forward-domain=https://old.com/*
Because CNAME can't be used in apex domains, you can use A/AAAA records.
To forward from old.com to new.net, add these records to your DNS:
old.com IN A 167.172.5.31
_.old.com IN TXT forward-domain=https://new.net/*
The star * at the end tells us that the remaining URL path is also forwarded to the destination URL.
If you use Cloudflare or any DNS which supports CNAME Flattening, you still can use CNAME records pointing to
r.forwarddomain.net. It's recommended to use CNAME records rather than A/AAAA records.
You can choose the type of redirection you want to use by declaring the http-status value:
www.old.com IN CNAME r.forwarddomain.net
_.www.old.com IN TXT http-status=302;forward-domain=https://old.com/*
Only the HTTP status code 301 and 302 are supported. By default it's 301, which is permanent redirection. Set to 302 if you want temporary redirection, it has effect on search engine indexing.
Forwarding domains should be easy to setup.
I use this myself for domcloud.io.
This service uses Google's Public DNS Resolver.
Once first accessed, values will be cached for a day.
For right now there's no way to flush the cache sorry.
It only slow at first time because it has to sign HTTPS certificates.
IPv6 record is added in r.forwarddomain.net so subdomain redirects will simply work with IPv6. We don't guarantee that its IPv6 address will be persistent though. See #2 for apex domains setup.
We only keep caches of DNS records and SSL certs. This also means we can see how many users and what domains are using our service from the software cache, but that's all. We don't keep log traffic nor keep any user data anywhere on our server.
Star our repo and spread the word, please :)
Additionally, you can also help us cover hosting costs.
Things in package.json. I also borrow code from zbo14/certnode.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.