---
title: "Website Security And Maintenance For Client Sites | Unolia"
description: "Keep client websites secure before maintenance becomes an emergency. Unolia checks DNS, email, certificates, servers and dependencies on every sync, attaches the fix and logs the proof."
url: "https://unolia.com/use-cases/security-and-maintenance"
locale: "en"
---

# Keep client websites secure before maintenance becomes an emergency.

Silent risks found before they become emergencies.

Most client-site problems start quietly. Unolia checks every project on every sync, queues what it finds with the fix attached, and keeps the servers maintained on schedule.

## Maintenance fails when it depends on memory.

The risky sites are usually the ones nobody has checked recently, not the ones already making noise. Nobody had to remember any of these three.

### The subdomain that pointed at nothing.

A campaign subdomain from two summers ago still delegated to a platform the client stopped paying. Nobody remembered it existed, which is exactly what made it dangerous. Unolia flagged the delegation mistake on sync, and the record was gone before anyone else found it.

### The monitor that was red for a month.

A form endpoint had been failing since February, in a dashboard nobody opened. In Unolia the monitor sits on the client's project, red where the whole team works. The fix took ten minutes once the problem had somewhere to be seen.

### The reboot nobody had to remember.

Kernel updates sat pending on 3 of the 8 servers. The maintenance run applied everything and rebooted only the 3 that asked for it, each step logged under the right client.

## What runs while nobody is looking.

Checks, fixes, runs and records, shipping today.

### DNS and email checks

Conflicts, duplicate or too-permissive SPF, missing DMARC and delegated-subdomain mistakes, caught on every sync.

### Guided fixes

Supported issues carry their fix. You read what will change, apply it, and the recheck confirms it went green.

### Dependency and vulnerability scans

Client repositories checked against published security advisories, with an issue opened on the affected project.

### Server maintenance runs

Ubuntu updates and pending reboots as structured runs with confirmations and a log for every step.

### Monitors in project context

Monitor state sits beside the deploys, providers and DNS of the site it watches, where red gets seen.

### Support windows and end of life

Every PHP version and every recognized package is measured against the support window its makers publish, so one that stopped getting security fixes is flagged with the date it happened.

## From checklist to operating system

| Before | After |
| --- | --- |
| Maintenance depends on whoever remembers the checklist. | Project signals, issues and automations make one repeatable loop. |
| The team discovers risk when a client complains. | The team reviews silent issues before they become visible incidents. |
| Proof of maintenance lives in scattered consoles, if anywhere. | Issues found, fixes applied and runs logged, ready to show the client. |

## Make client-site maintenance visible.

Issues found, fixes applied, runs logged. The maintenance your retainer promises, visible at last.

[Join the waitlist](https://app.unolia.com/register)