A working redirect is only half the story. If the destination it points to is down, your visitors still end up on an error page. Broken destination monitoring checks your destinations for you and warns you when one stops responding. Available from the Pro plan and up.
Enabling monitoring
Turn on destination monitoring on the Settings page of your team. It then applies to all destinations.

You can override the team setting for an individual destination, for example to exclude a destination that deliberately blocks automated requests.

How it works
We check every monitored destination once an hour. A broken destination is flagged in your redirects overview and included in your summary email.

Open the redirect to see the details of the last check, including the status code we received. Press the icon under Last checked at to run a new check right away.

The monitoring status is also available as a destination variable, so a dynamic destination can send visitors elsewhere while a destination is down.
Probe locations
Checks run from multiple probes in different regions. A destination is marked as up as soon as any probe receives a successful response. This prevents false alarms for destinations that block traffic from certain regions, for example a site that's reachable from the US but blocked in the EU.
Allowlisting our checks
User agent
Monitoring requests identify themselves with this user agent:
Mozilla/5.0 (compatible; redirect.pizza/1.0; +https://redirect.pizza/destination-monitor)
IP addresses
Our outbound IP addresses are published in machine-readable form:
- redirect.pizza/.well-known/ips.json or ips.txt: all addresses
- ips-v4.json and ips-v6.json: IPv4 or IPv6 only
These addresses can change. If you allowlist them, fetch the list periodically rather than copying it once.
Request signing
Every monitoring request is signed according to the HTTP Message Signatures standard (RFC 9421) and carries Signature and Signature-Input headers. Verify them against our public key to be certain a request came from us. The key is published at redirect.pizza/.well-known/http-message-signatures-directory.