Changelog

We've added a dedicated SSO login button to the login screen. Previously, we automatically detected the email address domain to switch to SSO mode. This behavior still exists; this dedicated SSO button makes it clearer to users that SSO may be available for them.

A new destination variable `{referrer}` is now available. This allows you to pass the incoming referrer directly into your destination URL, making it easier to build more dynamic redirect behavior.

You can now configure the `Referrer-Policy` header for your redirects. This gives you more control over how much referrer information is shared with destination websites, helping you balance privacy and analytics needs. You may set this onteam level for all redirects, and overrule on hostname level where needed.

You can now upsert redirects through both the API and import functionality. Instead of manually fetching the redirect to determine whether it requires creation or updating, existing redirects are updated automatically when a match is found. This makes bulk updates and automated workflows much easier to manage. Set the `upsert` boolean to `true` on the POST /api/v1/redirects call.

We fixed several issues affecting Azure DNS when working with large zones. Record syncing and lookups are now more reliable, improving overall stability for domains with many entries.

We now automatically detect SYN flood attack patterns and temporarily block the offending IPs in real-time via our centralized RTBH. This helps reduce unnecessary load on the platform and keeps your redirects performing reliably, even under malicious traffic.

Our regex parser has been optimized to handle complex redirect rules more efficiently. Matching is now faster and more consistent, especially for teams with large or advanced configurations.

We've made several upgrades to our DDoS protection. This includes adding more infrastructure resources, increasing available L3 bandwidth, and introducing an additional fallback BGP provider. Together, these changes improve resilience and ensure more stable performance during traffic spikes or attacks in L3 scenarios.