Encryption is not identity
HTTPS protects a connection. It does not prove that the operator is honest, that the page is harmless, or that the domain is the one a visitor intended.
Human Interactive Protocol
HIP is an open trust protocol and trust layer for evaluating websites with technical, reputation, identity and behavioural evidence. A scanner is one way to use HIP, but the protocol is the larger system that defines evidence, scores, confidence, verification and review.
Why HIP exists
HTTPS protects a connection. It does not prove that the operator is honest, that the page is harmless, or that the domain is the one a visitor intended.
HIP separates observations, rule versions, score components, confidence and limitations so clients can present the same result without hiding how it was reached.
A public result can include domain trust, page trust, content risk, evidence coverage, confidence, reasons and a final HIP score. Limited Data is a valid result, not a guess.
Website owners can prove control, inspect public-safe findings and use the documented appeal path when evidence is wrong or incomplete.
Four distinct concepts
A 0 to 100 result tied to the evidence, scan time and active rule or policy version. A high score is not a safety guarantee.
A DNS or supported website challenge can prove control of a domain. Control alone does not establish trustworthiness.
An issued certificate binds a domain, verification level, evidence and validity period to a signed HIP record that can be checked independently.
The badge is the public presentation of a current eligible HIP state. It links back to verifiable information and can stop representing an active state when its certificate or evidence is no longer current.