Standing service domain-keep-dns-email-records-and-renewals-intact · revised 11 October 2026
Standing service
Keep your domain, DNS and mail records from silently breaking, month after month
We check your domain's public records, expiry dates and certificate against an agreed baseline, tell you what changed, and prepare a correction that restores any drifted record.
This starts a conversation by email. Nothing is charged, and nothing is monitored, until we have agreed scope and terms with you in writing.
The responsibility you hand over
A domain is a quiet single point of failure. Its renewal date, its registrar lock, the records that send mail and show the website, and the certificate all fail without any warning to the people who depend on them. A record changes during someone else's project, a verification record is deleted, an old alias points at a service nobody uses, or a renewal card expires, and the first notice is a customer.
Who it’s for: Owner of a small business whose website, email and booking tools all depend on one domain that nobody actively looks after.
Usually starts when: A past outage came from a lapsed renewal, a changed record or an expired certificate, or the person who set the domain up has left.
The result: The domain's public records stay as agreed in a baseline you have confirmed, expiry dates are watched with warnings in good time, and every month you see what was checked, what changed and what was done about it.
What stays true, and what we do about it
No response-time guarantee is published for this new service. A target is agreed in writing before it starts, set to what a service at this stage can actually keep.
Hours are agreed in writing before the service starts. At launch the service is not staffed round the clock, so we do not offer round-the-clock cover.
What must remain true
- The records in the confirmed baseline still answer as agreed, and any change is noticed and explained
- The domain's public expiry date is more than 60 days away and, where the public record shows it, its transfer-lock status is as agreed
- The certificate served for the agreed names has more than 14 days left
- No record points at a service you no longer use
What we watch
- Public DNS answers for the names in the baseline
- The domain's public registration record, which shows more or less depending on the domain ending
- The certificate served at the agreed names
- Your quarterly confirmation of renewal and lock settings, and any export you give us
When something happens
Scroll the table sideways to read it all.
| When | What we do |
|---|---|
| A baseline record changes, appears or disappears. | We compare it with the baseline, ask you whether it was intended and, if not, prepare the correction for your DNS holder. |
| The bare domain or the www address stops reaching your website. | We report which baseline record differs and prepare a correction restoring it. If restoring the baseline value does not bring the website back, finding the cause is the matching job at its listed price. Priced as: Fix bare domain and www |
| The mail routing records no longer point only at your named email provider. | We show which mail routing records differ from the baseline and prepare a correction restoring them. If restoring the baseline values does not bring mail back, tracing and repairing it is the matching job at its listed price. Priced as: Fix incoming mail routing |
| The SPF, DKIM or DMARC record is missing, duplicated or no longer matches your senders. | We show what changed and prepare a correction restoring the baseline records. A change to your senders, or to a sender's own settings, is the matching job at its listed price. Priced as: Business email out of spam |
| The certificate has less than 14 days left or has expired. | We tell you under the notification target agreed in writing before the service starts. If a DNS record the certificate depends on has drifted we prepare a correction for it; renewing or reissuing the certificate is the matching job at its listed price. Priced as: Expired certificate, Not secure |
| The expiry date is within 60 days or, where the public record shows it, the transfer-lock status changes. | We tell you under the notification target agreed in writing before the service starts, and set out the steps for you to take at your registrar. |
| A month ends. | We send a short written summary: checks run, changes seen and what is still open. |
We do on our own
- Read public DNS, registration and certificate records
- Keep and update the baseline file, once you have confirmed each change
- Prepare corrections (written changes restoring a record to its baseline value) and send you the findings
We ask you first
- Any change to a DNS record, a nameserver or a registrar setting
- Contact with your registrar, DNS provider or any supplier on your behalf
- Updating the baseline for a change you did not request
We escalate to you when
- The expiry date is within 30 days, or a nameserver or transfer-lock change appears that you did not ask for
- A record appears that points at a service you do not recognise, which may be an unauthorised change
- Mail or the website stops working and restoring the baseline does not fix it, which is then handled as the matching job at its listed price
How you know it held. Each month you get the checks and their results, the baseline differences with how each was resolved, and the days left on the domain and certificate. A harmless test record added in the first month proves the check notices a change.
How we keep it true
This service is never finished. Each month's summary shows whether the baseline held, and it continues until you end it.
Make your bare domain and www address both open the same website Job Each time it fires
Repair the DNS records and arrange one redirect so the bare domain and the www address both reach your website, with mail records left exactly as they are.
Each time the website names stop working
A prepared correction is in the monthly price. Finding the cause and repairing beyond it is bought at this job's listed price when you approve it. This job covers zones of up to 40 records; a larger zone is quoted.
Find and fix why mail sent to your domain does not arrive Job Each time it fires
Correct the MX records and, where your host has one, the mail routing setting, so test messages from outside and from your own website reach the right mailboxes.
Each time mail routing drifts
A prepared correction is in the monthly price. Tracing and repairing mail beyond it is bought at this job's listed price when you approve it.
Set up SPF, DKIM and DMARC for business mail going to spam Job Each time it fires
Authenticate mail from your domain across your mailboxes and up to three other sending tools. Check headers and DMARC reports; inbox placement cannot be guaranteed.
Each time authentication records drift
A prepared correction is in the monthly price. A change to your senders or their own settings is bought at this job's listed price when you approve it; the job covers up to four senders.
Clear the “Not secure” warning after your site's certificate expired Job Each time it fires
Find why your site’s HTTPS certificate expired, replace it through your host, check the renewal path where the host exposes it, and set an independent expiry warning.
Each time the certificate lapses
A prepared correction for a drifted record is in the monthly price. Renewing or reissuing the certificate is bought at this job's listed price when you approve it.
What is included, and what is not
- The baseline: every record in the zone, marked as website, mail, authentication, verification or other, confirmed by you
- A prepared correction (a written change restoring a drifted record to its baseline value), for your DNS holder to apply, whenever a record drifts from the baseline without your agreement
- A written monthly summary and a quarterly confirmation request
- A list of the accounts that hold the domain, DNS and certificate, who owns each login and the renewal dates, with no credentials in it
Included
- Monitoring of one domain's public DNS answers for the website, mail, authentication and verification names listed in an agreed baseline
- Watching the domain's public registration record for its expiry date and, where that record shows it, its transfer-lock status, and the certificate served for the agreed names; what a public record shows varies by domain ending, and we tell you at the start what yours shows
- A written quarterly request for you to confirm the renewal and lock settings that live inside your registrar account
- A review each quarter for records that point at services you no longer use
- A prepared correction restores one drifted record to its confirmed baseline value, as a written change (record name, type, previous value and baseline value) for your DNS holder to apply. It includes no diagnosis, no new records and no work in another tool. Anything beyond that, such as finding why mail or the website stopped, changing a sender or reissuing a certificate, is the matching job at its listed price.
- A written monthly summary of the checks, the changes seen and what was done about them
Not included
- Renewing the domain, paying fees or holding the registrar login: those stay with you
- Making DNS changes ourselves unless you grant DNS-only access and approve each change
- Fixing mail delivery, certificates or redirects beyond a prepared correction: each repair is the matching job at its listed price
- Out-of-hours cover or any guaranteed response time
- More than one domain, or more than 60 records in the zone, which we agree separately
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
In the first month the baseline lists every record in the zone, each marked website, mail, authentication, verification or other, and you have confirmed it in writing.
Evidence: The baseline and your confirmation
A harmless test record added by your DNS holder in the first month is detected and reported, and the report names the record and the time it was seen.
Evidence: The finding message and the lookup showing the record
Each monthly summary lists every check with its date and result, the days left on the domain and the certificate, and every difference from the baseline with its resolution.
Evidence: The written monthly summary, which you can compare with your own lookups
Sign-off. You confirm the baseline, read each monthly summary and answer the quarterly request. A finding counts as handled when you accept it.
If it fails. If a check cannot be run, the summary says so and why, and it does not count as passed. If the service is not working for you, you can end it at the end of any month.
When it fits, and when we stop
It fits when
- The domain is registered to you or your business and you can give us a read-only export of its DNS each month, or invite us with read access
- A named person on your side can approve DNS changes and confirm registrar settings each quarter
- DNS for the domain is answered by one provider
We stop and tell you if
- The domain's ownership is disputed or the registrant record is not you
- DNS is split across providers in a way that cannot be read as one zone
- Records change often for good reasons, so we agree a different scope with you
What could go wrong
The service only reads public records and files you give us, so ending it changes nothing in your DNS. Any correction we prepare is applied by your DNS holder, who can reverse it from the recorded previous value.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| A drift is noticed too late because checks run on a schedule. | The schedule is written down and no response-time promise is made; the service reduces surprises but is not a live alarm. |
| A legitimate change is reported as a fault, or a fault is accepted as the new baseline. | Nothing joins the baseline until you confirm it, and every change is shown with its previous value. |
| The renewal and lock settings inside the registrar cannot be seen from outside. | The quarterly request asks you to confirm them, and the summary says plainly that they are your confirmation, not our observation. |
Each change or report is checked by a reviewer separate from the work that produced it before it reaches you. No human supervisor is included unless your agreement names one. At launch the work is largely automated, and we say so.
Stays with a person
- You approve every DNS change and every baseline update
- You hold the registrar login and make or approve every renewal
Access we would need
- A DNS export or read-only access to the zone
- Your quarterly confirmation of renewal and lock settings
Questions
How is this different from the one-off DNS jobs?
Each job repairs one fault once. This is a standing responsibility: we keep watching the domain against a baseline you confirmed, month after month, and tell you when something moves.
Will you renew my domain?
No. Renewal and the registrar login stay with you. We tell you in good time and set out the steps.
Can you see my registrar settings?
Not from outside. We read public records and ask you each quarter to confirm renewal and lock settings.
What is a prepared correction?
A written change that restores one drifted record to the value in the baseline you confirmed, for your DNS holder to apply. Finding out why mail or the website stopped, changing a sender, or reissuing a certificate is the matching one-off job at its listed price.
Send an enquiry
Send us
- The domain name and the names of your DNS provider and registrar, if you know them
- Who uses the domain: website, mail provider, booking, newsletter and other tools
- Who should be told when something changes
Later, once you agree
- A DNS export or read-only access to the zone
- The names of the providers that should appear in each mail and verification record
- A named approver and a second contact for urgent findings
- A company-controlled secure handoff agreed before any access: no passwords or registrar logins by ordinary email
The domain, the registrar account and the DNS account stay in your name. We read public records and any export you give us. We change nothing in your DNS unless you grant DNS-only access and approve the specific change.
Email fallback: open your mail app
If website submission is unavailable, review and send the fallback email yourself. An email fallback is not a website receipt. Or write to hello@syntheticindustry.ai with “domain-keep-dns-email-records-and-renewals-intact” as the subject.