RendexWatch

RendexWatch is the automated fetcher behind Rendex Watch, our website change-monitoring service. This page exists so that site owners can recognize, verify, contact, or block it. If you arrived here from a User-Agent string in your server logs, you’re in the right place.

What RendexWatch does

Rendex Watch lets a Rendex user monitor a single web page for visual or text changes. When a user creates a watch, RendexWatch captures (renders) that page on a schedule the userchooses — as infrequently as once a day on the free plan, down to every few minutes on paid plans — and compares each capture against the previous one to detect changes for the user who set it up.

It only fetches pages a Rendex customer has explicitly asked to monitor. RendexWatch does not crawl links, follow pages, discover new URLs, or build a search index. Every fetch corresponds to one specific page a specific user is watching.

User-Agent

By default, every RendexWatch request identifies itself with this exact User-Agent string:

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36 RendexWatch/1.0 (+https://rendex.dev/bot)

The +https://rendex.dev/bot token points back to this page, so anyone inspecting their logs can find out who we are.

One exception.If a watch uses device emulation (for example, capturing a page as an iPhone), the request instead presents that device’s own User-Agent, so the page renders exactly as it would for that device. Those requests do not carry the RendexWatch token, so a User-Agent match alone will not identify them.

How we keep it polite

• Minimum check interval per plan.RendexWatch respects a minimum interval between checks based on the watching user’s plan. There is no sub-minute hammering — even the fastest schedules leave minutes between requests, and most watches run hourly or daily.
• Per-host caps. We cap how many watches a single account can point at one host, so no one account can concentrate load on your site.
• Runs from Cloudflare’s network.Requests originate from Cloudflare’s global edge infrastructure.
• User-directed only. RendexWatch only fetches pages a Rendex user has explicitly added as a watch. It never discovers or visits pages on its own.

How to identify or block it

The simplest way to recognize default RendexWatch traffic is to match the RendexWatch token in the User-Agent. To ask it not to fetch your site, add a matching rule to your robots.txt:

User-agent: RendexWatch
Disallow: /

An honest note on robots.txt. For user-directed monitoring of public pages, Rendex treats robots.txtas advisory rather than a hard boundary. A watch is a fetch the user could perform themselves in their own browser — the Rendex user is the actor directing it — so we do not treat a public page as off-limits solely because of robots.txt.

If you want a hard guarantee, block the RendexWatch User-Agent (or the originating requests) at your CDN or web server. A User-Agent–level deny will stop default RendexWatch traffic. Because device-emulation watches present a device User-Agent instead (see above), a content- or IP-level rule is needed to stop those.

Contact us

If you’d rather we stop monitoring a specific page, believe a watch is misconfigured, or just have questions, email us at support@rendex.devand we’ll help. You can also learn more about the product itself at Rendex Watch.