Detect UptimeRobot

PluginView evaluates public page signals in these classes when identifying UptimeRobot. Individual fingerprint rule bodies are proprietary and are not published.

• Response headers
• Script sources
• DOM selectors

Illustrative indicators derived from public catalog metadata for UptimeRobot. A live scan may match additional proprietary rules beyond these examples.

• content-security-policy: .uptimerobot.com
• .uptimerobot.com/

Establishes

One or more public signals on the scanned page matched a known UptimeRobot signature (3 rules) at the time of the scan.

Does not establish

A sitewide install of UptimeRobot, an active vendor contract, exclusive use, or that UptimeRobot is still in place today.

1. 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest UptimeRobot signals.
2. 2. PluginView reads only public responses (response headers, script sources, dom selectors) and scores them against the UptimeRobot signature set (3 rules).
3. 3. Review the confidence score and text explanation for UptimeRobot on the results page.

Can PluginView detect UptimeRobot without logging in?

Yes. PluginView only reads publicly accessible responses when checking for UptimeRobot — typically response headers, script sources, dom selectors. It does not bypass authentication or paywalls.

What category is UptimeRobot?

UptimeRobot is classified under Issue trackers in the PluginView directory.

How many fingerprint rules cover UptimeRobot?

This reference currently tracks 3 fingerprint rules across response headers, script sources, dom selectors. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses UptimeRobot?

Illustrative public indicators for UptimeRobot include content-security-policy: .uptimerobot.com; .uptimerobot.com/. A live scan may match additional proprietary rules beyond these examples.