From report to takedown

    What actually happens after you hit submit: how Fraudpol screens, verifies, escalates and monitors a malicious website until it's gone.

    The Fraudpol pipeline

    Six stages, each with a clear owner. Every report follows the same path: the speed and depth depend on your plan.

    1. You submit a report

    A guided form collects the domain, the exact URLs, what you observed and your evidence. You can report a website with or without an account. Reports about an individual or group need a sign-in. You decide whether a website report is shared with the community.

    2. Automated screening

    Website reports on the free tier are screened automatically for description quality, evidence and plausibility. Clearly empty or invalid reports are rejected with a written reason; everything else goes to a person. Company reports skip this step.

    3. A team member confirms

    A Fraudpol team member checks the site. As soon as a report is accepted, the reported page is saved automatically together with a SHA-256 fingerprint, so the evidence survives even if the site disappears. Nothing is sent to anyone before a team member has confirmed the abuse.

    4. Notices to the responsible providers

    After confirmation, notices go to the providers that can act: the hosting provider, the domain registrar and, where relevant, the platform or service involved. Each notice describes what the site does and carries the evidence fingerprint. Serious cases can be referred to the competent authorities.

    5. Monitored to resolution

    We keep checking the site until it is offline, suspended or no longer resolves. You receive an email on meaningful status changes only.

    6. Published once closed

    Confirmed takedowns appear on the Results page and as case pages once the case is closed. Reporter details are never published.

    What makes a report pass screening

    Free-tier website reports are screened automatically. Clearly empty or invalid reports are rejected with a written reason; everything else goes to a person.

    Do

    • • Describe the abuse in 2-3 specific sentences.
    • • Attach at least one piece of evidence: screenshot, hash, log or URL.
    • • Screenshot before the site disappears: evidence goes fast.
    • • Use WHOIS to fill in registrar and hoster when you can.
    • • Enable community sharing so others get warned.

    Don't

    • • Submit placeholder text, gibberish or test data.
    • • Upload actual malware samples: screenshots and hashes only.
    • • Report well-known legitimate domains without overwhelming proof.
    • • Spam duplicate reports for the same URL.
    • • Include PII of victims beyond what's necessary.

    How your plan changes the pipeline

    Everyone gets the same escalation channels. Paid tiers change how fast a report reaches a human and how many you can push through per hour.

    Plan
    Review path
    Provider response
    Rate limit
    Free
    AI triage
    Best effort
    10 reports/hour
    Starter
    Team review
    Provider-dependent
    50 reports/hour
    Pro
    Priority analyst
    Provider-dependent
    25 reports/hour
    Enterprise
    Dedicated analyst
    Custom
    Custom

    Starter and Pro can be purchased directly on the pricing page.

    Report status guide

    What each state means and what happens next.

    Pending

    Received and queued for automated screening. The system scores the report on description quality, evidence, domain reputation and anti-abuse signals.

    Screening typically completes within minutes: the report is either accepted for analyst review or auto-rejected.

    Accepted

    Passed screening and/or picked up by a human analyst for investigation.

    The analyst verifies whether the reported site is actually abusive.

    Invalid

    The report could not be processed: insufficient information, wrong format, or out of scope.

    Terminal state. You can submit a new report with corrected information.

    Abuse Confirmed

    Investigation confirmed abusive activity. Evidence has been captured into the vault.

    Notices are prepared and sent to the responsible providers.

    Abuse Not Found

    No evidence of abuse at the time of analysis. The site may have been cleaned or the threat was not confirmed.

    You can add fresh evidence to reopen the case.

    Forwarded

    The report has been sent to one or more external parties for action.

    We keep checking the site and wait for the provider to act. How long that takes depends on the provider.

    Refused

    After investigation, the report does not meet criteria for forwarding.

    You get an explanation. You may add evidence if you believe this was in error.

    Solved

    The abusive website has been taken down or otherwise neutralized.

    Terminal state. The URL is added to the Wall of Neutralized Threats.

    Rejected

    The report was rejected: false reporting, duplicate submission or policy violation.

    Terminal state. Review our guidelines before submitting future reports.

    Where reports get sent

    Confirmed abuse is forwarded through legitimate channels: we do not run offensive operations.

    Hosting Provider

    Can suspend the hosting account behind the reported site.

    Domain Registrar

    Can suspend the domain registration.

    Platform or Service

    Can act on the abusive content or account within its service.

    CERTs / Law Enforcement

    For serious criminal activity: fraud, illegal content, coordinated campaigns: we escalate to the appropriate authority.

    Email: only when it matters

    • • Submission confirmation.
    • • Abuse confirmed or not found after investigation.
    • • Forwarded to hoster, registrar or authority.
    • • Final outcome: Solved, Refused or Rejected.

    Intermediate transitions like Accepted or Pending don't email you: track them live in your dashboard.

    In-app tracking

    • • Notification centre for live status changes.
    • • Investigation tab with enrichment output.
    • • Full timeline per report: never gets deleted.
    • • One-click GDPR data export from Settings.

    Zodiac · OSINT investigation boards

    For deeper cases, Hunter, Starter, Pro and Enterprise users get a collaborative graph workspace to map persons, domains, IPs and wallets, enrich them automatically, and submit verified indicators into a system-wide flag database.

    Graph canvas

    30+ entity types, smart paste from clipboard, floating edges with auto-avoidance, dark/light themes.

    Realtime collaboration

    Invite analysts, presence avatars, per-node comments, task assignment and read-only sharing.

    Conflict-aware editing

    Soft node locks and version checks detect conflicting saves instead of silently replacing a newer saved board.

    Automated enrichment

    IP/ASN, WHOIS and wallet lookups, plus external threat-intelligence lookups. Optional automatic enrichment caches results for inspection.

    Global flag database

    Matching verified indicators are highlighted on boards when flag data is loaded or refreshed.

    Verification

    Boards can be submitted for verification, with recorded decisions and reasoning.

    Snapshots & audit

    Restorable board snapshots and a SHA-256 hash-chained verification audit. Node edit snapshots are best-effort.

    Forensic PDF export

    Summary, node and relationship counts, flagged entities and evidence sources, with a graph screenshot when capture succeeds.

    Ready to fire a report through the pipeline?

    Free, no credit card, no follow-up spam. If you're here on behalf of a company, join the pilot for managed takedowns and brand monitoring.