Is this guide for a cloud Codex environment?

These steps configure your local Codex CLI. A separate environment needs its own MCP configuration and access to the MailVakt endpoint.

Will MailVakt change my DNS or send email as me?

No. Domain checks read public DNS and return findings and suggested fixes. You make any DNS edits yourself. For an inbox test, you send a message to a temporary test address; MailVakt does not send it for you.

Does fixing these records guarantee inbox placement?

No. Authentication is one part of deliverability. Sender reputation, message content and recipient behavior also matter. MailVakt helps you find and address configuration problems.

← All integrations

MailVakt + Codex

Investigate email delivery with Codex

Give Codex evidence from your sending domain while it helps investigate email problems. Turn the findings into concrete DNS changes you can review and apply.

Connect Codex Try a domain check

Free public checks · No DNS access needed · You stay in control of changes

Inspect your domain

Check live email DNS records, including SPF, DKIM and DMARC, without handing over your DNS login.

Understand the findings

Ask Codex to explain failures and help prioritize the problems that could affect delivery.

Get a fix you can review

Get proposed record names and values. MailVakt does not edit DNS; you apply approved changes at your provider.

Get connected

Set up MailVakt in Codex

Install and sign in to the Codex CLI. This guide registers MailVakt in your local Codex MCP configuration.

Run the command below in your terminal to add the remote MCP server.
Run codex mcp list to confirm the entry, then start a new Codex session. For account-linked tools, run codex mcp login mailvakt and complete browser sign-in.
Ask Codex to use MailVakt to check your domain. Review the findings and any suggested DNS changes.

Terminal

codex mcp add mailvakt --url 'https://mcp.mailvakt.com/mcp'

Public checks and inbox tests need no MailVakt account. Sign in when prompted to manage domains or read DMARC summaries. Your assistant may ask you to connect an account during setup.

Setup guidance checked October 9, 2026. Official Codex setup documentation.

Start with a question

Replace example.com with your sending domain, then paste a prompt into Codex.

Use MailVakt to diagnose example.com and summarize what could affect delivery of my app’s emails.

Use MailVakt to check example.com and explain any SPF lookup-limit or DMARC alignment failures.

Use MailVakt to propose the DNS fixes for example.com and write a verification checklist for after I apply them.

Questions

Is this guide for a cloud Codex environment?: These steps configure your local Codex CLI. A separate environment needs its own MCP configuration and access to the MailVakt endpoint.
Will MailVakt change my DNS or send email as me?: No. Domain checks read public DNS and return findings and suggested fixes. You make any DNS edits yourself. For an inbox test, you send a message to a temporary test address; MailVakt does not send it for you.
Does fixing these records guarantee inbox placement?: No. Authentication is one part of deliverability. Sender reputation, message content and recipient behavior also matter. MailVakt helps you find and address configuration problems.

Use MailVakt with another tool