We've sped up DNS verification for newly added domains.
New hostnames are checked more often in the first hour, so a correct DNS change is picked up sooner and your redirect can go live without waiting on the slower retry schedule.
We've updated the TLS 1.2 cipher suites on the edge network.
HTTPS redirects now follow Mozilla's Intermediate profile, which matches NCSC-NL guidance: AES-GCM and ChaCha20-Poly1305 only. CBC and SHA-1 MAC suites are no longer offered. TLS 1.3 is unchanged.
Your redirects work the same way. Current browsers and clients are unaffected. We still hold an A+ rating from Qualys SSL Labs on every plan. Read more in the automatic HTTPS article.
You can now import redirects through the API, using the same columns as the dashboard importer. Send a JSON array or a CSV string to POST /api/v1/redirects/import, then poll the import status endpoint for progress.
Re-importing an existing source now updates the destination instead of leaving you to edit it by hand. That makes bulk migrations and ongoing syncs much easier to run. Details are in the API docs.
We've added a new edge node in Warsaw, Poland.
Visitors in Central and Eastern Europe now have a closer hop, which keeps redirects fast in the region. See the full map on the network page.
We've released version 0.3.0 of the official Terraform provider.
API requests now retry on HTTP 429 and honor Retry-After, so parallel applies back off instead of failing immediately. Registry docs and examples also use the published enflow/redirectpizza source address. Read more in the Terraform provider article.
Email forward logs now live in your account, so you can see delivery status, subject, and related events without leaving redirect.pizza.
The same logs are available through the API at GET /api/v1/email-forwards/logs. Open any email forward to get started, or see the API docs.
Same pizza, new box. redirect.pizza has a new logo, a new color palette, and a redesigned website and app. The ingredients are the same, and nothing changed about how your redirects work. Here's what did change.
The pizza slice stays. We'd never drop it. It's now a bolder, simpler wedge on our yellow tile, next to a deep plum that replaces pink as the main color. Plum carries the headings, buttons and hero sections, yellow is for the moments that matter, and there's a lot more white space in between. Calmer, easier to read, and still unmistakably us.
Every public page has been rebuilt on the new design: a new homepage, feature pages with live illustrations of automatic HTTPS and automatic DNS, a clearer pricing page (same plans, same prices), a dedicated enterprise section, and a cleaner reading layout for support articles and this changelog.
Inside your account the new colors carry over to headings, buttons, tables, charts and illustrations. We deliberately kept the layout as it was, so your redirects, domains and settings are exactly where you left them.
Everything under the hood. The edge network, your DNS records, the API, certificates and every redirect you've set up are untouched. There's nothing you need to do.
A redesign this size always leaves a few crumbs. If something looks off, tell us through the chat in the bottom right corner and we'll fix it quickly. And if you like the new look, we'd love to hear that too!
You can now manage redirect.pizza from Claude Code, Cursor, VS Code, and other MCP clients. It's the same team, the same API token, and the same scopes as the REST API.
Create a token with the mcp:use scope on the API/MCP page, copy the sample config for your client, and you're set. Read more in the MCP support article.