RedirX bot

Seeing RedirX in your server logs? Our redirect checker requests URLs submitted to RedirX to check what happens after a site migration.

Identify redirect checks

The redirect checker sends this User-Agent header:

redirxbot/1.0 (+https://redirx.dev/bot)

A User-Agent can be copied by anyone; it is a log identifier, not proof that a request came from RedirX. This page does not publish a verified IP allowlist.

This identifier describes redirect verification and monitoring. Separate RedirX URL-discovery tools may use a different User-Agent and make different requests.

What the checker requests

  • It starts with a HEAD request. If the server returns 400, 403, 405, 406 or 501, it retries that URL with GET.
  • It examines HTTP status codes and Location headers, following redirects one hop at a time. It does not parse the page body or follow links found in HTML.
  • It records redirect destinations, status codes and failures to help the person running the migration check their approved mapping. A redirect check does not establish that Google has indexed a page.

The current URL-first matching workflow uses imported URL lists and confirmed examples. Matching those lists does not itself request page bodies from your site.

Request limits and access controls

Redirect checks have timeouts and a bounded hop limit. Each destination is checked against network safety rules; private and local network addresses and unsupported ports are refused.

Request pacing depends on the checking workflow and deployment configuration. We do not promise a single fixed requests-per-second rate for every RedirX check.

The redirect checker does not consult robots.txt before each check. Use your server or firewall access controls if you need to restrict requests, and contact us if you want help investigating traffic. Blocking checks can leave a migration’s redirects unverified.

Ask about requests to your site

Email Dylon@RedirX.dev with your domain, timestamps and time zone, request paths, observed source IPs, and the User-Agent from your logs. These details help us investigate; the User-Agent alone cannot confirm the source.

Remove passwords, cookies, authorization headers and sensitive query values before sharing logs. No need to send full page content.