>_Why trust surfaces drift0%
    Back to blogARTICLE_READY
    Workflow6 min readMay 4, 2026

    Score Watch: how to catch grade drops before your users do

    A practical guide to VibeLeak Score Watch: how it works, how to subscribe, and how to respond when a scheduled rescan detects a grade change.

    Drift

    Security posture degrades silently

    A site that scored Grade A at launch can drift to Grade C within months. New deployments overwrite headers. Infrastructure changes remove controls. Third-party scripts introduce new surfaces.

    Header regressions

    ~35%

    Of drift cases involve a header that was present at launch but missing later.

    Certificate issues

    ~25%

    Expired, misconfigured, or newly untrusted certificates.

    New exposure

    ~20%

    Files or endpoints that were not present in the original scan.

    Infra changes

    ~20%

    CDN, proxy, or hosting changes that altered the trust surface.

    Automation

    Score Watch runs rescans on a schedule and compares grades

    When you enable Score Watch on a saved scan, VibeLeak stores the current grade and re-runs the scan on a regular interval. If the grade changes, you get an email with the before and after.

    What triggers an alert

    Any grade change — up or down — triggers an alert. An improvement is worth knowing about too. It confirms a fix worked or that a deployment had a positive security side effect.

    Configuration

    Enable Score Watch in three clicks

    Score Watch is available for any saved scan when you are signed in. The subscription is tied to the scan result, not the domain, so you can watch multiple scans independently.

    01

    Run and save a scan

    Complete a scan and save the result to your dashboard. Score Watch only works on saved scans.

    02

    Toggle Score Watch

    Open the scan result and enable Score Watch. Confirm your email address for alerts.

    03

    Wait for the first check

    The first rescan runs within 24 hours. After that, checks run on the configured interval.

    Response

    When an alert fires, treat it like a bug report

    The email includes the old grade, the new grade, and a link to the new scan result. Open the result, review the findings, and trace the change to a recent deployment or infrastructure change.

    • Open the new scan result and compare findings to the previous scan.
    • Check recent deployments, CDN changes, or infrastructure updates.
    • Fix the root cause, not just the symptom.
    • Re-run the scan manually to confirm the grade recovered before closing the issue.

    Pro tip

    Add Score Watch alerts to your team Slack or Discord via email forwarding. That way the whole team sees grade changes in real time.

    Habits

    Make Score Watch part of your operational rhythm

    The most effective teams treat Score Watch as a safety net, not an afterthought. Here is how to get the most value from it.

    • Enable Score Watch on every production site after launch.
    • Set up a shared inbox or channel for alerts so they are not missed.
    • Review alert trends monthly to spot systemic issues across your infrastructure.
    • Use grade history to show security improvement to stakeholders and auditors.

    Next action

    Run the scanner against your own site

    The article lands hardest when it turns into a fix list. Scan, close the gaps, and recheck.

    Start scan