Broken destination monitoring

Keeping your redirects working is very important. But even if your redirect is working, and the destination isn't reachable, the user still get an error.

Broken destination monitoring helps by checking the destination to ensure it's reachable.

Destination monitoring can be enabled in your Team settings: (Pro plan and up)

Enable destination monitoring

You can also overrule the general Team setting for a specific destination:

Monitoring specific destination

If monitoring is enabled, we automatically check the destinations every hour. If a destination is broken you will see it on your redirects overview and we will notify you in the Summary email.

Broken destinationWhen you click on the specific redirect that has a broken destination, you can see more details about this. You can also trigger a 'Recheck' by clicking on the icon below 'Last checked at'.

Broken destination details

Probes locations

We monitor destinations using multiple uptime probes from different locations. Each probe checks the destination URL, and if any probe returns a successful response, we mark the destination as up.

This helps prevent false downtime reports for destinations that may block traffic based on geolocation. For example, a destination might be reachable from the US but blocked from the EU.

User agent allowlist

We'll send requests to your destination with the User Agent set to:

Mozilla/5.0 (compatible; redirect.pizza/1.0; +https://redirect.pizza/destination-monitor)

IP allowlist

To create an allowlist based on IP addresses, our outbound IPs may be found via the following link:

JSON format: https://redirect.pizza/.well-known/ips.json
.txt format: https://redirect.pizza/.well-known/ips.txt

To only include IPv4 or IPv6 addreses, you may specify the format:

https://redirect.pizza/.well-known/ips-v4.json
https://redirect.pizza/.well-known/ips-v6.json

Important note: these IP addresses are subject to change in the future!

Request signing

We sign every outgoing broken destination monitor request with the HTTP Message Signatures standard (RFC 9421). Each request includes a `Signature` & `Signature-Input` header. You can validate based on our public key below, that we're the originators of the request.

Our public key can be found at: https://redirect.pizza/.well-known/http-message-signatures-directory

More articles

Walkthroughs
GoDaddy: Forwarding with HTTPS support
Network Solutions: Forwarding with HTTPS support
Namecheap: Forwarding with HTTPS support
Hover: Forwarding with HTTPS support
TransIP: Forwarding with HTTPS support
Cloudflare: Forwarding with HTTPS support
Amazon Route 53: Forwarding with HTTPS support
NS1: Forwarding with HTTPS support
DigitalOcean: Forwarding with HTTPS support
Google Cloud DNS: Forwarding with HTTPS support
EuroDNS: Forwarding with HTTPS support
Azure DNS: Forwarding with HTTPS support
DNS Made Easy: Forwarding with HTTPS support
Freenom: Forwarding with HTTPS support
Mijndomein: Forwarding with HTTPS support

Can’t find the answer you’re looking for?

24 hours
E-mail us
support@redirect.pizza
Start a chat
Online 9:00 - 21:00 CEST
Phone
Available with Enterprise
Pricing Background
Domain redirects delivered hassle-free

Get started right away

  • Free plan
  • No creditcard required
Features

Everything
you need