Help Centre

Getting started

1

Enter a domain

Type the domain you want to check — for example, example.com. No http://, no www, just the domain name.

2

Add DKIM selectors (optional)

If you know which DKIM selectors your email provider uses (e.g. google for Google Workspace, dkim1 for some providers), list them as a comma-separated list. DKIM selectors are not discoverable — Mailrecord can only check the ones you tell it about.

3

Read the results

Each record type (MX, SPF, DMARC, DKIM) gets its own card with a plain-language explanation. No composite score, no pass/fail verdict — just what the domain's DNS currently says and what that actually means.

Check a domain

Frequently asked questions

What does Mailrecord check?

Mailrecord reads the published DNS records for the domain you enter: MX (mail exchangers), SPF (authorised senders, with lookup counts against the 10-limit), DMARC (policy, with a plain-language explanation of what it does), and any DKIM selectors you name. It checks only the domain you type — never subdomains and never scans.

My SPF record is over the 10-lookup limit. What does that mean?

An SPF record that triggers more than 10 DNS lookups (counting include, a, mx, ptr, and exists mechanisms) will be silently truncated by receiving servers. Mechanisms after the 10th lookup are never evaluated. This is one of the most common configuration errors that looks correct on a checklist — Mailrecord counts every lookup and reports the actual number against the limit so you can see the gap.

My DMARC policy says p=none. Is that protecting my domain?

No. p=none is a monitoring-only policy. DMARC reports are still generated (if a reporting address is configured), but the receiving server takes no action on messages that fail authentication. The domain is not protected against spoofing. Many organisations set p=none as a starting point to monitor their mail flows, then move to p=quarantine or p=reject once they are confident legitimate mail passes. Mailrecord reads the policy value and explains what it means — it does not treat the presence of a DMARC record as protection.

Why can't you auto-detect my DKIM selectors?

DKIM selectors are not published anywhere discoverable. There is no DNS record or registry that lists which selectors a domain uses. The only way to know a selector is to be told by the person who configured it (e.g. your email provider's documentation). Mailrecord checks exactly the selectors you name and says plainly that others may exist. If we checked no selectors and found nothing, we never report "no DKIM" — because absence of a lookup is not absence of a key.

Can Mailrecord tell me if my email is actually being delivered?

No. Mailrecord reads published DNS records — it does not send test messages, check inboxes, or track delivery. It answers the question "what has this domain told the internet about its mail?" not "is my mail getting through?" The tool's disclaimer on every page makes this clear.

Is the Plus plan available yet? How do I pay?

The Plus plan is still in development and is not yet available for purchase. The Free plan costs $0 — no account, no payment method, no registration. The checkout form shown on the pricing page is a visual demo only; no payment information is collected and no data leaves your browser. When Plus becomes available, the price and features will be published on the pricing page.

Known limitations

No email delivery or authentication verification. Mailrecord cannot tell you whether mail is delivered, whether a message passed SPF/DKIM/DMARC authentication, or whether anyone is spoofing this domain. It reports only what is published in DNS.
No subdomain scanning. Mailrecord checks exactly the domain you type. It never enumerates subdomains, never scans, and never guesses.
DKIM selectors are not discoverable. You must provide the selectors you want checked. The tool never guesses selector names and never reports "no DKIM" when it didn't know where to look.
No accounts, no data storage, no history. Every lookup is standalone. Nothing is cached, saved, or stored server-side. There are no user accounts, no saved preferences, and no way to review past checks.
No scheduled re-checks or monitoring. Mailrecord does not re-check domains on a schedule, send alerts when records change, or notify you of anything. These features are planned for the Plus tier (in development).
No DMARC report ingestion. Mailrecord reads the DMARC policy record — it does not receive, parse, or display DMARC aggregate/forensic reports. That capability is planned for the Plus tier (in development).
No email sender or contact mailbox. Support is not yet reachable by email. There is no mailbox configured on this domain. This page will be updated when a contact address is available.

Contact us

Support is not yet reachable by email — no mailbox has been configured for this domain.

If you have found a bug or have a question about using Mailrecord, please check the FAQ above first. For issues that are not covered there, the owner will need to establish a contact route. This section will be updated when a support address or issue tracker is available.

Note on legal entity: A legal entity (company or individual) that operates this service has not yet been registered. The contact section will be updated with the operator's details once they are available.