Domain health guide
Monitoring client domains as an agency or MSP
When a client's certificate expires or their invoices start landing in spam, the first call goes to whoever built the website or manages the IT. Monitoring client domains lets you make that call yourself, before the client notices, and charge for it.
Why client domains fail quietly
A client's domain is touched by many people who do not talk to each other: the agency, a previous agency, an internal administrator, a marketing contractor who adds a new email tool. Each change is reasonable on its own. The failures appear later and somewhere else: a certificate that no longer renews, an SPF record over the lookup limit, a subdomain pointing at a deleted site.
None of these produce an error anyone sees. The client finds out from their own customers.
What to monitor on every client domain
Five areas cover most incidents.
- Certificates: the expiry and hostname coverage of the certificate actually served, for the site and important subdomains.
- DNS: changes to A, MX, NS and TXT records, with the previous value kept so a change can be explained.
- Email authentication: SPF validity and lookup count, DKIM keys for the selectors in use, and the DMARC policy and report address.
- DMARC aggregate reports: which systems send mail as the client's domain and whether they pass.
- Subdomains: records pointing to resources that no longer exist.
From one-time check to recurring service
A one-time audit is a good first conversation: it shows a client the current state of their domain in terms they can act on. Its weakness is that it is out of date the next time anyone changes a record.
The recurring service is the monitoring: continuous checks, alerts to you rather than to the client, and a periodic report. It is straightforward to price per domain, costs little to deliver once set up, and gives you a reason to speak to the client every month that is not an invoice.
Reporting to clients who do not read DNS
Clients do not want record values. A useful client report says what was checked, what is healthy, what needs a decision from them, and what you already fixed. A single health score with a short list of actions is easier to forward internally than a technical export.
Put your own brand on it. The report is evidence of the work, and a branded PDF with the client's domain on the first page is the artefact that gets forwarded to the person who approves the budget.
Keeping client data separate
When several people in the agency and sometimes the client need access, separate each client's domains and limit who sees what. Read-only access for a client contact is usually enough and avoids accidental changes. Keep an audit trail of who added or removed a domain.
Where to start
Scan three client domains and read the results before deciding anything. In most portfolios at least one has a DMARC record at p=none with no report address, or no DMARC record at all. That finding, shown to the client with a clear next step, is usually enough to start the conversation about ongoing monitoring.
What an incident costs you
When a client's certificate expires on a Saturday, the agency loses more than the hour it takes to fix. Someone has to be reachable, find out who controls the hosting, get access and explain to the client why nobody saw it coming. The explanation is the expensive part: the client now believes the site was not being looked after, whether or not certificate renewal was ever in the contract.
The same failure caught two weeks earlier is a five-minute task and a line in a monthly report that says a renewal problem was found and fixed before it affected anyone. The work is nearly identical. The difference is entirely in when it was noticed.
Onboarding a client domain
Most of the value of monitoring comes from knowing who controls what before something breaks. Collect it once, when the client is taken on.
- The domains the client owns, including redirect, campaign and old brand domains.
- The registrar, who holds the login, and when each domain expires.
- Where DNS is hosted, which may differ from the registrar, and who can edit it.
- Where the website is hosted and how its certificate is renewed.
- The mailbox provider and every other system that sends mail as the domain.
- A baseline scan of each domain, saved, so that later changes can be compared with a known state.
- A named contact at the client for decisions, and an agreed way to reach them urgently.
The first findings are usually the same
Baseline scans of small-business domains turn up a familiar set of problems. Naming them in advance helps when explaining to a client why the audit is worth doing.
- No DMARC record, or p=none with no report address.
- An SPF record that lists a provider the client left years ago, or two SPF records.
- A newsletter or invoicing tool sending mail that is not aligned with the domain.
- A certificate on a subdomain that nobody knew existed.
- DNS records pointing to a previous host or a deleted campaign site.
- A registration set to expire with auto-renew off, tied to a former employee's email address.
example.com. TXT "v=spf1 include:old-host.example include:_spf.google.com ~all"
_dmarc.example.com. TXT (no record)Access you need and access you do not
Monitoring a client's public records needs no access at all, which makes it easy to start: there is nothing for the client to grant and nothing that can be broken. Fixing what the monitoring finds does need access, and that is worth arranging properly rather than by sharing a password.
Ask to be added as a user with a limited role at the DNS provider and the registrar, under your own login. Most providers support delegated or team access. It keeps an audit trail, survives staff changes on both sides and can be withdrawn cleanly when the engagement ends.
Packaging it as a service
Clients buy outcomes, so describe the service by what it prevents. Three levels cover most agencies, and the difference between them is how much of the fixing is included.
- Watch: continuous monitoring and a monthly report. The client or their IT contact acts on findings.
- Watch and fix: the same, plus the agency resolves findings within its access, such as DNS and mail authentication records.
- Managed: the agency also owns certificate renewal, registrar renewals and the DMARC rollout to an enforcing policy.
What the monthly report should say
The report is the visible part of the service and the document the client forwards to whoever approves the invoice. Write it for that reader.
- One line on overall status: healthy, needs attention or action required.
- What changed since last month, in plain words.
- What was found and already fixed, with the date.
- What needs a decision from the client, with a recommendation and the consequence of doing nothing.
- Dates coming up: certificate and registration expiries in the next sixty days.
- A short note on what was checked, so that a clean report is understood as work done rather than nothing happening.
A DMARC project for a client
Moving a client domain from no DMARC record to an enforcing policy is a well-defined piece of work with a clear end, which makes it a good first project. It also needs the client's involvement, because only they know which systems send their mail.
- Publish p=none with a report address you control, with the client's agreement.
- After two to four weeks, present the list of sending sources from the reports and ask the client to confirm each.
- Fix alignment at each legitimate source. This is where most of the hours go.
- Move to quarantine in steps, then to reject, telling the client before each change.
- Keep monitoring the reports. A new tool added by the client's marketing team will show up there first.
Limits to state in the agreement
Be precise about what the service is. External monitoring observes what is public: DNS, certificates, mail authentication records and whether the site responds. It does not see inside the client's server, does not test the application for vulnerabilities and does not replace backups or patching. A healthy report means the public configuration is intact, not that the client cannot be breached.
State response times as well. Monitoring that alerts at night is only a promise of a night-time response if the agreement says so.
When a client leaves
Offboarding deserves the same checklist as onboarding. Hand over the domain inventory and the last report, remove your own access at the registrar and DNS provider, and stop reports from being sent to your addresses. If the DMARC record's rua address points at a mailbox or service of yours, change it before you close the account, or the client's domain will keep sending reports to an address that no longer exists and they will lose visibility without knowing.
Doing this with CloudSpex
CloudSpex is built around this workflow. Each client's domains are kept separate, checks run on a schedule, alerts go to the agency and reports can be produced as a PDF under your own brand. A client contact can be given read-only access to their own domains. The free scan is a reasonable way to produce the baseline for a prospective client: it reads the public records for one domain and shows what a receiver or a browser would see today.
Frequently asked questions
How many client domains make monitoring worthwhile?
It becomes worthwhile at the first client incident you would rather have prevented. In practice agencies start with their largest clients and add the rest once the reporting routine works.
Should alerts go to the client?
Usually not. Alerts go to the agency, which decides what needs the client's attention. Clients receive the periodic report.
Can clients see their own domains?
In CloudSpex a client contact can be given read-only access limited to their own domains.
Do I need the client's permission to monitor their domain?
The records are public, but monitoring should be part of an agreed service. Changing anything, including publishing a DMARC record, needs the client's consent and access.
How should the service be priced?
Most agencies charge a flat monthly amount per domain or per client, with fixes either included up to a limit or billed separately. A one-time DMARC rollout is usually quoted as a project.
What if the client's IT is handled by someone else?
Then the report is the product. Send findings to both the client and their IT contact, with the recommended action, and record when each was resolved.
Use public checks as a starting point
CloudSpex reads limited public-facing signals. It does not change DNS, website, certificate, or email settings. Confirm the responsible provider and test relevant changes before applying a remediation.
Editorial details
Author and reviewer: CloudSpex. Sources: public technical standards and provider documentation relevant to the topic. Last reviewed: November 10, 2026. We update guides when the product behavior or the underlying guidance changes.