Detect Hostinger

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

• Response headers
• DNS records

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

• platform: hostinger
• SOA: .dns-parkinghostinger.com

Establishes

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

Does not establish

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

Can PluginView detect Hostinger without logging in?

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

What category is Hostinger?

Hostinger is classified under Hosting in the PluginView directory.

How many fingerprint rules cover Hostinger?

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

What public signals suggest a site uses Hostinger?

Illustrative public indicators for Hostinger include platform: hostinger; SOA: .dns-parkinghostinger.com. A live scan may match additional proprietary rules beyond these examples.