PAGES

Claim history

A scan request that sets a `discord_webhook` pointing at the local machine, dashboard listener, link-local, multicast, or cloud metadata address now gets a 400 (or a WebSocket `error` event) instead of proceeding; webhooks already saved in queue state or schedules are checked when sent and a refused one is logged. Our best guess
Claim history
  1. Revision 1 · · Our best guess

    A scan request that sets a `discord_webhook` pointing at the local machine, dashboard listener, link-local, multicast, or cloud metadata address now gets a 400 (or a WebSocket `error` event) instead of proceeding; webhooks already saved in queue state or schedules are checked when sent and a refused one is logged.

    machine summarizer

Saved in this browser. Sign in to sync your tools.