Monitoring
Know the day it breaks, not the quarter.
A scan tells you about today. Sites rot quietly: a redirect gets added, a CDN drops a header, a deploy ships a stray noindex. Web Scan re-checks your URL every hour and messages you only when something actually changed.
What sets it off
The score drops five points or more
Small movement is noise and stays quiet. A five-point fall means a weighted check changed state, which means someone shipped something.
A check starts failing that was not failing before
The alert names it. A new noindex, an og:image that started 403ing, a certificate that stopped redirecting. You get the specific one, not "your score changed".
The page stops answering
One message on the way down, not one an hour. It stays quiet until the state changes again.
How it stays private
No account, no email
You get an unguessable link. That link is the monitor. It is how you check on it and how you turn it off. Nothing else is stored about you.
Your webhook never leaves the database
The alert is sent from inside Postgres. The application never reads the webhook back, and no API path can return it, so a leak of the public key would not expose it.
Slack and Discord only
Webhook URLs are restricted to those two hosts, so a stored destination can never be aimed at anything else.