NEOANTIPHISH
Anti-phishing research & abuse reporting

We document live phishing infrastructure and report it to the parties who can act.

NEOANTIPHISH identifies active phishing campaigns, captures evidence to a standard a registrar or hosting provider can verify, and submits targeted abuse reports. We are a reporting initiative — not a trademark holder and not a takedown service.

01 — Process

How a case moves

Every reported domain goes through the same sequence. Nothing is reported before the evidence for it exists on disk and is reproducible.

01

Identification

A domain is added to the case list with the full suspected URL — not only the hostname. Phishing is frequently served from a specific path, subdomain, or query string.

02

Infrastructure resolution

Registration data is pulled via RDAP (with WHOIS as a secondary source) to establish the registrar of record and its published abuse contact. DNS, network and hosting attribution are resolved separately, and are reported separately, because registrar, DNS operator, hosting provider and CDN are usually different organisations.

03

Evidence capture

The page is captured in an isolated browser session with no personal accounts, no stored credentials, and no wallet connectivity. Screenshots, response headers, redirect chains, page source, and a timestamp in UTC are preserved and hashed.

04

Cloaking analysis

Where a target serves different content depending on the visitor, we test and record which conditions trigger the malicious response, and state the capture method for every screenshot so the claim can be reproduced by the recipient.

05

Targeted reporting

Reports are routed to the party able to act: hosting provider first where content is hosted on it, registrar for DNS-level mitigation, then registry and escalation bodies according to their own published procedures.

06

Tracking and escalation

Each case keeps its issue references, correspondence and timestamps. Escalation only happens after the first-line party has been given a reasonable opportunity to respond, and it references the original report.

02 — Methodology

What we do and how we keep it verifiable

Registrars receive a high volume of low-quality abuse complaints. The difference between a report that gets acted on and one that gets ignored is almost always the quality of the underlying evidence, so that is where we put the effort.

What we do

  • Monitor and confirm live phishing pages impersonating real brands.
  • Capture verifiable evidence with visible URL and UTC timestamps.
  • Identify the correct recipient for each report rather than guessing contacts.
  • Submit clear, structured reports in English.
  • Notify the impersonated organisation where it can be identified.
  • Track case status and escalate only with a documented history.

What we do not do

  • We do not present ourselves as a brand, its legal representative, or law enforcement.
  • We do not submit credentials, seed phrases or payment data into phishing forms.
  • We do not claim a finding we were unable to reproduce, without labelling it as such.
  • We do not send mass identical complaints to unrelated parties.
  • We do not guarantee a removal outcome — mitigation decisions rest with the recipient.
03 — Evidence standard

What accompanies a report

This is the record set we keep per case. Fields that cannot be established are marked unknown rather than estimated.

Case record — example fields
Domain
Defanged in correspondence, e.g. example[.]tld
Full URL
Exact suspected phishing endpoint, including path and query
Abuse type
Phishing
Targeted entity
Brand or organisation being impersonated, with its legitimate website
Observed at
UTC timestamp of capture
Reproduction
Conditions required to trigger the page, and the capture method used
Attachments
Screenshots with visible address bar, page source, response headers, redirect chain
Infrastructure
IP, ASN, nameservers, hosting provider where attributable
Registration
Registrar of record and domain creation date, via RDAP
Integrity
SHA-256 of each preserved artefact
Issue ID
Internal reference used in all follow-up correspondence
04 — Reporting channels

Where a case can be routed

The appropriate recipient depends on the case. For a small number of domains, the registrar is usually the first point of contact for DNS abuse; where the abuse sits in website content on a provider's infrastructure, that provider is typically better placed to act precisely.

01 — Hosting provider

Where the malicious content is served from infrastructure they control.

02 — CDN / reverse proxy

Where a proxy layer fronts the origin and operates its own abuse process.

03 — DNS provider

Where name resolution is operated independently of the registrar.

04 — Registrar of record

First-line contact for DNS abuse on an individual domain.

05 — Registry operator

Where the abuse spans many domains or the registrar is unresponsive.

06 — Browser safety services

Interstitial warnings that reduce victim exposure while a case is open.

07 — Impersonated organisation

Where the brand has standing to file its own complaint.

08 — Escalation body

Only after first-line parties have had a reasonable opportunity to respond.

05 — Contact

Reach the team

We accept inbound phishing reports. Please include the full URL, the time you observed it, and any screenshot showing the address bar.

Report a phishing site →

Phishing reports
Report a site

Fastest route: the intake form queues a case for an operator.

Phishing reports (email)
[email protected]

New cases and evidence submission.

Security & registrar liaison
[email protected]

For registrars, hosting providers and brands responding to a report.

PGP
Public key

Fingerprint published at /.well-known/security.txt.

Response time
within 72 hours

Reports are triaged in the order received.