Threat list updates checked against url safeties, in one pass

What does it already know about your url safeties?

All 2 operations read.

Your account, not a guess at it: a companion can get threat list updates and check an URL safety, and the full list below is the whole list, with nothing inferred from Google Safe Browsing's documentation.

The threat list updates are what most of this inventory is about, alongside the url safeties. A companion can hold all 2 of these operations and forty open tabs in the same pass, which is how an afternoon of Google Safe Browsing admin becomes a queue you review.

• Get Threat List Updates
• Check URL Safety

It can get threat list updates. Can it act on what it finds?

Through the screens you already use.

Google Safe Browsing exposes no write operation to a connected account, so a companion drives Google Safe Browsing in the session you are already signed into instead, filling the same forms you would to move a threat list update, and anything consequential stops for an approval card before it happens.

That is the ordinary case rather than the exception. Most of what a threat list update in Google Safe Browsing touches has no API pointed at it, and a companion is useful precisely because it does not need one.

Can the threat list updates pass run every Monday?

Yes.

Saved as a routine, the Google Safe Browsing threat list updates pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.

The product and engineering playbook catalogues the other recurring shapes of the infrastructure checks, the Google Safe Browsing threat list updates sweep among them, and finished runs are published at real runs.

Frequently asked questions