NERDTOOLS / DOMAIN DIAGNOSTICS

WORKFLOW / DOMAIN EMAIL AUTHENTICATION

Check the controls behind the From address.

SPF authorizes sending infrastructure, DKIM verifies a cryptographic signature, and DMARC requires one of those identities to align with the domain visible to recipients.

01 /

Verify each independent control.

A passing record in one system does not compensate for a broken identity in another.

  • Keep one valid SPF policy within its processing limits.
  • Publish DKIM keys for the selectors actually used by senders.
  • Route inbound mail through the intended MX providers.
  • Use message headers to verify real authentication outcomes.

02 /

Use DMARC to connect the identities.

DMARC evaluates alignment with the visible From domain and publishes a handling policy for failures.

  • Collect aggregate reports before tightening enforcement.
  • Authenticate all legitimate third-party senders.
  • Review subdomain and alignment modes.
  • Progress toward quarantine or reject only after validating the sending estate.

03 /

Choose the signal you need.

FAQ /

Operational detail.

Do I need both SPF and DKIM?

Using both improves resilience because forwarding can break SPF while a valid DKIM signature may survive. DMARC needs at least one aligned authentication method to pass.

Is p=none secure?

It enables monitoring and reporting but does not request quarantine or rejection of failing messages.

Can public DNS prove a message passed?

No. Inspect the Authentication-Results header or sending-provider logs for the actual message outcome.