v152 · suspicious site warnings
Audit your own markup
Nobody outside Google knows what the signals are. What is public is the shape of the thing being described — patterns that deceptive pages use and honest pages usually do not — and those are checkable. Paste your markup, or audit this page, and see which of them you are emitting.
What to check
Findings
| check | hits | example | why it looks deceptive |
|---|---|---|---|
| Nothing audited yet. | |||
This is not a Safe Browsing simulator and cannot predict a verdict — a clean result here is not a promise and a dirty one is not an accusation. It is a list of patterns that are worth not having, most of which are also bugs.
The insecure-subresource check looks only for URLs written as absolute http://. An earlier version resolved every URL against the page and flagged three findings on this page itself, because a development server on plain http makes every relative path resolve to http — a false positive that would have taught the wrong lesson to anyone auditing locally.
What this can and cannot tell you
| question | answerable here? | why |
|---|