Documentation

Set up your first domain, read what receivers report, fix SPF, DKIM and DMARC, and connect your own agents. Each guide covers one task.

Get started

Get started with MailgloMailglo shows which services send email as your domain, whether that mail passes authentication as receiving mail servers report it, and helps you fix SPF, DKIM and DMARC with changes you approve. This guide takes a new account to its first reports.
Create an accountSign up with a work email and confirm the address. Turning on two-factor authentication adds a second step to sign-in.
Check a domainA public check reads the authentication records any domain publishes in DNS. It needs no account, no ownership proof and changes nothing.
Add and verify your domainMonitoring a domain takes three steps: make the DNS changes, activate monitoring, then wait for the first report. Each is separate: verified access proves control, activating starts monitoring, and reports bring in what receivers saw.
Connect DMARC reportsReceiving mail servers send DMARC aggregate reports to the addresses in your DMARC record's `rua=` tag. Adding Mailglo's address there is how Mailglo learns which services send as your domain and whether their mail passes.

Read a domain overviewEach domain page answers three questions, in order.
Confirm a sending serviceA sending service is anything that sends email as your domain: your mail provider, a newsletter tool, a billing system. Reports show which servers sent mail; Mailglo names the services behind them where it can.
How investigations workAn investigation tracks one authentication question through its fix and its verification. For example: an unfamiliar service is sending as your domain, or a service you use is failing DKIM.
Review and approve changesA change is a reviewed update to a domain's authentication records. Preparing one never changes DNS.

SPFSPF (Sender Policy Framework) lists the servers allowed to send email for your domain. It is one TXT record starting `v=spf1`.
DKIMDKIM adds a signature to each message. Receivers check it against a public key published in your DNS under a selector, for example `s1._domainkey.example.com`.
DMARCDMARC ties SPF and DKIM to the domain people see in the From address. A message passes DMARC when SPF or DKIM passes for that domain. The DMARC record, at `_dmarc.example.com`, also tells receivers what to do with failing mail and where to send reports.

Team and permissionsRoles give a person a starting set of permissions. You can add or remove single permissions for people and agents.
Share a domain with another accountSharing gives another Mailglo account access to one of your domains, for example an agency that helps with your email. You stay the owner.
Client authorityBefore monitoring or changing a client's domain, record that the client authorized you.
NotificationsMailglo tells you when something needs attention or moves forward: an investigation, an approval, a gap in reports, a billing event, a service incident or a setup step, such as a domain whose access Mailglo just verified.
Two-factor authentication and account securityTwo-factor authentication adds a code from an authenticator app to every sign-in, so a stolen password alone cannot open your account. You choose whether to turn it on, and every part of Mailglo works either way.

Connect your agentYour own AI agent can read your domains, explain problems and prepare changes for a person to approve. It uses the same API, permissions and approvals as your team.
Use the command lineAny shell or script can call the Mailglo HTTP API with an agent's token or your own. The OpenAPI description at `/api/openapi.json` lists every operation with its fields, and the [API guide](/docs/api/) explains permissions and errors.
MCPYour AI assistant can work with your Mailglo organization directly: list your domains, explain what needs attention, read DMARC report data and prepare DNS changes for you to approve. Mailglo runs an MCP server for this. MCP (Model Context Protocol) is the standard way AI assistants call tools.
API and permissionsThe Mailglo HTTP API offers every operation the workspace uses. The OpenAPI description at `/api/openapi.json` lists them all.

PricingStart free with one domain. Paid plans have identical features and differ only in how many domains they hold. Each separately managed hostname counts as one domain.
How domains are countedA counted unit is one separately managed hostname.
Trial timingThe trial lets you try paid features on more domains before choosing a plan.
Fair use and service limitsLimits protect every customer's capacity. Reaching one pauses new work; it never adds a usage fee.
Leaving the serviceExport, exit and deletion are handled by support. To ask about your data, email support@mailglo.com.

Get help or report a documentation errorEmail support@mailglo.com, or use the question form on the [support page](/support/), with a question, a problem in your account or an error in these pages. No account is needed.

Agents can read the same pages at /api/v1/docs and the entry-point index at /api/v1/discovery.