Google released v4 of its safe browsing API, a tool for software developers that helps client applications check URLs against Google's list of suspected malicious pages.
“With protocol version 4, we've optimized for this new environment with a clear focus on maximizing protection per bit, which benefits all Safe Browsing users, mobile and desktop alike. Version 4 clients can now define constraints such as geographic location, platform type, and data caps to use bandwidth and device resources as efficiently as possible,” wrote Chrome Security Product Manager Emily Schechter and Safe Browsing Software Engineer Alex Wozniak, in a Google security blog post. “This allows us to function well within the much stricter mobile constraints without sacrificing protection.”
Google launched the first version of its Safe Browsing API in 2007, when mobile web browsing was used minimally. Browsers now face increasingly complex challenges mobile, especially as free certificates are used to conceal malicious campaigns.
Earlier this month, in response to search ads increasingly being used for tech support scams, Microsoft updated its user policies for Bing Ads, banning third-party tech support services.