Every signal we use, the weight we give it, and the source it comes from. We publish this so you can judge our scores critically.
Every domain starts at 100 / 100. We then subtract weighted penalties for each risk signal we detect. The final score maps to one of three risk bands:
We also publish a confidence score with every TrustScore. It reflects how many of our signals returned real data versus "unknown" for the domain. Low confidence means we couldn't gather much — treat the result as preliminary.
We don't penalize signals we couldn't measure — "unknown" is never treated as bad.
Newly registered domains (under 1 year, especially under 30 days) are statistically more likely to host short-lived scams. Brand-new domains lose the most points.
Many legitimate sites also hide WHOIS for privacy, so this is a small penalty — only meaningful in combination with other signals.
A site that does not use HTTPS cannot encrypt anything you submit. This is a structural problem regardless of intent.
The domain has been independently flagged by Google Safe Browsing for malware, phishing, or unwanted software at the time of the scan.
An LLM detected strong scam patterns in the page text — typically high-pressure urgency, fake giveaways, gift-card payment requests, or impersonation language.
Some suspicious patterns were detected, but not enough to be confident. Treated as a caution signal, not a strong indicator.
The domain name closely resembles a well-known brand (e.g. paypa1.com, amaz0n-support.net). False positives are possible for legitimate resellers — disputes are reviewed.
Brand-new sites with no traffic at all is one weak indicator. We never penalize a site simply for being unknown to us.
Signed-in users can report a site (with reason). Reports are weighted but capped — the score cannot collapse from reports alone.
It means our automated checks didn't surface obvious risk signals at the time of the scan. Sophisticated scams, breached accounts, and fresh phishing pages can still pass automated checks. Always use your own judgment.
It is an automated risk opinion based on weighted public signals. Legitimate businesses can score low for benign reasons — new launch, hidden WHOIS, low traffic, or a redesigned policy that triggers our content checks. If you believe a score is wrong, file a dispute and we will review it.
We do not vet ownership, investigate fraud, or verify business registration. Treat TrustScores as one input among many — alongside your own due diligence, established review platforms, and qualified professional advice for any decision with legal or financial consequences.
Domains change owners. Sites get redesigned. Policies are rewritten. A score from last week may not match today's site. The Methodology, our scanner, and the dispute process are designed around this — but you should still treat scores as fresh signals, not permanent labels.
Anyone can submit a dispute on a domain's score or policy analysis. Verified disputes are reviewed by our team, the score is hidden from public share pages while the review is in progress, and every decision is logged in our public corrections feed.
The Article Fact Checker takes the text you paste and asks an AI model to assess its credibility against publicly available sources. Every assessment is a hedged, opinion-based signal — never a declarative verdict.
Fact-check verdicts use four hedged labels — Likely Credible, Mixed Signals, Likely Misleading, and Unverifiable. We never use absolutes like "False" or "Fake News". If you believe a fact-check assessment is wrong, file a dispute from the report and we will review it.
Last updated for the deterministic TrustScore engine in production. Material changes to weights or signals are versioned in our changelog.