SPF
SPF allows email servers to verify if messages from a domain are sent from authorized hosts.
DKIM adds a digital signature to messages, allowing recipients to verify the email was not altered.
DMARC defines how to handle emails that fail SPF and DKIM checks.
SPF allows email servers to verify if messages from a domain are sent from authorized hosts.
Enter a domain to query this record.
Querying public DNS.
No matching record was found at the queried name.
Conflicting records were found. Review the configuration before interpreting its policy.
The inspected record syntax contains a problem. See the technical details.
The public key format or size does not meet this tool’s local checks.
The key is revoked: the p field is empty.
An RSA key shorter than 2048 bits was found. Review the recommended size for current use.
This tool does not inspect this key type. Its validity has not been confirmed.
Enter the DKIM selector to query its record. An unknown selector does not mean DKIM is absent.
The DNS provider could not be reached. Try again.
The query exceeded 10 seconds. Try again.
DNS reported that the queried name does not exist. This does not establish that the main domain is missing.
The provider returned a DNS error. The record’s presence cannot be determined.
The DNS response is incomplete or uses an unexpected format. Try again.
Review the domain and selector. The complete DNS name must meet format and length limits.
The -all mechanism declares a failure for senders not authorized by earlier mechanisms.
The ~all mechanism declares a soft failure. It does not determine automatic message rejection.
The +all mechanism authorizes any sender that reaches this rule. Review the intended policy.
The ?all mechanism makes no assertion about whether remaining senders are authorized.
The record delegates its policy through redirect. The destination record was not queried.
No all mechanism or redirect delegation was identified. A complete evaluation was not performed.
SPF references, macro expansion and lookup limits were not evaluated.
The record includes terms that need additional analysis beyond this query’s scope.
Mechanisms after all are not reached during evaluation.
A public key with a recognized format was found. This does not confirm that messages are signed.
The public key is published with the t=y testing flag.
The published key does not authorize the email service in its s field.
The h field does not allow SHA-256. Review compatibility; SHA-1 must not be used in current DKIM.
Automatic discovery checks only nine common selectors. Other selectors may exist.
Some selector attempts failed. The DKIM query cannot be concluded.
None of the attempted selectors revealed a key. This does not prove DKIM is absent.
p=none does not request DMARC blocking. Reporting depends on the other settings.
p=quarantine requests suspicious treatment for messages that fail DMARC.
p=reject requests rejection of messages that fail DMARC. The receiver makes the final decision.
The t=y flag indicates DMARC policy testing. Do not interpret the declared policy as full enforcement.
The record uses the legacy pct field. Handling can vary between DMARC implementations.
The record does not explicitly declare p; this inspection uses none under the current rule. Check receiver compatibility.
The query checks only the displayed DNS name; it does not discover parent-domain policies.
This inspection does not send email, validate message signatures or alignment, or guarantee delivery or phishing protection.
Enter a domain to query this record.
