MailSenpai DNS Check

App · 1 action

Check whether a domain's email is set up right: its SPF, DKIM, DMARC and MX records, what to fix, and the exact values to publish. Useful before a campaign, when onboarding a client's domain, or on a schedule to catch a broken record. No account or API key required.

Check a domain's email DNS

Check whether a domain is set up to send and receive email reliably. Reads its SPF, DKIM, DMARC and MX records, says for each whether it is OK, needs fixing or is missing, and gives the steps to fix them with the exact values to publish. A domain that can't be checked (not registered, or a public service such as gmail.com) comes back with a status saying so rather than failing the step. No API key required.

Inputs

DomaindomaintextRequired
The domain that sends your email, such as yourcompany.com. A website or email address works too: the domain is taken from it.
DKIM selectorselectortext
The name your sending service gives its DKIM key, the part before ._domainkey (for example google or s1). Leave empty to try the common ones. Fill it in when the DKIM check can't find a key.
Languagelanguagetext
The language of the results, notes and steps to fix.One of: en (English), it (Italian). Default: en.

Outputs

all_in_ordertrue/false
True when the domain was checked and all four records are OK. Handy for a condition that alerts when something breaks.
cachedtrue/false
True when this is the answer from a check of the same domain in the last 15 minutes.
checked_attext
When the records were read (UTC, ISO 8601).
checksobject
The result for each of the four records.
domaintext
The domain that was checked, taken from what was entered.
messagetext
A sentence or two explaining the summary.
recordsobject
The records found in DNS, as published.
report_pagetext
MailSenpai's web page for the same check, when it has one in the chosen language.
statustext
'checked': the records were read. 'public_mailbox': a public email service such as gmail.com, whose records belong to the provider. 'not_found': the domain isn't registered. 'invalid': not a domain name. 'dns_unreachable': DNS didn't answer, try again later.
summarytext
One line, e.g. '3 things to fix' or 'all in order'.
tipslist
What to do, most important first, with the values to publish.
to_checknumber
How many of the four records couldn't be confirmed.
to_fixnumber
How many of the four records need fixing.
Example output
{
  "all_in_order": true,
  "cached": false,
  "checked_at": "2026-10-19T22:36:13Z",
  "checks": {
    "dkim": {
      "label": "OK",
      "note": "DKIM signature found on selectors google, s1, s2 (2048-bit key).",
      "result": "ok"
    },
    "dmarc": {
      "label": "OK",
      "note": "It exists, with p=reject: email using your domain without permission is rejected. Reports are sent to dmarc@skipflow.com.",
      "result": "ok"
    },
    "mx": {
      "label": "OK",
      "note": "Mail for lodol.com is received by Google Workspace (1 server).",
      "result": "ok"
    },
    "spf": {
      "label": "OK",
      "note": "There is a single SPF record ending with ~all (flags email from servers not listed), using 3 of the 10 allowed DNS lookups. Record: v=spf1 include:sendgrid.net include:_spf.google.com ~all.",
      "result": "ok"
    }
  },
  "domain": "lodol.com",
  "message": "In short: the four records we check are in order. Below you'll find the details and two tips to keep them that way.",
  "records": {
    "dkim_selectors": [
      "google",
      "s1",
      "s2"
    ],
    "dmarc": [
      "v=DMARC1; p=reject; rua=mailto:dmarc@skipflow.com; pct=100; adkim=s; aspf=s"
    ],
    "mx": [
      {
        "host": "smtp.google.com",
        "priority": 1
      }
    ],
    "spf": [
      "v=spf1 include:sendgrid.net include:_spf.google.com ~all"
    ]
  },
  "report_page": null,
  "status": "checked",
  "summary": "all in order",
  "tips": [
    "When you add a service that sends email on behalf of lodol.com (website, CRM, newsletter tool), add its include to the SPF record and turn on DKIM signing there too.",
    "Check the DMARC reports sent to dmarc@skipflow.com every now and then: they show who is sending email on behalf of your domain."
  ],
  "to_check": 0,
  "to_fix": 0
}

On this page