Changelog

We've introduced the {domain.subdomains.*} destination variable, which is especially useful when working with subdomains and only needing specific parts of the source domain.

For example, if you want to use the result of a wildcard in the destination's subdomain:

Source: *.test.example.com
Destination: {domain.subdomains.0}.destination.com

This allows you to dynamically map subdomains from the source to your desired destination.

You can now configure CNAME records, direct IP URLs, and even geolocation directly from your Dedicated IP detail screen. Setup is available immediately after activation—no need to contact support.

You can now limit API token access using tags! This means you can create multiple tokens, each with its own specific purpose and access level in your redirect.pizza account. It’s a great way to keep things secure and organized, especially when managing multiple use cases in a single account.

Automatically fetches the destination’s og:image for the frame page. When sharing the source URL on social media, the destination’s og:image is displayed for a seamless integration.

If multiple regexes are defined under a single source, multiple regexes can match the incoming URL. We now automatically sort the regexes list under the source based on the number of unique path segments (i.e. number of slashes in the path). We will automatically try to match the regex with the most slashes first, followed by those with fewer slashes.

This helps when defining regexes like test/(.*) and test/(.*)/(.*), where the second regex is more specific, and is commonly the one that we first want to match on.

We’ve added two new filters on the redirect page, making it easier to locate specific redirects.

Source filter
You can now filter by source, either by specifying the full domain or including the path. This is an exact filter, allowing you to quickly find the precise source you’re looking for.

Examples:

• source:redirect.com
• source:redirect.com/path
• source:redirect.com/path/

Destination filter
You can now search within the destination URL. This filter returns results that partially match your search query, making it easier to identify redirects by their destination.

Examples:

• destination:destination.com
• destination:destination.com/path

We’ve resolved an issue with the destination monitor. It now runs immediately after changing the URL and provides instant feedback — no page refresh required.

When using the frame redirect type, we automatically fetch the destination's title & favicon information. We now automatically update these details daily for all frame redirects, to ensure the page context is always up-to-date.