Chrome’s New Scam Warnings: 6 Checks for Site Owners

On this page
Chrome suspicious site warnings are a new, softer warning level Google added on October 20, 2026. They appear for Enhanced Protection users when a page looks like a scam but Google isn’t sure.[1] Chrome also now asks every user before opening a plain HTTP site.[2]
Most legitimate sites won’t notice either change. But Google hasn’t said how a site owner can see or dispute the new suspicious label, so a few checks now are worth the time.[1][4]
What happened
Google announced four Chrome changes in two days. Three apply to Enhanced Protection, the stricter Safe Browsing mode that more than 1 billion Chrome users had turned on as of 2025, per Google.[1] The fourth applies to everyone.[2]
1. Two levels of site warning
Until now, a flagged site got the full-page red “Dangerous site” screen. That stays for high-confidence verdicts. Below it, Chrome now shows a “suspicious site” warning with a different look, icon and wording.[1][8] Google describes the new level this way:
“lower confidence verdict, possible risk of user harm”
Google, Chrome team [1]
It appears when a page shows deceptive patterns common on known malicious sites.[1] Google says the separate look lets it “safely expand” coverage and show more warnings.[1]
2. Gemini now judges pages on Google’s servers
Last year Chrome used a small on-device Gemini model to spot tech support scams on supported devices. It has now moved to a larger model on Google’s servers, for all Enhanced Protection users.[1] The model looks at which brand a page claims to be, what the page wants the visitor to do, and how scam-like it is. Safe Browsing combines that with the domain’s reputation to reach a verdict.[1] It now also covers fake antivirus and fake browser update pages.[1]
On privacy, Google says Chrome sends page text only when a site shows high-confidence scam signs, and that the text is never logged, kept or used for training.[1]
3. Warnings when someone copies a ClickFix command
ClickFix pages trick people into copying a command and running it themselves to “fix” a fake problem, often behind a fake CAPTCHA. When an Enhanced Protection user copies a suspicious command, Chrome strips personal data from it, checks it with Safe Browsing and warns if it’s dangerous.[1] We covered how these pages get planted on WordPress sites in our fake Cloudflare CAPTCHA guide.[9]
4. Chrome asks before opening HTTP sites, for everyone
Chrome now asks for permission before it connects to a site over unencrypted HTTP. Enhanced Protection users got this earlier in 2026, and on October 21 it became the default for all users.[2][3] Visitors see the prompt on their first visit. After they approve, Chrome won’t ask again unless they stay away for at least two weeks.[2] Intranet names and local IP addresses are exempt.[2] In early data, nearly 95% of desktop users saw no HTTP warning in a given week.[2]
Why it matters for your site
For most site owners, these changes are good news. Scam pages that copy your brand, and ClickFix pages planted on hacked sites, now get caught more often. Three things still deserve attention.
- More warnings, by design. A lower-confidence tier means more pages get flagged. Google hasn’t published thresholds or a false-positive rate.[1][4]
- Your page is judged on brand and intent. PPC Land notes that resellers, comparison sites and affiliate pages use brand names they don’t own, and it’s unknown whether they’re more likely to be flagged.[4]
- No public appeal for the new level. Google’s post doesn’t say whether site owners are notified of a suspicious verdict, or how to contest one.[1][4] The existing review process covers Safe Browsing flags in general.[5]
The HTTP change is simpler. Any page you still serve over plain HTTP now shows a prompt to first-time visitors, not just a “Not secure” label.[2] That includes old campaign landing pages and forgotten subdomains.
Chrome suspicious site warnings and the others, at a glance
| Warning | Who sees it | What it means |
|---|---|---|
| Dangerous site (full-page red) | All Safe Browsing users | High-confidence phishing, malware, unwanted software or social engineering.[1][8] |
| Suspicious site (new) | Enhanced Protection only | Lower-confidence verdict: the page looks like known scams.[1] |
| Copied-command warning (new) | Enhanced Protection only | A copied command looks like a ClickFix attack.[1] |
| HTTP connection prompt | All users, by default | The site isn’t using HTTPS.[2] |
6 checks for site owners
- Check your Safe Browsing status. Enter your domain in Google’s Safe Browsing site status tool. A clean result reads “No unsafe content found.”[7] Google hasn’t said whether the new suspicious level shows up there, so treat it as a check for the red warnings.
- Verify your site in Search Console. The Security Issues report is where Google lists problems it finds and where you request a review.[5] If you haven’t verified ownership, you can’t use it.
- Hunt down HTTP leftovers. List every subdomain, old landing page and tracking link you use in emails or ads. Each should send visitors to HTTPS. Chrome now prompts first-time visitors on anything that doesn’t.[2] A quick test from a terminal is below.
- Don’t look like a scam. Gemini is looking for brand claims, intent and scam-like patterns such as fake security alerts and fake browser updates.[1] Our advice: drop fake countdowns, pop-ups styled like system warnings and “your device is at risk” copy, even in ads.
- Say who you are if you use other brands’ names. If you resell, compare or review other companies’ products, make it obvious on the page that you are a separate business. This is our advice, since Google hasn’t said how it treats these pages.[4]
- Know the fix-and-review path. If a real problem caused the flag, clean it first. Then request a review in Search Console. For a phishing flag you think is wrong, you can also use Google’s report_error form.[5][6]
Here is the HTTP check. Run it for each hostname you use. A good result shows a 301 or 308 redirect with a Location header that starts with https.
curl -sI http://www.example.com/ | grep -iE '^HTTP|^location'How long reviews take
Google’s review guide says a phishing review takes about a day and a malware review a few days. Hacked-spam reviews can take several weeks. Once a site is found clean, warnings are removed within 72 hours.[5] Requesting a review before the problem is fully fixed keeps the flag in place longer.[5]
If a customer tells you Chrome warned them, ask for a screenshot. The new suspicious warning looks different from the red one, and knowing which they saw tells you which path to take.[1]
What we don’t know yet
Google’s announcement leaves gaps that matter to site owners. It gives no rollout dates by platform, no minimum Chrome version, and no list of patterns that trigger the suspicious level.[1][3][4] It also offers no guidance for website owners.[1] We’ll update this guide if Google publishes guidance for site owners.
One more angle: the same checks that catch scams also catch clones of real businesses. If fake copies of your store are a worry, our guide to finding and reporting brand clones covers the reporting side.
Where Zero Spam fits
Zero Spam doesn’t control Chrome’s warnings and can’t clear a Safe Browsing flag. What it does is block spam bots and known bad IPs on your forms and comments, so scam links don’t end up published on your pages. The free Zero Spam WordPress plugin is an easy start, and you can start on the free Explorer plan.
FAQ
Frequently Asked Questions
It’s a new, lower-level Chrome warning for pages that look like known scams when Google’s verdict is less certain. It looks different from the full-page red “Dangerous site” warning.[1]
Only people who use Chrome’s Enhanced Protection mode. The red dangerous-site warning still applies to all Safe Browsing users.[1]
Check your domain in Google’s Safe Browsing site status tool and watch the Security Issues report in Search Console.[5][7] Google hasn’t said whether the new suspicious level appears in either.
Yes. Since October 21, 2026, Chrome asks all users for permission before opening a site over plain HTTP. Move every page to HTTPS.[2]
Sources & References
- Google: Our latest defenses against evolving web scams, suspicious site warnings, Gemini checks and ClickFix detection (Oct 20, 2026)
- Google: Chrome now warns before insecure HTTP connections, on by default for all users (Oct 21, 2026)
- SecurityWeek: Google hardens Chrome against ClickFix attacks and insecure HTTP connections (Oct 21, 2026)
- PPC Land: Chrome adds suspicious-site warnings for Enhanced Protection users, open questions for site owners (Oct 24, 2026)
- Google web.dev: Request a review of a security warning in Search Console, review times by issue type (accessed Oct 25, 2026)
- Google Safe Browsing: Reporting incorrect data, report_error form for wrongly listed phishing URLs (accessed Oct 25, 2026)
- Google Transparency Report: Safe Browsing site status checker (accessed Oct 25, 2026)
- Chrome Help: Manage warnings about unsafe sites, dangerous and lookalike warnings (accessed Oct 25, 2026)
- Zero Spam: Fake Cloudflare CAPTCHA on WordPress (ClickFix), how to spot and remove it (accessed Oct 25, 2026)
