See how HIP checks and scores a website.

HIP resolves the domain, follows redirects, negotiates TLS, reads DNS records and fetches the page as an ordinary visitor would. It records what it observed and when. It does not record who asked. Provider lookups run in parallel and are attributed individually.

Each detection rule looks at the collected evidence and either fires or does not. A rule that fires produces a finding with an id, a severity, a plain-language reason and, where one exists, a suggested fix.

Findings carry weights. The score starts from a configurable baseline and moves as findings apply. HIP does not treat 50 as automatically neutral, and the published rule set includes the baseline. The breakdown appears alongside the score.

Automated checks get things wrong. Any finding marked appealable can be contested with context; a reviewer looks at the evidence and either upholds it, adjusts it, or fixes the rule for everyone. Feedback and outcomes are logged.

Results surface in the web portal, through the browser extension and, for verified domains, as a domain verification record and an earned trust badge. A HIP-aware DNS service is planned so results can travel with a lookup rather than a page load.