Help

Compromise monitor

Check one public page for Safe Browsing, redirects, hidden frames, and miner hosts. Watch it daily for $9, or buy one $79 snapshot.

Who This Topic Is For

Owners and agencies who need a public-page signal before they decide on daily monitoring or a one-time scan.

Prerequisites

Before You Start

Use this checklist to make sure the workflow guidance applies cleanly to your current task.

  • You have the public HTTPS URL.
  • You can open the free checker or the compromise monitor.
Expectations

What To Expect

Use this section to set the right outcome before you start the workflow.

One free read

The checker returns the signal list for that URL and stops. Run it again any time. It does not save a seat.

A quiet first monitor day

The $9 monitor stores the first result and does not email it. Later days email a new failing signal.

Hash stays off

Turn on text hash only if you want mail when that hash changes. The default is off, and it is still not a malware cleaner.

Refund before start

A paid snapshot can be refunded until you start it. After Start snapshot, read the report. The refund button is gone.

Playbook

Step-By-Step Guidance

Follow these steps in order for a reliable and repeatable outcome.

  1. Run the free checker.

    Read Safe Browsing first. A failure there means the check did not clear the URL.

    Then read the redirect, frame, and miner rows.

  2. Start the monitor if the page should be watched.

    Open the compromise monitor, name the site, and choose $9 per month or $90 per year. Leave text hash off unless you want that extra mail.

  3. Buy the snapshot if you also want a Standard scan.

    Pay $79, then decide. Refund stays available while the status is paid.

    Start snapshot runs the scan and closes the refund.

  4. Hand the failing rows to the person who can change the site.

    Use the signal list, or the snapshot Do this next section, as the handoff. Vulnify does not remove the script, the redirect, or the flagged page.

Examples

Worked Examples

These scenarios show how the workflow looks in practice, including the result you should see.

The test page matches malware

The public Safe Browsing test URL returns a malware match. A normal page with a working key returns no match.

Treat a match as a failing signal. Treat a missing key as a failing signal too.

The same shop is already on Website Watch

You add the monitor for an origin that already has an active Watch seat.

Quiet hours, extra recipients, and mutes from that seat are reused. The daily monitor still does not clean the site.

The snapshot is still paid

You paid $79 and have not clicked Start snapshot.

Refund is still available. Starting the snapshot runs the Standard scan and closes the refund.
Operations

Operational Playbook

Use this long-form guidance to execute the workflow consistently across planning, implementation, and validation.

Start with the free check

The checker reads one public URL once. It looks for a Safe Browsing match, a redirect to another host, a hidden frame, a meta refresh, and known miner script hosts. It does not log in and it does not change the site.

A missing key is a failure

If the result says Safe Browsing could not be checked, do not call the page clean. The other rows are separate signals. A match and a missing key are both failures.

Watch the page daily

The monitor is $9 per site per month or $90 per year. The first check is quiet. Later days email a new failing signal. An optional text hash is off until you turn it on.

Buy one snapshot when you need a scan

The snapshot is $79 once. It keeps the external signals and adds one Standard scan. Refund is available while the status is paid and you have not clicked Start snapshot.

Reuse the Watch seat you already have

If that origin already has an active Website Watch seat, the monitor reuses its quiet hours, extra recipients, and mutes. The monitor still does not replace the weekly scan.

What this will not do

None of these products remove malware, install a firewall, or clean the page. The snapshot report ends with a Do this next list from the failing signals. The cleanup still happens on your host.

Validation

Validation Checklist

Use this checklist to confirm the workflow was completed correctly.

  • A missing Safe Browsing key was described as a failure.
  • The monitor price was $9 per month or $90 per year.
  • Refund was offered only before the snapshot started.
Troubleshooting

Common Problems And Fixes

If something does not match expectation, check these common failure modes first.

The result looked clean but the key was missing

Safe Browsing could not be checked is a failed row. Do not tell the site owner the page is clean.

Common failure mode

Monitor checkout will not open

The $9 or $90 Stripe Price ID is missing or the amount does not match. An admin saves it before checkout can succeed.

Common failure mode

Start snapshot removed the refund button

Refund is only available while the status is paid and the scan has not started. After start, read the report.

Common failure mode
FAQ

Compromise monitor FAQs

Common questions for this topic.

No. The checker and the monitor report external signals. The snapshot adds one Standard scan and a next-step list. Cleanup stays on your host.

Next Recommended Action

Continue to the best next page based on where you are in your workflow.