Redirect.pizza

Operated by Redirect.pizzaOperational

Ensures redirect destination URLs are reachable.

What Redirect.pizza does

Redirect.pizza's destination monitor checks every hour that the destination URL behind a customer's redirect is still reachable, since a working redirect pointing at an unreachable destination still shows users an error. Failures trigger alerts in the dashboard and summary emails, and rechecks can be triggered manually. Requests identify as "Mozilla/5.0 (compatible; redirect.pizza/1.0; +https://redirect.pizza/destination-monitor)" and come from probes in multiple geographic locations to avoid false positives from geolocation-based blocking. IP ranges are published in JSON and text formats under redirect.pizza/.well-known/, and every request carries RFC 9421 HTTP Message Signatures for verification.

How to identify Redirect.pizza

Temso identifies Redirect.pizzatraffic by matching the request's User-Agent header against this pattern. User-agent strings can be spoofed, so treat a match as an indication, not proof.

redirect\.pizza

Redirect.pizza FAQ

What is Redirect.pizza?

Redirect.pizza is a redirect management service whose destination monitor checks hourly that the destination URLs behind its customers' redirects are reachable, alerting the redirect owner when they are not. Its requests identify with the user agent "Mozilla/5.0 (compatible; redirect.pizza/1.0; +https://redirect.pizza/destination-monitor)".

Can I block Redirect.pizza with robots.txt?

The documentation does not mention robots.txt; the monitor is a reachability checker that requests destination URLs configured by redirect.pizza customers rather than a content crawler. To control its access, you can allow or block traffic by its user-agent string or by the IP ranges published at redirect.pizza/.well-known/ips.json and ips.txt, which are subject to change.

About Operational Bots

Monitoring, security scanning, link previews, webhooks, and feed fetchers: the utility traffic that keeps integrations and shared links working.

Most of this traffic is service-critical or user-triggered. Webhooks and previews don't follow robots.txt, and blocking them tends to break things you rely on.

See which bots visit your site

Temso helps marketers track every AI crawler and bot that visits your site, and runs regular audits to make sure your website is always performing at its full potential.

Explore Website Audits
Website audit dashboard showing bot visits, citation-bot visits, and a table of AI bots crawling the site