Table of Contents

The redirector is a special feature provided by DNSimple that you can use to redirect HTTP requests sent to a host name to a different URL.

This feature can be used, for example, to redirect the www version of a domain to the non-www hostname. Another use case is to redirect a secondary domain you purchased to the main domain without pointing it to any web hosting service.

This feature can’t be used to redirect from one protocol to another protocol on the same host name. For example, you can’t use it to redirect from to To perform a redirect from HTTP to HTTPS on the same host, you’ll need to implement the redirection inside your application. If you host on Heroku, this guide explains how to perform the redirection.

Configuring a redirect

To configure a redirect, use the special URL record, available in the record editor.

This article contains specific information on how to add, update, and remove a URL record in DNSimple.

Redirecting status code

The redirector sets a 301 status code. The code is not configurable, and it’s not possible to return a 302 temporary redirect using the URL record.

HTTPS redirects

The redirector doesn’t support HTTPS, so you can’t redirect an HTTPS request.

It’s not possible to use the URL record to redirect the www to the non-www version of your domain with HTTPS. You can redirect, but not

Take a look at the article redirector and HTTPS for additional information and a list of alternative solutions.

URL to URL redirects

URL to URL redirects can’t be done with our URL record. Only domains or subdomains can be redirected to complete URLs.

The following redirect will not work, because you can’t add a URL to the name part of the URL record. to

This would work, because you can add a URL record for to

Any path or query information passed by the user is passed to the resulting URL. If you set up a redirect from to, when the user goes to they’ll be redirected to

Wildcard URL redirects

You can configure a wildcard redirect using the same conventions of a DNS wildcard record. However, the target can’t contain any wildcard references.

# Valid redirects
* to
* to

# This will redirect to the hostname
* to *

The wildcard pattern can only be on the left outermost level.

# Valid redirects
* to

# Invalid redirects
foo.* to

Match-based URL redirects

The redirector doesn’t support redirect targets that include a back-reference (match) to the redirect source. For example, the following redirects won’t work:

* to$1
* to $