How the score worksEvery number, and where it comes from.
The score runs from 0 to 100; higher means fewer risk signals. It is a weighted average of the factors we could measure for that domain at that moment, and nothing else.
The factors and their weights
| Factor | Source | Weight |
|---|---|---|
Domain age Registration date from the registry's RDAP record. | rdap.org → the registry | 45% |
HTTPS certificate A TLS handshake on port 443; the certificate must chain to a trusted authority and match the name. | Direct connection | 30% |
Email authentication SPF record on the domain and DMARC record at _dmarc. | DNS TXT records | 25% |
Domain age
Age is counted in days from the registration date to the moment of the check.
- Under 1 month
- 5/100
- 1 to 3 months
- 15/100
- 3 to 6 months
- 35/100
- 6 to 12 months
- 55/100
- 1 to 2 years
- 70/100
- 2 to 5 years
- 85/100
- 5 years or more
- 100/100
HTTPS certificate
- Valid for the name
- 100/100
- Offered but invalid
- 10/100
- Connection refused
- 0/100
- Timed out or unreachable
- not checked
Email authentication
- SPF and DMARC
- 100/100
- One of the two
- 60/100
- Neither
- 20/100
- DNS did not answer
- not checked
When a factor cannot be checked
A lookup can fail: the registry does not answer, the server times out, DNS returns an error. That factor is then shown as not checked and is removed from the average; the remaining weights are scaled up. It never counts as a fixed or guessed value. With fewer than 2 measured factors there is no score at all, only the findings.
The result page always says how many factors were checked, so a score built on two factors is never mistaken for one built on three.
Bands
- 80 to 100
- Few risk signals
- 60 to 79
- Some risk signals
- 40 to 59
- Several risk signals
- 0 to 39
- Many risk signals
The bands describe signals, not intent. We never label a site a scam or safe.
Deliberately not scored
- Blocklists. The reliable phishing and malware lists need an API key or forbid this use, so we link to Google Safe Browsing and VirusTotal instead of pretending to check.
- Traffic rank. No free source is wired in, and a guessed rank would be an invented figure.
- Registrar and owner privacy. Shown for context. Hiding owner details is normal and required by law in many countries, so it is not a risk signal.
- Reviews and content. We do not read the site's pages or collect opinions.
Freshness and limits
A result is kept for 24 hours and then checked again on the next visit. Checks are rate-limited per connection. We only connect to public addresses on port 443 and send no HTTP request to the site, so a check never logs in, submits a form or follows a redirect.