Changelog

We are now supporting Apple Pay and Google Pay, thanks to our payment partner Paddle. Fast and secure subscriptions just got easier!

We’ve added a segments destination variable from 0 to 9 to be used as either a replacement tag or in dynamic destinations. This can be helpful when using partial path matching and then forwarding a specific path element to the destination.

For example, you have a request like example.com/test1/test2. In this case, you always want to use the second path segment. You can now use the segments variable: {segments.1}. The first segment of the path can be found under {segments.0}.

We’ve added a new API endpoint: apply automatic DNS. This endpoint can be called through a POST call to trigger the automatic DNS changes if configured in the account.

Each domain resource object now includes an automatic_dns resource. This indicates whether Automatic DNS is available for this domain and, if so, provides the URL to which the POST call should be sent to apply the DNS changes.

Read more about this change here.

We're happy to announce it's now possible to serve robots.txt files on your domains!

This can help block (bad) bots and get's you back in control how you want your domains to be indexed.

Serveral options are available:

• No robots.txt (default)

• Explicitly allow all

• Block bad bots

• Disallow all

• Custom (Dedicated IP only)

Read more here.

We now include a monitoring destination variable to automatically steer traffic based on the destination’s status.

This can be particularly beneficial when your website is unavailable and you need to redirect your users to an alternative location.

For example, you can configure a dynamic destination using the expression monitoring.status == 'down' to lead visitors to the emergency landing page informing them that the website will be back up shortly. Once the website is back online, users are automatically redirected again to the primary destination.

We've made some improvements to the add/edit redirect page. Tags are now under the 'Add tag' button. And for an easier experience, you can click 'Add note' to add notes while you're creating or editing a redirect. This makes everything a bit more streamlined.

You can now add notes on your redirects. This can be helpfull to add reasoning why a redirect is needed and why it’s redirecting to a specific destination.

Notes can be added/maintained via the API as well. View our updated API docs here.

We've added the ability to specify regexes to the 'alias' part of the email forward. This allows you to create complex email forwarding rules. You can match and pass along the capture group to the email destination.

Read more here