How Emailmetry protects your SPF

Emailmetry checks each update before publishing it. If a provider’s records are unavailable or an update fails validation, your last validated SPF record stays in place.

Checks before publication

Flattening an SPF record means replacing provider references with sending addresses. Emailmetry checks that the new record preserves the supported policy’s rules for IPv4 and IPv6 addresses, including rule order and the result for unauthorised senders.

The hosted record is checked again before publication. An update that fails these checks is held back. Read about SPF flattening and the lookup limit.

When a provider’s DNS is unavailable

A failed lookup does not mean a provider has stopped sending email. Emailmetry keeps the last validated policy when DNS answers are incomplete or cannot be verified.

Policy history

Previously validated versions are retained so an earlier record can be restored if needed. Updates are checked after publication. DNS caching means a change or restoration can take time to reach every receiving mail system.

Your DNS and email stay with you

Add the SPF record Emailmetry provides at your existing DNS provider. Emailmetry does not need your DNS account password or API key, and it does not relay or read your email.

Published records are served separately from the management application. An application outage does not delete those records.

Supported SPF rules

• Dynamic rules such as exists, ptr and macros in policy references are unsupported.
• Invalid syntax, broken references and existing SPF evaluation-limit errors need to be resolved before the policy can be managed.
• When you add or remove an email service, update your selection in Emailmetry. Automatic updates follow the providers you choose.

SPF, DKIM and DMARC

SPF identifies the servers allowed to send for your domain. DKIM signs messages, and DMARC checks that passing authentication aligns with the From domain. You still need to configure these with your email providers. Valid SPF alone does not guarantee inbox placement.

How SPF, DKIM and DMARC work together.