What's included
- Registration expiry and registrar, read from the registry over RDAP — or WHOIS for the registries RDAP does not cover yet, .pt among them. If a registry cannot be read one day, the last known date is kept.
- SPF as receivers see it — one record, valid, within the 10 DNS lookups every receiver enforces (the classic outage after adding "one more include"), and not ending in +all.
- DMARC and DKIM — whether DMARC exists, is valid and actually enforces a policy (p=none only monitors), and DKIM on the selectors the big mail platforms use, plus any you add for the domain.
- Name servers and MX, compared every day. A change raises a critical alert — it can mean a hijacked domain, or a migration nobody told you about — and every change is kept in the domain's history with its old and new values.
- Alerts where you already look — in Alerts, on the Dashboard and by email to administrators: a domain about to expire (30 days ahead by default, critical at 7), SPF or DMARC missing or wrong, MX or name servers changed, lookups failing three days in a row. They close by themselves once fixed — and an MX or name-server change a week after it happened. DKIM is shown but never alerted, because its selectors can only be guessed.
- No email storm on day one. The first check of a new domain opens its warnings without emailing anyone; only critical problems email straight away.
- Suggest proposes domains from your clients' email domains, their monitored websites and their Microsoft 365 verified domains — tick the ones to add.
- A detail window per domain with the registration, name servers, MX, SPF and each of its lookups, DMARC, the DKIM selectors, the raw records and the change history — and Check now, once a minute, to confirm a fix.
- On the client's page and in the report — a Domains tab on the client's page and a Domains section in the client report.
How it works
- 01
Add the domains
Type them, or let Suggest pick them from what SLApp already knows about your clients, and link each one to its client.
- 02
SLApp checks them every day
From its own servers, against the registries and public DNS resolvers — so you see what the rest of the Internet sees, not what an internal DNS server answers.
- 03
Fix what is wrong
Open the domain to see which record is wrong and why; once it is fixed, Check now confirms it and the alert closes.
- 04
Know when something moves
A later change of MX or name servers shows up at the next daily check, with the old and the new values.
What it needs
- Only the domain names: nothing to install, and no access to the client's DNS or registrar account.
- Any technician can add, edit and check domains; resolving an alert by hand is for administrators.
- Domains are checked once a day, so a change shows up at the next daily check — not within minutes.
Domains & email
Registration expiry, SPF, DKIM and DMARC of every client's domain, checked daily, with alerts before anything breaks.