Security & Defacement Alerts (v1)
Security or Defacement Alerts, Instantly
ChangeTower loads your pages like a visitor as often as every 5 minutes, signs in where it has to, and emails you in plain language what appeared.
✓ No credit card · First monitor live in 5 minutes
Every page in this folder is under a monitor. It loads on your schedule, as often as every 5 minutes, stores a dated snapshot on every check, and emails you when your criteria are met. Detection is content and HTML level: the page a visitor gets, not the server behind it.
The screenshot ChangeTower stored on that check: the page as a visitor saw it, kept with the HTML and never edited.
Detection is content-level: ChangeTower reads the words and the HTML the page serves. The screenshot is kept as a dated record, not compared against anything.
One folder for every page you would not want changed quietly: homepage, checkout, sign-in page, legal footer, the member area nobody outside sees. Open a row for what changed and the page as it looked that day.
Set the rules for critical alerts
Write your criteria in plain language. ChangeTower AI reads every change against them: matches reach you right away, the rest is archived.
Criteria in your own words.
No rules engine, no severity matrix. Define what counts as critical, and AI monitoring handles the rest.
One rule, written once. Two ordinary edits archived quietly; the 02:35 change reaches you on the check that finds it.
The pages only signed-in customers see get watched too.
Changes behind a login can sit for months, seen only by the people they target. Record the steps to reach them once, and ChangeTower replays them on every check.
Record the steps once. They run before every check.
Accept the banner, sign in, open the member area. You record the steps once, and the monitor repeats them.
The same four steps your customer takes, run every 5 minutes. A page only they can reach still gets a dated snapshot.
From the defacement alert to a dated record of what the page said.
Explore how ChangeTower improves website security monitoring.
Every monitored page captured on schedule. 2 changes since yesterday, both archived.
A script from a domain not seen on this site before is now loading on the checkout page. The visible page is unchanged.
Summary: The hero headline, supporting line and button were replaced with unrelated promotional content, and an outbound link to a domain not seen here before was added. Matched your rule.
Sent the moment the 02:35 check found it. ChangeTower reports what changed. It does not scan for malware, block, clean up or take the page down.
The hero headline, supporting line and primary button were all replaced with unrelated promotional content, and an outbound link to a domain never seen on this site was added. The navigation, footer and the rest of the page are untouched, which is why nothing looked wrong from a distance.
Claim your prize before it expires. Follow the link below to continue.
This offer is limited and will not be repeated.
The screenshot stored on that check: the page as a visitor found it, kept with its HTML.
Every check in between has a snapshot too, changed or not. Every other change here in the last two weeks came from your own team, in working hours. This one did not, and the record makes that visible.
Turn the cadence up on the pages you would not want changed quietly, and down on the ones that barely move all year. Every setting is per monitor.
Just inherited a site nobody's watching? Monitor it from that tab.
The pages nobody watches are rarely in the runbook: old microsites, inherited client sites, forgotten landing pages. The extension monitors the page you are on.
From open tab to monitored page, in one click.
Three links into a site you just took over, click the icon, say what matters, and the page is monitored.
This page has not been edited since 2024. It is still linked from the footer of every other page on the site, and it still loads for everyone who finds it.
We design and build for independent retailers.
Studio enquiries go to the address in the footer.
Found on a Tuesday, monitored before the tab closes. It joins your other monitors and is archived from the next check on.
The pages worth watching first.
A homepage or a checkout should not change without somebody knowing within the hour. A legal footer changes twice a year. Set frequency per page, as often as every 5 minutes.
Homepages & Landing Pages
Most traffic, loudest failure. Watched for the headline, hero and primary call to action being replaced by content your team never wrote.
every 5 minCheckout & Payment Pages
Where a change costs the most and shows the least. Watched for form fields, submit targets and small print moving while the page still looks right.
every 5 minScripts, Tags & Embeds
The script tags, iframes and embeds the page serves. Watched for one that was not there last check, or an existing one loading from somewhere new.
every 5 minOutbound Links & Redirects
Links and redirect markup added to a page. Watched for anything pointing somewhere your site never pointed before.
every 5 minSign-in & Account Pages
The pages where a customer types a password. Watched for the form, its fields and where it posts, none of which a visitor can see.
every 5 min – dailyNews, Notices & Listings
Anywhere a page publishes a list. Watched for entries appearing in bulk, linking off site, or reading nothing like yesterday's.
hourlyLegal Footers & Required Elements
A privacy link, a copyright notice, a regulator statement or a cookie notice. Watched for the element going missing, the change nobody reports because nobody reads it.
dailyMember & Customer-Only Pages
Portals, billing screens and member areas the public never reaches. The monitor signs in and reads what your customer reads, on your schedule.
dailyError States & Failed Loads
A page that starts returning an error, or stops loading for the monitor, shows up on the check that finds it, alongside the pages still fine. This is a change signal, not an availability guarantee.
every 5 minWhat teams actually use it for.
Find out from a check, not from a customer
The worst version is a support email at nine asking why your homepage is advertising something strange. A monitor on that page turns it into an email at 02:36 with the wording attached.
See what appeared, not just that something moved
"Something changed on the checkout page" starts an hour of guesswork. A plain-language summary naming the script, the link or the field that moved starts the actual work instead.
Watch the pages nobody looks at
The two-year-old campaign microsite, the members-only billing screen, the old landing page linked from every footer. All still serving, and nobody would notice for months. Under a monitor, each is checked as often as the homepage.
Have the record before anyone asks for it
Every check stores a dated snapshot, changed or not, so the timeline writes itself: what the page said before and after, and the exact check that caught it. That is the part nobody can reconstruct afterwards.
Cover every client site, not just the ones that complain
Agencies, hosts and internal platform teams answer for sites they did not build and rarely open. Group each client into their own folder, and add homepages, checkouts and sign-in pages in one pass with bulk setup.
Show a client exactly what their page said, and when
The conversation after an incident is about dates and wording. Dated snapshots, stored exactly as captured and never edited, answer it without relying on anyone's memory or a screenshot somebody took.
Looking after a portfolio rather than one site? Bulk setup adds a list of URLs in one pass.
A monitor watches the page. It does not watch the server.
Worth knowing up front: does this sit next to your security tooling, or instead of it? Next to it.
Everything a visitor can reach, watched from outside
ChangeTower loads your page like a visitor, as often as every 5 minutes, and reads what came back: the content on the screen and the HTML behind it. Anything a visitor can see, you see, on the check that finds it.
- Headline, hero and body content replaced on a public page
- A script tag, iframe or embed that was not there last check
- An outbound link or redirect markup pointing somewhere new
- A form quietly posting to a different address than yesterday
- A required element disappearing: a privacy link, a notice, a footer
- Pages that start returning an error or stop loading for the monitor
- The dated snapshot of all of it, stored on every check either way
Your server, your files, your logs
ChangeTower has a visitor's access, which is the point: it sees what your customers see. It cannot look behind the page. It does not scan, does not judge whether a change is an attack, and never touches anything. It reports what moved, with a timestamp. The rest is yours.
- Malware, virus or vulnerability scanning
- Blocking, cleaning, quarantining or rolling anything back
- Server, file-system, database or log access of any kind
- Firewalls, WAFs and intrusion prevention
- Telling you how a change got there, or who made it
- Uptime monitoring, availability figures or an SLA
The honest version: this is a tripwire on the outside of the building. It will not stop anyone getting in, and it will tell you the moment something inside has moved.
On your own pages, turn these on.
Four of these do most of the work. The other two decide how you hear about it.
AI Monitoring
Alert criteria in your own words: "alert me when a script or an outbound link appears, or when the main content is replaced." Every change gets a plain-language summary, and only matches reach you.
Explore →Keyword Monitoring
Watch for a string appearing or disappearing: a word with no business on your page, or a privacy notice line that belongs in the footer. The alert names the element, not the page.
Explore →Manual User Actions
Member areas, billing screens and staging sites sit behind a banner, a sign-in and two clicks. Record those steps once, and ChangeTower replays them before every check to read the page your customer sees.
Explore →Password-Protected Pages
If a page only exists once you are signed in, the monitor signs in too. Credentials are stored securely and used only to reach that page.
Explore →Scheduled Checks
Set frequency per page: as often as every 5 minutes on the homepage and checkout, weekly on legal pages that move twice a year. Turn it up on the pages you would least like changed quietly.
Explore →Email Notifications
The alert lands in your inbox with the summary attached, so a change at 02:35 is waiting when somebody picks up their phone. Nothing to install, nothing else to watch.
Explore →The questions people ask before they start.
How does website defacement monitoring work?
You name the pages that matter, from the homepage and checkout to the microsites nobody opens, and ChangeTower loads each one like a visitor on the schedule you set. When the content changes it names what appeared or disappeared in plain language, and stores a dated snapshot of the page as it was served.
Is ChangeTower a security tool?
Not in the sense most people mean. ChangeTower is a change monitor pointed at your own pages: no malware or vulnerability scanning, no firewall, nothing sitting between anyone and your site.
It tells you, from outside, that a page is no longer what it was, and exactly what changed. That is the missing signal for many teams: tooling inside watches the server, nobody watches the page.
How quickly will I hear that a page was defaced or changed?
The alert goes out on the check that finds the change: as fast as your cadence, and checks run as often as every 5 minutes. A change at 02:35 reaches your inbox around 02:36.
The limit, plainly: a change made and reverted between two checks passes unseen, because there was nothing different to find. Nothing watching a page from outside on an interval can promise otherwise.
Can it tell me how someone got in, or who did it?
No. ChangeTower reads the page the way a visitor does, with no view of your server, files, database, access logs or accounts. It cannot see a route in or attribute a change to anybody.
It gives you the part hardest to reconstruct afterwards: the exact minute the page changed, and what it said before and after. That is where an investigation starts, not where it ends.
Will it clean it up, block it, or take the page down?
No. ChangeTower reports, it does not act. Nothing here writes to your site, changes a record, restores a backup or touches a file. The site's owner decides what to do, with their own tools.
The value is the head start. The expensive change is the one nobody has noticed, and the gap between 02:36 and a customer's email at nine is most of the damage.
Can you monitor pages behind a login, like a member area or billing screen?
Usually, yes. These are often the pages worth watching most: nobody outside ever looks at them. Record the sign-in as a step before each check, and the monitor reaches the view your customer sees, in a member area, billing screen or staging site. Credentials are stored securely, used only for that page.
The exception is a site that blocks automated access outright: if a page will not load, it cannot be watched. You see that straight away, not after a month of silence.
Will I get an alert every time we deploy?
Not if you write criteria, which is what makes this usable on a site your team edits all day. Say what deserves waking someone up: "alert me when a script or an outbound link appears, or when the main content is replaced", and the AI reads every change against it.
A reworded paragraph, a rotated banner or a tag version bump is classified and archived without an alert. The record stays complete, the alerts stay rare enough to read.
Can ChangeTower watch our JavaScript and CSS files for injected code?
ChangeTower monitors pages, not standalone files, which covers more than it sounds: the HTML a page serves includes its script tags, iframes and embeds. A new tag, or an existing one loading from somewhere else, is a change on the page like any other.
It will not treat a .js or .css file as its own target and tell you its contents changed. If that is what you need, this is not the tool for it.
Can I watch just part of a page, or do I have to watch all of it?
Either. On your own pages, watch the whole thing: the point is catching what you were not expecting, and narrowing the scope narrows what can surprise you.
Selective monitoring is for pages that would otherwise be unreadable: a rotating carousel, a live feed or a "customers are viewing" rail changing every few seconds. Point it at the parts that should be stable, and the noise stops counting as change.
Does it work differently for agencies looking after client sites?
The monitoring is identical; the organising changes. Folders keep each client, brand or property separate, so an agency covering forty sites is not reading one long list, and bulk setup adds homepages, checkouts and sign-in pages in a single pass.
Dated snapshots matter more here than in-house. When a client asks what their page said on the day something went wrong, the record is already there and was never edited.
What is a snapshot, and how long is it kept?
A dated capture of the page: the rendered page and the HTML behind it, stored on every scheduled check, changed or not. Each carries a precise timestamp and stays retrievable.
That lets you say what a page looked like on a given morning, no memory required, and it is why "changed or not" matters: only an unbroken series proves a page was fine at 02:30 and not at 02:35.
Where do security alerts get sent?
Email, Slack or Microsoft Teams. Alert rules decide what is worth waking someone up for, so an injected script reaches the channel immediately while a copy tweak is archived quietly.
How is this different from a WAF or a malware scanner?
A WAF tries to block the request and a scanner looks for known signatures. ChangeTower reads the page a visitor is actually served and tells you what it says now that it did not say before, which catches defacement and injected content that never matched a signature.
Know before your customers do.
Put your homepage, checkout and the pages nobody looks at under a monitor. First monitor live in under 5 minutes.