How Do You Report a Phishing Site to Google Safe Browsing?
Published 2026-11-14 · Reviewed 2026-11-14 · 6 min read · By the Ingenious AI team
Is someone impersonating your domain right now?
Run the free DomainGuard scan: lookalike registrations, MX-armed variants, certificate-transparency and CAA checks for your domain, in one report.
Run my free DomainGuard scanThe short answer
You report a phishing site to Google Safe Browsing through Google's Report Phishing Page form at safebrowsing.google.com/safebrowsing/report_phish, giving the full URL, and ideally filing in the same hour as your registrar, hosting, and Microsoft SmartScreen reports. A successful listing puts a full-page red warning in front of Chrome users — and, through Safe Browsing's data sharing, users of several other browsers — usually within hours. It does not remove the site from the internet. It neutralises most of the traffic while the slower takedown channels finish the job.
What a Safe Browsing report actually does
Safe Browsing is a warning system, not a removal system, and planning around that distinction saves frustration. When a URL is confirmed and listed, Chrome displays an unmissable interstitial — a red screen telling the visitor the site ahead is deceptive — and most visitors turn back. Search results from the flagged domain can also carry warnings. The server, however, keeps running, the domain keeps resolving, and a determined visitor can click through. Your registrar and host reports are what actually end the site.
Used correctly, the warning is the fastest harm reduction available to you. Registrar timelines are measured in days; hosting abuse desks in hours to days; Safe Browsing verdicts on clear credential-phishing pages often land within the first hours. In incident terms, you file Safe Browsing to protect people tonight and the registrar to end the problem this week. File both, in parallel, from the same evidence pack.
Building the report Google can act on
The form asks for the URL and details of the threat. Precision wins speed. Submit the exact phishing URL, including path and any subdomain, not just the homepage — listings attach to what you report and what Google's crawlers can verify. In the details field, say plainly what the page does: which brand it imitates, what it asks for (credentials, card numbers, one-time codes), and how victims are being sent there, if you know — a phishing email, a text, an ad.
Assemble the underlying evidence before you open the form: timestamped screenshots showing the address bar and the credential form, the page's certificate details, the domain's registration date, and any phishing message that delivered the link, with headers if it was email. Google does not require attachments on the basic form, but the same pack goes to the registrar and host, and having it ready means all your filings go out in one sitting instead of dribbling across a day.
The filing sequence that protects users fastest
If you are triaging a live incident with limited hands, order matters. First, Safe Browsing and Microsoft SmartScreen, because warnings protect the most users per minute of effort. Second, the hosting provider, because hosts suspending content is usually the fastest true removal. Third, the registrar, whose suspension ends the domain across every host it might move to. Fourth, community feeds such as PhishTank and Netcraft, which propagate your report into gateways and security products you will never file with individually.
File law-enforcement reports for financially significant cases alongside, not instead of, the fast channels. And re-check the URL after submission: load it in Chrome and confirm the warning appears. If hours pass with no warning and the page is unambiguous phishing, you may submit again with sharper details — but do not spam the form; one clear report with strong detail outperforms five vague ones, and Google re-crawls and re-evaluates listed and unlisted URLs continuously.
Common reasons reports stall
The most common failure is reporting the wrong granularity: the bare domain when the phishing kit lives on a specific path or subdomain that crawlers must be pointed at. The second is a page that behaves differently for Google's crawlers than for victims — some kits serve benign content to datacenter IP ranges or non-target geographies. Noting that behaviour in your report details ('the page cloaks: serves a blank page outside residential IPs in our country') genuinely helps reviewers reproduce what victims see.
The third is timing: a page reported in its first minutes may not be crawled until it has changed or moved. Treat a stalled verdict as a monitoring task, not a concluded one. Keep the URL in your incident notes, check it on a schedule, and push the hosting and registrar channels harder meanwhile — those desks act on your evidence directly and do not depend on a crawler seeing the same thing you saw.
After the warning: finish the job
A red warning tempts teams to declare victory early. Resist it. Click-throughs happen, some browsers and in-app webviews warn less strongly, and the attacker can move the kit to a fresh URL on the same domain faster than new warnings attach. The warning buys time; the registrar and host filings spend it well. Keep all channels moving until the domain is suspended or the content is gone, and verify by resolving and loading the address yourself.
Close the loop internally as well. Tell your support team the URL is listed, so customer reports get a confident answer. Save the timeline — first seen, filed, warned, removed — because those numbers are next quarter's argument for monitoring budget, and because a written timeline is what insurers and law enforcement will ask for if money moved. Then register the lesson: incidents found by your monitoring, like the CT alert in our worked example, get filed while the site is still being built, which is the cheapest version of this whole process.
Five actions to take today
- Capture the evidence pack first: full URL, timestamped screenshots with the address bar, certificate details, and the delivering message if you have it.
- File at safebrowsing.google.com/safebrowsing/report_phish with the exact phishing URL and a plain description of what it harvests.
- File Microsoft SmartScreen, the hosting provider, and the registrar in the same hour — warnings protect, hosts and registrars remove.
- Verify the result by loading the URL in Chrome and confirming the red warning appears.
- Keep registrar and host pressure on until the site is actually gone, and log the full timeline for your records.
Worked example: Mesa Verde Rentals stops a clone in one evening
Mesa Verde Rentals, a fictional property company monitoring 4 domains, found a lookalike booking page through a DomainGuard lookalike alert at 16:20, showing 23 registered lookalikes across its estate and 1 live clone. Staff captured screenshots and filed Safe Browsing and SmartScreen reports by 17:05; the Chrome warning was live by 19:40. The host suspended the content the next morning, and the registrar suspended the domain on day 3. Booking-system logs showed 41 visits reached the clone before the warning appeared — and zero credential submissions after it did.
FAQ
How long does a Safe Browsing listing take?
For clear credential-phishing pages, often within hours of a good report, though timing varies. It is the fastest user-protection channel, which is why it is filed first, in parallel with removal channels.
Does a Safe Browsing warning remove the site?
No. It warns visitors away but the site stays online until the host or registrar acts. Treat the warning as harm reduction while your removal filings proceed.
What URL should I report — the domain or the full path?
The full phishing URL, including subdomain and path. Listings and crawling attach to what you report, and kits often live on specific paths rather than the homepage.
Can I report a site that is impersonating someone else?
Yes. Anyone can report phishing. Reports from the impersonated brand carry useful context, but a clear third-party report with good details is still acted on.
The warning never appeared. What now?
Check whether the page cloaks its content from crawlers and note that in a follow-up report, then push the hosting and registrar channels harder — they act on your evidence directly rather than on crawler observations.