Detect Heroku

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

• Response headers
• URL patterns
• DNS records

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

• via: vegur
• .herokuapp.com
• TXT: heroku-domain-verification

Establishes

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

Does not establish

A sitewide install of Heroku, an active vendor contract, exclusive use, or that Heroku 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 Heroku signals.
2. 2. PluginView reads only public responses (response headers, url patterns, dns records) and scores them against the Heroku signature set (3 rules).
3. 3. Review the confidence score and text explanation for Heroku on the results page.

Can PluginView detect Heroku without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Heroku — typically response headers, url patterns, dns records. It does not bypass authentication or paywalls.

What category is Heroku?

Heroku is classified under PaaS in the PluginView directory.

How many fingerprint rules cover Heroku?

This reference currently tracks 3 fingerprint rules across response headers, url patterns, dns records. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Heroku?

Illustrative public indicators for Heroku include via: vegur; .herokuapp.com; TXT: heroku-domain-verification. A live scan may match additional proprietary rules beyond these examples.