Changelog

New features, improvements, and bug fixes as we ship them.
RSS

Tester in the sources list

Improvement

DNS help improvements

Improvement

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.

Add inline documentation to DNS errors

Improvement

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.

HSTS options customizable

New feature

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.

HSTS options customizable

API documentation rewrite

Improvement

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!

DNT (Do-Not-Track)

New feature

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.

Infrastructure move

Improvement

We are very happy to report that we've moved redirect.pizza and it's API to our high-availability managed hosting cluster. This means even better stability and performance for you to enjoy!

This move also ensures that we have better options to scale up our infrastructure needs based on demand in the future.

Legacy redirects migrated

Improvement

We've migrated our legacy infrastructure over to the codebase of our new edge network. This ensures we only have a single redirector codebase to maintain and will ensure that legacy users have access to the latest features.

Users are still requested to change over the IP address, as the legacy IP space is scheduled to be phased out. Read more here.