Check your domain’s email configuration
Prove domain control, collect dated DNS observations and record the decisions that follow.
Source checked: 2026-10-03 · Operational suggestions
Prove control first
Sign in with a verified free account. Add your registered domain and confirm authorization. Give the generated TXT record to your DNS administrator, then verify it. Leave it in place: each manual check confirms control again. Verification lasts 30 days; renewing rotates the challenge.
Know what is checked
The account service queries Cloudflare’s public DNS resolver for MX, SPF, DMARC and up to three supplied DKIM selectors. It does not contact websites, ports, mailboxes or message contents. Aliases, failed lookups and unsupported checks remain unknown or not checked. Three checks per account per rolling 24 hours are included, subject to shared domain and service limits.
Interpret records carefully
Record presence does not prove delivery, SPF evaluation, valid signing or DMARC alignment. A null MX declares no incoming mail. Provider review and tests of real messages are still needed. No overall score or compliance conclusion is assigned. Methods reference RFC 7208 (SPF), RFC 7489 (DMARC), RFC 6376 (DKIM) and RFC 7505 (null MX).
Save a useful review
Each requested check saves private account history. Download an editable copy or explicitly save a review to My saved projects. If you activated that library’s firm program, permitted members can access the saved review. Domain-check authorization stays private; joining a firm never transfers it. Public editing stays in browser memory.
Make decisions, then connect work
Record relevance, reasons, evidence and any follow-up. Only deliberate actions become program work. Firm submission compares the source copy with the original collected report. Deleting check history removes that verification source; existing exports and saved copies remain. Approval does not establish effective configuration or close remediation.
Source & applicability
PRODUCT-DOMAIN — Domain and email check method
Bounded MX, SPF, DMARC and selected DKIM observations through a fixed public DNS resolver after explicit domain proof. DNS observations do not test mail delivery, SPF evaluation, message signing, alignment, website vulnerabilities or regulatory compliance.
SEC-registered and state-registered firms may have different obligations. Have the appropriate professionals review what applies to your firm. No regulatory determination is made here.