DNS and email authentication checker

DNS records route people to websites and mail to inboxes. SPF, DKIM and DMARC provide signals that receiving mail systems can use to evaluate whether messages legitimately represent your domain.

Check a domain’s DNS and mail records

The main checker opens in its existing compact interface. Results are not indexed as public content.

DNS and MX records

A and AAAA records point hostnames to IPv4 and IPv6 addresses. NS records name authoritative DNS servers. MX records tell senders where to attempt mail delivery for your domain.

A domain can serve a website without accepting email. Missing MX records may be intentional, so a checker should not automatically label every domain without mail records as insecure.

How SPF, DKIM and DMARC work

SPF is a DNS TXT policy declaring which mail servers are permitted to send mail using the domain in the SMTP envelope. A sender can pass SPF without the visible From header matching, which is why alignment matters.

DKIM adds a cryptographic signature to outgoing messages, and a public key is published under a selector in DNS. xMyIP checks common selector names as hints; not finding a selector is not proof that DKIM is absent. A genuine DKIM verification also requires a signed message.

DMARC connects SPF and DKIM outcomes to alignment with the visible From domain and states whether receivers should monitor, quarantine or reject failing mail. Actual mail delivery still depends on each receiver’s policy.

Related protection records

CAA records restrict which certificate authorities may issue certificates for a domain. MTA-STS provides an SMTP TLS policy, and TLS-RPT describes where some mail TLS failure reports may be sent. DNSSEC can help protect signed DNS data against tampering when fully deployed.

These records address different threats, so a high score cannot certify a domain as protected against all email abuse. A missing optional feature may be an operational choice rather than a defect.

How to use the checker

Enter a domain such as example.com, choose DNS & mail and review the resulting record information and notes. If you change DNS records, allow time for resolver caching to expire before comparing results.

For mail troubleshooting, compare the public records with your actual mail provider settings and test message headers when needed. The checker is read-only and does not send an email for you.

These remote diagnostic results are point-in-time observations, not a security certification. Scan only systems you own or have permission to test.