Dark Reading (RSS)

https://www.darkreading.com/rss.xml

Mixed quality; verify before use. URL UPDATED 2026-05-08: HTML root https://www.darkreading.com/ returns HTTP 403 to WebFetch, switched to RSS feed which serves cleanly with full dated entries. Cite per-article URLs (drill into <link> from feed). | 2026-06-20 full audit (v2.62): live=Y, drill=Y. FETCH → rss: python3 tools/fetch_source.py feed https://www.darkreading.com/rss.xml 5, full dated entries with substantive summaries; cite per-article <link>. AVOID: Both WebFetch and the bridge 403 the HTML root and brand-new article URLs, do not retry the bridge direct fetch on darkreading.com (it's on the bridge-fails list). | 2026-07-05 admiralty audit: C (was MEDIUM), established trade press but mixed original/re-reported content, corroborate before use; live via RSS, no change (active). | 2026-08-18: health sweep flagged needs-demote on HTTP 404; that is a probe artifact, not the recipe. A serial re-probe this run returned HTTP 200 on the record's own feed URL (https://www.darkreading.com/rss.xml) with a browser user agent, and `fetch_source.py feed <url> 3` parsed three dated in-window items directly with no reader fallback. The HTML root and /latest-news both 403 as the existing note already says, do not probe those. NOT demoted; recipe unchanged and confirmed live. Worth recording that this feed surfaced an in-window item none of the four domain sweeps reported, which is an argument for keeping it in rotation rather than demoting it.