Real browser screenshots
Each monitored page is rendered in a real browser. You get a full screenshot of the page as it appeared, not a heuristic guess from an HTTP response.
DefaceGuard watches your websites with a real browser, stores the screenshots and checksums, and links every check into a verifiable hash chain. When something changes, a person decides what to do next.
No CDN. No edge proxy. Your checks, your infrastructure, your evidence.
Why DefaceGuard
A status code cannot tell you whether your homepage was replaced. DefaceGuard captures what visitors actually see, then makes every finding checkable.
Each monitored page is rendered in a real browser. You get a full screenshot of the page as it appeared, not a heuristic guess from an HTTP response.
Every capture is checksummed and linked into an append-only hash chain. A report becomes something you can verify, not just something you are told.
Visual changes and check signals are summarized through Plugsky into plain-language findings that help a reviewer understand what may have changed.
Defacement is only one failure mode. Availability, certificate validity and DNS changes are tracked alongside visual checks so context is never missing.
Before anyone raises an incident, compare renders, checksums and chain proof. Separate a real defacement from a template change, cache artefact or false positive.
Assign monitors to teams, receive daily reports, and publish a clear public status page so stakeholders can see current state without asking.
Product overview
DefaceGuard runs in your own environment. It checks your sites, preserves the evidence, summarizes the signal and hands the decision to a human.
A real browser loads the monitored URL and captures a screenshot of the rendered result.
Checksums are computed and linked into the hash chain. Screenshots and signals are retained for review.
Plugsky turns the visual diff and check data into a readable summary of what likely changed.
Teams see the finding in the app and in daily reports. A person validates the claim and performs cleanup.
Inside the product
Two views from the same monitoring run: what the page looked like, and why the finding can be trusted.
Interface illustration. Captures are produced by DefaceGuard's browser checks.
Illustrative record fields. Actual values depend on your deployment.
Features
Purpose-built for self-hosted teams: detection, evidence and response workflow without pretending to be a CDN or a managed cleanup service.
Screenshots of the rendered page, captured on a schedule and on demand for every monitor.
Checksums and chain links make each capture independently verifiable after the fact.
Readable summaries of visual and signal changes, generated through Plugsky.
Availability and infrastructure checks that sit alongside the visual record.
Signature checks add a second signal to visual detection, with results attached to each finding.
Generate rules for your origin or reverse proxy. DefaceGuard suggests; it does not sit in front of your traffic.
Assign ownership, review a daily digest, and keep the whole team looking at the same evidence.
Share current monitoring state with a hosted-in-your-environment status page you control.
Confirm a suspected incident against the baseline and the chain before anyone declares an outage or a hack.
How it works
Simple enough to run yourself, rigorous enough to hand to an auditor.
Point DefaceGuard at a URL and choose what to watch: page render, uptime, certificate and DNS.
The first captures become the known-good reference, sealed with checksums in the hash chain.
New renders, signature results and the Plugsky summary arrive as a finding. Validate the claim against the evidence.
Your team performs cleanup and applies any suggested origin WAF rule. Nothing is changed on your site by DefaceGuard itself.
Get started
Run DefaceGuard in your own environment. Connect a page, capture a baseline and see what a verified finding looks like — without putting a proxy in front of your traffic.
Pricing
No per-scan surprises and no traffic-tier billing. Tell us how many monitors and team members you need, and we will size the license with you.
For a single monitored site: browser screenshots, checksums, hash chain, uptime / SSL / DNS checks and daily reports.
Pricing on request.
Everything in Solo, plus teams, public status page, AI summaries via Plugsky and origin WAF rule generation.
Pricing on request.
For organizations running several deployments: more monitors, signature management with ClamAV / YARA and support for your review workflow.
Pricing on request.
FAQ
No. DefaceGuard is self-hosted: monitors, screenshots, evidence and reports run in your own environment. The app at /app is the interface to your deployment.
No. Cleanup is manual and human-led. DefaceGuard detects changes, preserves evidence, validates the claim and alerts your team. A person reviews the finding and performs the cleanup. There is no guaranteed cleanup SLA.
Each check's checksum is linked to the previous one in an append-only chain. That lets you verify that a captured screenshot or finding has not been altered after the fact, and that the sequence of records is contiguous.
No. DefaceGuard is not a CDN, not an edge WAF, and not DDoS protection. It generates origin-level WAF rules that you can apply at your own origin or reverse proxy. Your traffic does not pass through DefaceGuard.
AI analysis is performed through Plugsky to summarize visual changes and check signals in plain language. It assists a human reviewer; it does not trigger changes to your site.
No native mobile apps. The app is accessed through a browser, and the public status page is a web page you can open on any device.
More answers on the full FAQ page.