Changelog

We've added the page title & page favicon to the 'frame' redirect type. This will ensure a title tag is set and the appropriate favicon is loaded.

We are proud to announce our broken destination monitoring feature!

With this feature enabled we'll periodically check all your redirect destinations. If unreachable, we'll list it in your dashboard and report a summary of broken destinations in the Summary email.

This feature is available from the Pro plan and up.

We've added API support for managing email forwards.

You may create, update & delete email forwards via the respective API calls.

See the updated documentation here.

Today we've launched our new summary email feature! 

The summary email is being triggered when there are changes detected on your team account (new verified hostnames, unverified hostnames etc.)

You can change the frequency of the summary email to monthly, weekly or even daily.

We've added the GET /api/v1/team endpoint to query your team's quota.

See the updated documentation here.

• You can now view analytics per day. Click on a specific day in the chart to view the statistics of that day per hour.
• We now show a comparison percentage compared to the previous period for your number of hits, active sources & active destinations.

We've added NameSilo DNS support to our Automatic DNS feature. This will automatically set the required DNS entries via the NameSilo API.

It is now possible to create a QR code that you can use for marketing purposes. The QR code generator is publicly available and free to use!

By using it in combination with redirect.pizza, you can create powerful dynamic QR codes by changing the destination when needed. No need to print it again!

Check it out here!

Added by popular demand: it's now possible to set-up 307/308 redirects. These advanced redirect types are mostly the same as the already existing 301/302 redirect types. We recommend using these new types only when there is a specific use case for them. Not sure which one to use? We recommend sticking with 301/302 redirects.

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.

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.

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.

• Lowered the interval between DNS checks. Domains are checked at least once a day, while newly added domains multiple times per hour.
• Improved the SAML SSO invite flow
• Detect redirect loops in our tester