Changelog

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

It is now possible to change the role of your team members. To do this, go to More -> Users and click on the desired team member. You can for instance create multiple owners for your team to manage by changing the role from 'Member' to 'Owner'.

• Improved the search on redirects

• Optimized importing speed

• Performance fixes all around

• Added an example import XLSX file

We’ve partnered up with GitHub as part of its Secret Scanning Program. This means that when an API token from redirect.pizza is pushed into a public repository, the API token is marked as compromised. You’ll receive an email and the API token will be automatically revoked.

See more here: https://github.blog/changelog/2022-06-09-redirect-pizza-is-now-a-github-secret-scanning-partner/

You can now force-check multiple domains to see if the DNS entries are correct. To use, go to Domains -> Select one or more domains -> Force check DNS

1. We've published the SAML SSO activation process in a support article.
2. The ACS & Entity ID per team was previously only available via support but can now be found on your Team Settings page via More -> Settings.
3. We've added a Service Provider initiated flow by detecting the domain of the email address automatically (previously SSO was IdP-initiator only)