Loading Empire…

Skip to content

Learn Fix Tools

Search/

Appearance

Filter tools…

Authentication
Deliverability
Monitoring
- Google Postmaster Tools
- Microsoft SNDS
Email Validation
DNS
Inbox Placement
- Inbox Monster
Testing
- Mail-Tester
- GlockApps
Analytics
- Google Analytics 4
Infrastructure
- Cloudflare DNS
Automation
- Customer.io
ESPs
Development
- Swaks
Utilities
- WHOIS / RDAP

Home
Tools
DNS
Google Admin Toolbox CheckMX

Google Admin Toolbox CheckMX

Google Admin Toolbox Check MX for inbound mail DNS sanity checks.

Reading time:: 5 min
Difficulty:: Intermediate
Estimated duration:: 5 min
Prerequisites:: None
Last updated:: 2026-07-15
Author:: empire

Overview

Google Admin Toolbox Check MX for inbound mail DNS sanity checks.

Vendor: Google

Primary purpose

Validate MX and related inbound DNS configuration quickly.

Best for

Checking inbound MX readiness for Google Workspace domains

Common use cases

Verify MX after a cutover
Catch missing address records for MX hosts

Advantages

Focused MX checklist
Browser-based

Limitations

Oriented toward Google’s inbound expectations

When not to use it

You only need outbound authentication inspection

Pricing

Free web utility.

Official website

toolbox.googleapps.com/apps/checkmx/

Inputs and outputs

Typical inputs

Domain

Typical outputs

MX and related DNS findings

Privacy notes

Review each vendor’s data handling before uploading production lists or message content.

Related learning

DNSDomain Name System — the lookup fabric email authentication depends on.

Related problems

CNAME at zone apexA CNAME is placed at the zone apex where other record types are also required.
HELO / EHLO problemsThe SMTP HELO/EHLO hostname is missing, invalid, or inconsistent with reverse DNS.
Inconsistent authoritative answersAuthoritative name servers for the same zone return conflicting data.
Incorrect MX targetMX points to the wrong host name or unreachable mail server.
Missing glue recordsDelegation references in-bailiwick name servers without required glue.
MX record missingNo MX record is published for a domain that should receive mail.
NXDOMAIN for expected nameA name that should exist returns NXDOMAIN from authoritative servers.
Reverse DNS mismatchPTR (reverse DNS) for a sending IP is missing or does not match the forward hostname used in mail.
Stale DNS cache after changeResolvers still serve prior answers after an authoritative change because TTL has not expired.
Wrong TTL for cutoverTTL values are too high for a planned cutover, prolonging mixed old/new answers.

Related tools

digCLI DNS lookup utility for authoritative and recursive inspection of mail-related records.
nslookupInteractive DNS lookup utility commonly used for quick MX and TXT checks.
Google Admin Toolbox DigBrowser-based dig-style DNS lookup from Google’s Admin Toolbox.

Workflows

Open step-by-step: Verify DNS recordsVerify zone authority, MX/address records, and authentication-related TXT publications.

Continue Learning

Open step-by-step: Verify DNS recordsVerify zone authority, MX/address records, and authentication-related TXT publications.

PreviousGoogle Admin Toolbox Dig

Company

About
Contact
Services

Platform

Learn
Fix
Tools

Community

Empire is a living operator community — share practice, follow releases, and help shape the knowledge base.

Newsletter — coming soon

Legal

Privacy Policy
Terms of Use
Disclaimer
Editorial Policy
Cookie Policy

© 2026 Empire Email

Independent educational platform focused on email infrastructure, deliverability, and lifecycle marketing.