Domain Monitoring: Setup, What It Checks, and How To Use It

A practical guide to mxio's Domain Monitoring feature. Learn how to add a domain, run the first check, understand the health view, adjust monitoring settings, and use the dashboard day to day.

9 min readproductThomas Johnson

What Domain Monitoring Does

Domain Monitoring watches the email authentication and DNS health of a domain on a schedule.

Instead of running a one-time check only when you remember, mxio keeps checking the domain and records what changed over time. If SPF breaks, DKIM disappears, DMARC stays weak, MX records change, or a blacklist issue appears, the dashboard shows it and your alerts can notify you.

This is the feature you use when you want ongoing visibility, not just a single scan.

Before You Start

To add a domain, you only need:

  • access to the mxio dashboard
  • the domain name itself

You do not need to change DNS just to begin monitoring. mxio can start checking the domain as soon as you add it.

Plans and Check Frequency

Domain Monitoring is available on every plan, with higher limits and faster check intervals on paid tiers.

Plan Monitored Domains Check Frequency History Retention
Free 1 domain Daily 7 days
Basic 5 domains Every 6 hours 30 days
Pro 25 domains Every 30 minutes 90 days
Business 50 domains Every 5 minutes 365 days

You can also run an on-demand check at any time with Check Now.

The Fast Version

The real setup flow is simple:

  1. Add the domain
  2. Let the first check run, or click Check Now
  3. Review the health table
  4. Adjust settings if needed
  5. Leave the domain monitored and use alerts/history when something changes

There is no SPF-style verification step and no DMARC-style DNS handoff required just to turn monitoring on.

Step 1: Add the Domain

Start from the Domains section of the dashboard and click Add Domain.

Enter the domain in plain form:

example.com

Do not include http://, https://, or www.

When you add the domain, mxio creates it as a monitored domain target and schedules health checks for it.

Step 2: Run the First Check

After the domain is added, monitoring starts automatically. The first scheduled check will run shortly.

If you do not want to wait, open the domain and click Check Now in the Domain Health section.

That gives you the first full set of results immediately.

Step 3: Review the Health Results

The domain detail page is built around one question: what is wrong right now, and how serious is it?

The main health area shows individual results for the checks that apply to the domain:

Check What it watches
MX Whether the domain can receive mail and whether MX hosts resolve correctly
SPF Record validity, lookup budget, and common SPF mistakes
DKIM Known selectors, key validity, and missing/broken DKIM setup
DMARC Record presence, policy strength, and reporting configuration
Delegation Whether nameserver delegation is healthy
Domain blacklist Domain-based reputation issues when applicable
MX blacklist Blacklist status tied to the mail path when MX monitoring is enabled

Each check gets its own status and summary. You are not left with a single vague score and no explanation.

Step 4: Adjust Monitoring Settings

Each domain has a settings panel with two important tabs:

  • Monitoring
  • DKIM

Monitoring tab

The Monitoring tab lets you enable or disable individual checks for that domain.

This is useful when:

  • a check does not apply to the domain
  • you want to reduce noise from something you already understand
  • you need to focus attention on the checks that matter most for that domain

DKIM tab

The DKIM tab is where selector management lives. mxio can discover common DKIM selectors automatically when the domain is added, but you can also review and manage selector coverage from the dashboard.

That matters because DKIM is the hardest part of domain health to check without context.

What mxio Discovers Automatically

When you add a domain, mxio does more than store the name.

It can also:

  • auto-discover common DKIM selectors
  • detect the DNS host provider for setup guidance
  • suggest related hosts from MX and SPF records when you want to expand into Host Monitoring

That last part is optional. Domain Monitoring works on its own. The host suggestions are there to help when you want to monitor the infrastructure behind the domain as well.

What Success Looks Like

A first-time user should expect this sequence:

  1. the domain appears in the Domains list
  2. the first check runs automatically or after clicking Check Now
  3. the Domain Health table fills in with statuses
  4. the page shows a health score, check summaries, and timing information
  5. the timeline and history start building as more checks run

If you have that, Domain Monitoring is set up correctly.

Understanding the Dashboard

Domain Monitoring is not just a list of domains. The dashboard gives you a working view of operational state.

Domains list

The main list shows:

  • overall health status
  • per-check status dots
  • when the domain was last checked
  • quick actions such as Check Now, Pause, and Activate

Worst domains float to the top so problems are easy to find.

Domain detail page

The detail page brings together:

  • the current health score
  • last checked and next check timing
  • the full Domain Health table
  • uptime and history views
  • incidents
  • DMARC Reporting entry points
  • related host discovery

This is the page you use when you need to understand a domain, not just confirm that it exists in monitoring.

Status states

The main domain states are:

State What it means
Active Monitoring is running normally
Paused Monitoring is stopped until you resume it
Inactive The domain exists in the account but has not started monitoring yet — typically the brief state between adding a domain and the first check running
Error Something about the target state needs attention

For most users, the meaningful distinction is simple: active domains are being monitored; paused domains are not.

Day-To-Day Use

Once a domain is added, the normal workflow is straightforward.

When everything is healthy

If the checks are green, you mostly leave the domain alone. mxio keeps checking on schedule and adds history over time.

When something changes

When a result moves to warning or failure:

  1. open the domain
  2. review the failing check summary
  3. decide whether it is a misconfiguration, expected change, or temporary issue
  4. rerun Check Now if you want immediate confirmation after a fix

When you need to reduce noise

Open the domain settings and disable the specific checks that are not useful for that domain. This is better than ignoring the domain entirely.

When a domain no longer needs monitoring

Pause it instead of deleting it if you may need the target again later.

Domain Monitoring vs. One-Time Tools

This is an important distinction.

The free Domain Health Check tool is a snapshot. It tells you what is true right now.

Domain Monitoring is the ongoing version:

  • it keeps running
  • it stores history
  • it feeds incidents and activity views
  • it works with your alerting setup

If you only need a quick diagnosis, use the tool. If you need operational coverage, add the domain to monitoring.

Common Situations

A new domain shows no data yet

That usually means the first scheduled check has not finished yet. Open the domain and click Check Now.

DKIM looks incomplete

That is common on the first pass. DKIM depends on selectors, and not every service uses the same names. Review the DKIM tab and run the DKIM Checker if you need deeper detail.

DMARC is warning but not failing

That often means the domain has p=none or another monitoring-only posture. The domain is not broken, but it is not fully enforced either.

MX blacklist depends on MX

MX blacklist monitoring depends on MX being enabled — it checks the IPs behind your MX records. If you disable the MX check, the MX blacklist check is automatically disabled too.

Alerts

When a domain check moves from healthy to warning or failure, mxio can notify you through your configured notification channels. Configure alert preferences in your account notification settings.

Alerts fire on state transitions, not on every check cycle. If SPF breaks, you get one alert when it breaks and one when it recovers. You do not get repeated alerts for the same ongoing problem.

Best Practices

  • Add your important sending domains first
  • Run Check Now after major DNS or provider changes
  • Leave historical monitoring on even when things are healthy
  • Use the settings panel to make the checks fit the domain instead of ignoring noisy results
  • Pair Domain Monitoring with DMARC Reporting when you need both configuration health and sender visibility
  • Use Host Monitoring alongside Domain Monitoring when you also need to track the infrastructure behind your domains
Was this article helpful?

Related Articles