Changelog

We've added a live indicator to Analytics to show how many hits your redirects got in the past 5 minutes.

We now recommend setting up a root path redirect if only path-specific redirects are found for a given hostname. This ensures users will always be redirected, even though a specific path might not be configured.

We've made additional quality-of-life improvements to our inline help documentation when a DNS change is required:

• Detect common forwarding services based on IP address and inform that these first need to be disabled.
• Improved copy.
• Added label to some IP addresses if they are communicated differently in the DNS zone editor.

On top, we've been also been busy on other segments:

• Added better error handling to our tester to inform you
• Improved the performance of the SSL certificate installation.
• Some mobile styling improvements in-app.

When we detect a DNS error, we now show inline documentation under the "DNS" button to help out with these settings in a step-by-step guide.

It's now possible to define custom HSTS values. This includes max-age, include subdomains and the preload attributes.

By allowing the max-age to be configurable, you can safely introduce HSTS across your domains by setting a low limit, see what the impact is and increase the max-age over time.

You may define a default on team level and overrule per domain like before.

Read more here.

We've rewritten our API documentation in OpenAPI 3.1 spec and added additional descriptions/examples to improve the experience of implementing our API.

Feedback on our API documentation is always welcome!

We always put privacy first. We've added support to honor the DNT (Do-Not-Track) header on our redirect network. When a visitor lands on a redirect and the DNT header is set, we only count the hit but do not save any visitor information.