Security
Answered with HTTP 200 and parsed as RSS 2.0 when we last looked.
https://blog.google/security/rss/Check it live- Format
- RSS 2.0
- Items in the feed
- 20
- Newest item
- 21 Oct 2026
- New items
- about every 7 days
- Language
- en-us
What was in the feed when we checked
- Chrome Now Warns Before Insecure HTTP Connections
- Protecting Chrome and Android Users from Compromised eMudhra Intermediate CA Certificates
- Our latest defenses against evolving web scams
- New Android protections to help keep you safe from mobile scams
- Android's Next-Gen Enclave for On-Device AI
- Chrome's Response to Recent ccTLD Registry Hijacks
At that moment the newest item was 27 days old, and items were appearing about every 7 days. The address above is the one to paste into a feed reader. Everything on this page comes from fetching the feed ourselves on 17 November 2026, not from a list that was typed once and never looked at again.
Other feeds on security.googleblog.com
These answered as well. It covers a narrower slice of the site, so pick the one that matches what you want to follow.
Google Online Security Blog
http://feeds.feedburner.com/GoogleOnlineSecurityBlogCheck it live- Format
- Atom
- Items in the feed
- 25
- Newest item
- 23 Apr 2026
- New items
- about once a month
What was in the feed when we checked
- AI threats in the wild: The current state of prompt injections on the web
- Bringing Rust to the Pixel Baseband
- Protecting Cookies with Device Bound Session Credentials
- Google Workspace’s continuous approach to mitigating indirect prompt injections
- VRP 2025 Year in Review
- Security for the Quantum Era: Implementing Post-Quantum Cryptography in Android
What our checker noticed
4 links such as src="/images/…" break in readers unless xml:base is set. Use full addresses.
How to subscribe
- Copy the feed address above.
- Paste it into the "add feed" or "follow" box of your reader. Feedly, Inoreader, NetNewsWire, Thunderbird, Reeder and every other reader take a plain address.
- The reader fetches the feed on its own from then on. Nothing is sent to Google Online Security Blog about you, and there is no account to make.
If your reader refuses the address, run it through the feed checker. It repeats the fetch live and says what came back.
Questions
Is this address official?
It is the address Google Online Security Blog itself serves. We found it linked from the site on https://blog.google/security/ and then fetched it to make sure it works. We do not host or mirror the feed.
How current is the information on this page?
It was all measured on 17 November 2026. Feeds move and get retired, so the generator reruns the checks and the page is rebuilt from the new results. If you want the state of the feed right now, the checker fetches it while you wait.
The feed stopped updating in my reader. Whose fault is it?
Check the feed here first. If it loads and shows recent items, the feed is fine and your reader is the problem, usually because the publisher is refusing its requests. Our guide on feeds that stop working runs through the rest.