Matching's matching options allow the ability to set-up complex redirect set-ups.

We'll first look in the database to lookup a redirect that matches the full URL. For example, a request for comes in. We'll search for that and if it exists we can be sure that the destination is the one defined on that redirect! If not, we'll continue down the line.

  1. Exact match (case sensitive) (
  2. Exact match (case insensitive) (
  3. Path without query string (
  4. Without path (

If non of these conditions match, we cannot be sure where to redirect to and present a 404 page.

URI Forwarding = no preference on root match

If a request comes in without a path defined ("homepage"), we'll prefer the source first that has URI Forwarding disabled. This enables the following:

  • Redirect 1: -> - URI Forwarding = yes
  • Redirect 2: -> - URI Forwarding = no

If a request comes in for ("homepage"), we'll redirect that request to Every other request will go to$PATH$ as defined on the incoming source.

More articles

Can’t find the answer you’re looking for?

E-mail us
Start a chat
Online 9:00 - 21:00 CEST
Available with Enterprise
Pricing Background

Domain redirects delivered hassle-free


Making it
too easy?

Automatic HTTPS

We automatically set up an SSL certificate for your domains. This means redirection with HTTP & HTTPS works out-of-the-box.


Who is still visiting that old domain? Gain insight with detailed statistics and find out where hits are coming from.

Email Forwarding

Setup your domains to automatically forward email. All your needs for migrating your domain in one platform.

Team Support

Doing things all by yourself isn't much fun. Invite your co-workers to manage the redirects and work as a team.


Connect your software to automatically create redirects via our API. Automate the heck out of it.

Import & Export

Manage your redirects without losing precious time. Import and export redirects in our UX-friendly interface