--- title: You're using a too-old browser | daily.dev description: A blog owner explains why visitors may be seeing an access-denied page: they've implemented bot-blocking measures targeting old browser User-Agent strings,... canonical: https://daily.dev/posts/you-re-using-a-too-old-browser-i6hi44otk twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: You're using a too-old browser | daily.dev og:description: A blog owner explains why visitors may be seeing an access-denied page: they've implemented bot-blocking measures targeting old browser User-Agent strings,... og:url: https://daily.dev/posts/you-re-using-a-too-old-browser-i6hi44otk og:image: https://api.daily.dev/og/posts/i6Hi44oTK.png og:image:alt: You're using a too-old browser og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # You're using a too-old browser **[Planet Golang](https://daily.dev/sources/planetgolang)** · 3 min read · 0 upvotes · 0 comments ## Summary A blog owner explains why visitors may be seeing an access-denied page: they've implemented bot-blocking measures targeting old browser User-Agent strings, which are commonly used by high-volume crawlers (including those gathering LLM training data). The post covers several edge cases — Inoreader and Feedly incorrectly caching blocked responses, Vivaldi users needing to adjust User-Agent Brand Masking settings, and archive.today being indistinguishable from malicious crawlers due to its use of old Chrome User-Agents and suspicious IP practices. The author recommends using archive.org as a better-behaved alternative. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why does Feedly show a blocked page instead of my blog's actual content? Feedly periodically fetches syndication feeds using a fake, old browser HTTP User-Agent header, which gets blocked by anti-crawler measures. It then latches onto that blocked response for its actual feed fetching with its regular Feedly User-Agent. The blog owner cannot fix this on their end; affected users need to contact Feedly support. _Developers running blogs with bot-blocking can track how feed readers mishandle User-Agents on daily.dev._ ### Why is Vivaldi being blocked by a website even though it's up to date? Current versions of Vivaldi can be blocked by anti-crawler measures because by default Vivaldi identifies itself as Google Chrome in its User-Agent string. Changing the 'User Agent Brand Masking' setting in Vivaldi's desktop miscellaneous preferences so it identifies as Vivaldi instead of Chrome resolves the issue. _Vivaldi users running into site compatibility issues like this one find relevant discussions on daily.dev._ ## Similar posts on daily.dev - [Serious editors are a commitment \(at least for me\)](https://daily.dev/posts/serious-editors-are-a-commitment-at-least-for-me--0dokaupm6) · Lobsters · 0 upvotes · 0 comments - [News publishers limit Internet Archive access due to AI scraping concerns](https://daily.dev/posts/news-publishers-limit-internet-archive-access-due-to-ai-scraping-concerns-pfgxshyte) · Hacker News · 2 upvotes · 0 comments - [News Sites Are Blocking Internet Archive Over AI Scraping Fears](https://daily.dev/posts/news-sites-are-blocking-internet-archive-over-ai-scraping-fears-2mqqvfze1) · Hackaday · 0 upvotes · 0 comments - [Scraping websites and bot-protection](https://daily.dev/posts/scraping-websites-and-bot-protection-fnv9adnrq) · A Java geek · 8 upvotes · 0 comments --- [View this post on daily.dev](https://daily.dev/posts/you-re-using-a-too-old-browser-i6hi44otk) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"You're using a too-old browser","url":"https://daily.dev/posts/you-re-using-a-too-old-browser-i6hi44otk","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/you-re-using-a-too-old-browser-i6hi44otk"},"datePublished":"2026-08-07T11:12:56.321Z","dateModified":"2026-08-07T11:13:19.948Z","description":"A blog owner explains why visitors may be seeing an access-denied page: they've implemented bot-blocking measures targeting old browser User-Agent strings,...","image":"https://media.daily.dev/image/upload/s--qPvKM23u--/f_auto/v1722860399/public/Placeholder%2009","thumbnailUrl":"https://media.daily.dev/image/upload/s--qPvKM23u--/f_auto/v1722860399/public/Placeholder%2009","isAccessibleForFree":true,"articleSection":"Planet Golang","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Planet Golang","logo":"https://media.daily.dev/image/upload/s--nkaYE8PY--/f_auto/v1721572510/logos/planetgolang","url":"https://daily.dev/sources/planetgolang"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/you-re-using-a-too-old-browser-i6hi44otk","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"","timeRequired":"PT3M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Planet Golang","item":"https://daily.dev/sources/planetgolang"},{"@type":"ListItem","position":3,"name":"You're using a too-old browser"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/you-re-using-a-too-old-browser-i6hi44otk#faq","mainEntity":[{"@type":"Question","name":"Why does Feedly show a blocked page instead of my blog's actual content?","acceptedAnswer":{"@type":"Answer","text":"Feedly periodically fetches syndication feeds using a fake, old browser HTTP User-Agent header, which gets blocked by anti-crawler measures. It then latches onto that blocked response for its actual feed fetching with its regular Feedly User-Agent. The blog owner cannot fix this on their end; affected users need to contact Feedly support. Developers running blogs with bot-blocking can track how feed readers mishandle User-Agents on daily.dev."}},{"@type":"Question","name":"Why is Vivaldi being blocked by a website even though it's up to date?","acceptedAnswer":{"@type":"Answer","text":"Current versions of Vivaldi can be blocked by anti-crawler measures because by default Vivaldi identifies itself as Google Chrome in its User-Agent string. Changing the 'User Agent Brand Masking' setting in Vivaldi's desktop miscellaneous preferences so it identifies as Vivaldi instead of Chrome resolves the issue. Vivaldi users running into site compatibility issues like this one find relevant discussions on daily.dev."}}]} ```