A DNS amendment, certificate renewal or e-mail service provider change may introduce a regression without immediately rendering the site unavailable. Periodic monitoring can detect these deviations before they become visible to users.
Why repeat the audit?
A one-time audit is a photograph. It confirms the state of a domain at a given moment, but does not protect against future expiration, accidental deletion or incomplete new configuration. The useful starting point is therefore a Reference score, followed by regular checks compared to this result.
1. DNS and IPv6
- presence and consistency of A and AAA records;
- NS servers and expected SOA information;
- lack of resolution to an old infrastructure;
- validity of DNSSEC when activated;
- presence of CAA if certification authorities are limited.
An alert is relevant when an address disappears, a name server changes without any planned operation or validation DNSSEC fails.
2. TLS certificate
Monitoring must verify the name covered, the certification chain, the validity dates and the accepted protocols. An automatically renewed certificate can be valid while omitting a subdomain. A decrease in the number of remaining days is normal; a near expiration, an incomplete string or an uncovered name requires intervention.
3. HTTP availability and security
- correct HTTPS response and redirect from HTTP;
- presence of HSTS, CSP and main protective headers;
- no redirection to an unexpected domain;
- stable HTTP status and security score.
Headers may disappear after a Nginx, CDN or framework change while the page continues to display normally.
4. MX, SPF, DKIM and DMARC
Monitor the presence of MX servers, policy uniqueness SPF and publication of DMARC. DKIM also deserves a check after a messaging migration or a rotation of selector. An absent or disabled e-mail policy can increase the risk of usurpation and deteriorate delivability.
Which frequency to choose?
Daily monitoring is suitable for professional areas: it quickly detects a regression while remaining light. The alert shall not repeat each result. It becomes useful when the score drops, if the number of anomalies increases or if a previously valid control fails.
Enable daily monitoring
InfraCheck sets a baseline score, restarts the audit every day and sends an e-mail only in case of degradation. During beta, an account can monitor up to three domains for free.
Monitoring a domainHow to react to an alert?
- confirm the change with a new analysis;
- Identify the category and control that have regressed;
- check recent changes in the registrar, host or e-mail provider;
- correct the configuration and then restart the audit;
- Keep the result in history to confirm the return to normal.
See also DNS audit prior to production and configuration SPF, DKIM and DMARC OVH.
Published on 23 July 2026.