Documentation Your domains

Read a domain overview

Until a domain is set up, its page is the setup screen. Once setup is complete, the page has five tabs: Overview, Sending services, DNS records, Activity and Settings.

Where does setup stand?

Until setup is complete, the page lists every DNS record to add on one screen, with each one's status, and a line for domain access, reports and monitoring. You can leave and come back; the page resumes where you were. Once setup is complete, Overview says the first report is on its way until one arrives, then leads with the report chart and one thing to look at.

What have we checked?

MailGlo reads SPF, DKIM, DMARC, MX, MTA-STS, TLS reporting and BIMI records at your domain's nameservers when you add the domain, at setup's check and, while the domain is monitored, every 6 hours. DNS records shows the latest check, with the time it was read, and its health check grades it. The Refresh button reads the records again now and says how old the latest check is.

When a scheduled check finds a record that changed since the check before it, MailGlo sends one notice per domain under Investigation updates, with one email for all the domains that changed together, and DNS records lists what changed. A lookup that fails is not a change. Published records are not proof that your mail passes authentication; receiver reports show that.

What have receivers reported?

Once reports arrive, Overview shows the chart, and View all reports opens the Reports page: totals, the services seen and which checks passed. Sending services lists each service with the question only you can answer: do you use it?

Reported messages by sending service

Overview and the Reports page open with a chart of your plan's report history: the last 90 days on the free plan, the last 365 days on paid plans. It shows how many messages receivers reported each UTC day, one line per sending service. Choose Failing DMARC to see only the messages that failed. View daily counts shows every number in a table.

  • What counts. The receivers' own DMARC results: a message passes when the receiver found DKIM or SPF aligned and passing. MailGlo's own recalculation is not used in the chart. Totals match the report summary for the same days.
  • Which day. A report counts on the UTC day its window ends. A report that covers several days counts once, on its last day.
  • Services. The four busiest services have their own line. Other recognized services are combined as Other services. Shared hosting, unrecognized sources and reports still being processed are Unattributed sources. A service keeps its color and line style when its rank changes.
  • Coverage. A day is complete when a report was counted and the day ended more than 72 hours ago, partial when reports for it may still arrive, and missing when no report was counted. Missing days are gaps in the chart, never zero.
  • History. The chart never reaches behind your plan's report history. When the history is shorter than the chart, the chart says so and starts at the first whole day inside it.
  • No reports in the period. If the domain has reported before but nothing was counted in these days, the chart keeps the dates and coverage and says when the latest report arrived. Before the first report, it says when results will appear.

The chart shows what reporting receivers saw. It does not show every message you sent, and it says nothing about inbox placement.

The other views

  1. Sending services: confirm the services you use.
  2. DNS records: every published record, the health check (the grade and the checks that need attention), hosted records, including hosted MTA-STS and BIMI, and preparing a change.
  3. Activity: the changes prepared and made for the domain, and its notices, such as access verified or a DNS change MailGlo noticed.
  4. Settings: domain access and its value, failure reports, the domain's state and leaving MailGlo for it.
  5. Reports, from Overview: the sending-service chart, coverage, totals, report rows and authentication results over time.

Documentation version docs-2026-10-12.

Found an error, or a question this page does not answer? Email support@mailglo.com.