DNS change
MX record changed
example.com
Potential mail issue. Mail routing differs from the assigned profile.
DNS visibility for MSPs
Spend less time checking DNS.
Check DNS, websites and certificates across your clients. Spot changes and see what needs attention.
It’s always DNS. Stay ahead of it.
Example checks & alerts
DNS availability
Nameserver not responding
ns1.example.net
No response received during the latest check.
Certificate check
Certificate expires in 14 days
www.example.com
Review renewal before the certificate expires.
Website check
Website responding
www.example.com
HTTPS check passed.
Built around your working day
Fewer repetitive checks.
Clearer answers.
Check in one place
Bring DNS, website and certificate checks into one workflow. Spend less time moving between tools.
Know what changed
Use DNS change history to focus your investigation. Start with the difference, rather than another round of lookups.
Define what good looks like
Compare domains against reusable profiles, including Microsoft 365. Make your expected configuration clear.
The checks behind the confidence
From “something’s wrong”
to somewhere to start.
Keep the signals that matter together.
Give your team a clearer next step.
A clearer starting point
A record changed. Now you know where to look.
DNS changes can explain a sudden mail or service issue. Track record changes and compare the current configuration with the profile you assigned.
Talk to us about Always DNSIllustrative check
MX record changed
example.com
Mail routing differs from the Microsoft 365 profile.
Review changeBeyond the DNS record
Check the website your client depends on.
Bring website checks alongside DNS so you can see whether a site is responding without starting a separate investigation in another tool.
Talk to us about Always DNSIllustrative check
Website responding
www.example.com
The HTTPS check for www.example.com passed.
Check passedKeep renewal in view
Put certificate checks in the same workflow.
Check certificates alongside DNS and websites. Make an approaching expiry visible so your team can review renewal before it becomes a client issue.
Talk to us about Always DNSIllustrative check
Certificate expires in 14 days
www.example.com
Review renewal for www.example.com.
Review renewalReusable DNS profiles
A baseline for
every client.
Set the records you expect.
See where a domain differs.
Define a profile for a setup such as Microsoft 365 email, then compare client domains against it. Give your team a consistent reference instead of rebuilding the same checklist.
Discuss your DNS profilesOne profile. A consistent reference.
Mail routing
SPF record
Autodiscover
Microsoft 365 profile
Expected configuration → clearer comparisons
A more consistent workflow
Check. Compare. Investigate.
- 01 /
Bring your domains together
Keep client DNS, website and certificate checks in one place.
- 02 /
Set your expectations
Use profiles to define the records that should be there.
- 03 /
Focus on the differences
Use check results and change history to guide your next investigation.
Keep a reference to recover from.
Retain zone backups where supported. Give your team a record of previous configurations when access allows.
It’s always DNS. Stay ahead of it.
Make DNS less of
a daily investigation.
Tell us about your MSP and the checks your team repeats.