# safe browsing Published articles for safe browsing. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Chrome puts insecure sites behind a permission prompt DevFeed: [Chrome puts insecure sites behind a permission prompt]() Original publisher: [Read original article]() Author: Anamarija Pogorelec Published: 2026-10-21T22:30:30Z Content type: news Language: en Sources: [Help Net Security]() Topics: [Google Chrome]() Tags: [browser](), [browsers](), [certificate](), [chrome](), [content](), [cybersecurity](), [data](), [google](), [http](), [https](), [malware](), [news](), [permission](), [phishing](), [prompt](), [protection](), [safe-browsing](), [security](), [sites](), [threats](), [traffic](), [traffic-monitoring](), [users]() ### AI overview Chrome now asks users to approve an HTTP connection before it occurs, giving them a chance to block exposure before data is sent. The prompt appears on a site's first visit and is suppressed for two weeks after approval. Chrome already labels insecure pages "Not Secure," but Google says that warning can be overlooked, misses short-lived HTTP traffic such as redirects, and appears only after a connection has exposed data. Prompts are disabled by default for local addresses and single-label hostnames such as `intranet/`, which generally require an attacker to be on the local network to tamper with traffic. Google reports that nearly 95% of desktop users see no HTTP warnings in a given week and fewer than 1% see three or more; mobile warning rates are lower. The supplied excerpt says the protection is enabled by default for all users and identifies Chrome as the first browser to do so. ### Source excerpt Google has rolled out a change to Chrome that asks users for permission before making an insecure HTTP connection. The protection is now enabled by default for all users, following its introduction earlier this year for users of Safe Browsing's Enhanced Protection mode. The vast majority of connections made by Chrome use HTTPS, according to Google. However, unprotected HTTP traffic can expose users to malware, phishing, eavesdropping and other threats. Any HTTP request gives attackers ... More -> The post Chrome puts insecure sites behind a permission prompt appeared first on Help Net Security. ## Optimizing Safe Browsing checks in Chrome DevFeed: [Optimizing Safe Browsing checks in Chrome]() Original publisher: [Read original article]() Author: Chromium Blog (noreply@blogger.com) Published: 2024-02-13T17:00:00Z Content type: news Language: en Sources: [Chromium Blog]() Topics: [Google Chrome](), [Page Speed Optimization](), [performance-engineering](), [performance-optimization](), [Artificial Intelligence](), [Machine learning](), [Business, Industry, Usability, User Experience, User Research, Web Strategy]() Tags: [ai](), [ai-and-ml](), [asynchronous](), [chrome](), [none](), [performance](), [phishing](), [safe-browsing](), [security]() ### AI overview Chrome is changing Safe Browsing checks to reduce browsing delays and unnecessary network requests while maintaining protection through other measures. Starting in Chrome 122, real-time server checks will run asynchronously, so pages can load before the check finishes; Chrome will still warn if a site is later found dangerous. The excerpt says local checks for sites known to deliver browser exploits remain synchronous. Chrome will stop checking sub-resource URLs, citing declining large-scale attacks through them and other detection methods, including a client-side visual ML model; this reduces network use and simplifies Safe Browsing detection and APIs. It will also contact Safe Browsing much less often for PDF downloads, citing hardened viewers such as Chrome's sandboxed viewer and a lack of widespread PDF exploitation. Google says these changes should improve responsiveness without degrading security, while noting that dangerous pages may briefly load before a warning appears. ### Source excerpt Balancing security and usability is always top of mind for us as we strive to stay on top of the constantly evolving threat landscape while building products that are delightful to use. To that end, we'd like to announce a few recent changes to how Chrome works with Google Safe Browsing to keep you safe online while optimizing for smooth and uninterrupted web browsing. Asynchronous checks Today, Safe Browsing checks are on the blocking path of page loads in Chrome, meaning that users cannot see pages until checks are completed. While this works fine for local-first checks such as those made using Safe Browsing API v4, it can add latency for checks made directly with the Safe Browsing server. Starting in Chrome 122, we will begin to introduce an asynchronous mechanism which will allow sites to load even while real-time checks with Safe Browsing servers are in progress. We expect this to reduce page load time and improve user experience as real-time server-side checks will no longer block page load, although if a site is found to be dangerous after the page loads then a warning will still be shown. In addition to the performance boost, this change will let us improve the quality of protection over time. By taking the remote lookup outside of the blocking path of the page load, we're now able to experiment with and deploy novel AI and ML based algorithms to detect and block more phishing and social engineering attacks. It was previously challenging to perform such experimentation because of the potential to delay page loads. In terms of potential risks, we evaluated the following and concluded that sufficient mitigations are in place: Phishing and social engineering attacks: With the move to asynchronous checks, such sites may start to load while server-side Safe Browsing checks are in progress. We have studied the timing data and concluded that it is extremely unlikely a user would have significantly interacted with (e.g. typed in a password) such a site by the time a