Sygnia

https://www.sygnia.co/blog/

Israeli IR firm; advisories at https://www.sygnia.co/threat-reports-and-advisories/. 2026-05-08 audit: WebFetch returned 5 dated articles Feb 15 - Mar 24 2026 (cleared previously-flagged Cloudflare interstitial). If Cloudflare reappears, fall back to `python3 tools/fetch_source.py url https://www.sygnia.co/blog/`. | 2026-06-20 full audit (v2.62): live=Y, drill=Y. FETCH → webfetch https://www.sygnia.co/blog/ (listing) then webfetch the per-post https://www.sygnia.co/blog/<slug>/ for technical detail. Cloudflare interstitial cleared; if it reappears, fall back to python3 tools/fetch_source.py url <URL>.. AVOID: No bridge needed currently (Cloudflare interstitial not present). Date format on listing is DD.MM.YYYY.. | 2026-07-05 admiralty audit: B, original IR/forensic research from own engagements; live and drillable. Keep active. | 2026-08-13: https://www.sygnia.co/blog/ returned HTTP 403 on direct WebFetch this run, differing from the 2026-07-31 'live and drillable' note, possible anti-bot change; try the jina reader next run before treating as a recipe gap. | 2026-08-15: blog path returned HTTP 403 again on the direct transport; not demoted (an access wall, not content death) and unresolvable this run because the reader pool was exhausted. | 2026-08-15: recipe repaired; the direct WebFetch 403 is bypassed by the bridge's url subcommand, which returned the full blog index this run; fetch_method switched webfetch -> bridge. | 2026-09-30: a dry-run health sweep (no snapshot kept) read a transient 'Please wait while your request is being verified' challenge (shell), and the persisted 07:17:58Z sweep read a no-content variant (irrelevant); re-tested minutes later, `extract https://www.sygnia.co/blog/` returned the full index (newest 2026-09-22), though the challenge and a no-content variant recur intermittently, and https://www.sygnia.co/post-sitemap.xml (Yoast, dated lastmod) is a reliable fallback listing. Recipe unchanged. (2026-09-30T0634Z-audit) | 2026-10-06 (S3): the post-sitemap.xml lastmod values were bulk-reset on 2026-10-05, so the sitemap is not a date signal; working recipe: `extract` the listing for post hrefs, then `extract` each top post and read the 'D Month YYYY' line under the byline. | 2026-10-29 (health sweep): the blog answers 403 on every in-container transport (direct, extract, the reader, feed) and on WebFetch; the Cloudflare challenge recurs intermittently, as noted on 2026-09-30. A 403 is transport blocking and never demotes; retry `extract https://www.sygnia.co/blog/` at the next sweep. | 2026-10-30 (2026-10-30T0255Z-intel, health sweep): `extract` of the blog failed again: direct 403, trafilatura no readable body, the reader relayed the upstream challenge; with WebFetch also 403 (2026-10-29) no transport reads it, so fetch_method is blocked (a 403 never demotes); retry `extract https://www.sygnia.co/blog/` at a later sweep. | 2026-10-31 (2026-10-31T0256Z-intel health sweep): probed again: direct 403, feed /feed/ 403, sitemap 403, trafilatura no body, jina relays the upstream challenge; fetch_method stays blocked and the record joins the handled set in tools/source_health.py (a 403 never demotes).