How we build a trust score
We combine technical, reputation, and community signals to produce a coherent indicator. The goal: useful and responsible estimation, not an arbitrary verdict.
Outline
Technical signals
Valid HTTPS, domain age, consistency of public records. These signals do not prove trust alone, but reduce uncertainty.
We favor objective, verifiable signals over superficial criteria.
For example, valid HTTPS is a baseline. Missing HTTPS often indicates weak hygiene.
Reputation signals
Safe Browsing and VirusTotal detect security reports. We consider presence, frequency, and severity without overweighting a single provider.
If sources disagree, we favor caution and historical consistency.
A single alert is not a verdict. Repeated alerts raise risk.
Community signals
User reviews and reports capture issues automation misses. We moderate reviews to limit fraud and bias.
Very low review volume is flagged as weak social proof.
Reports are cross checked with technical checks before impacting the score.
Known limits
A site can be legitimate but too new for a strong history. Conversely, an older site can become fraudulent. The score should be combined with your own verification.
We update weights as threats evolve.