Tiếng ViệtOpen the app

Methodology & data sources

Last updated:

This page explains where Raccoon gets its data, how it combines it, and what the tool cannot do — so you know how much weight each result deserves.

Data sources

SourceUsed for
WHOIS / RDAP, DNSRegistration date, registrar, name servers, IP address and hosting provider — to find where a report should go.
VirusTotalVerdicts from many security scanners on a domain or URL.
Google Safe BrowsingWhether Google flags the page as phishing or malware.
URLhaus (abuse.ch)Known malware distribution URLs reported by the community.
SpamhausWhether a domain or IP is on a blocklist.
urlscan.ioOpening the page in an isolated sandbox to record redirects, credential forms and downloads.
Search resultsWatching page 1 of search results for brand keywords to spot unknown domains.
Cloudflare APIReading and creating redirects and canonicals on the Cloudflare account the user connects.

Some sources only work when the server has the matching API key. When a key is missing, the interface says “not configured” instead of showing an assumed result.

How risk is assessed

  1. Collect information from the sources above for each domain or URL.
  2. Compare signals: newly registered domain, name close to the brand, login form, unusual redirects, already flagged elsewhere…
  3. Score how suspicious it is and show each signal alongside, so you can see why a page scores high or low.
  4. The user reviews before any report is sent. Raccoon never accuses or reports on its own without confirmation.

Limits to keep in mind

Changes to this methodology

When we add or remove a data source or change how results are assessed, this page is updated and the date at the top changes. Feedback on accuracy: [email protected].