Planning policy rollout
Read the current policy before tightening it. Test every legitimate sending stream.
Look up a domain's DMARC record and inspect the public policy used for authentication reporting and enforcement.
DMARC builds on SPF and DKIM and lets a domain publish instructions for messages that fail authentication alignment. Policies commonly include none, quarantine and reject.
EmailValidly queries the public TXT record at _dmarc.yourdomain.com and reports whether a record beginning with v=DMARC1 is present.
This lookup reads the policy at _dmarc for the submitted domain. It checks basic tags and duplicates, not a received message or every parent-domain policy that could apply.

Use the domain whose published policy you want to inspect.
The p tag states a requested treatment for failures; it is not a message pass result.
Review a real received message to assess authentication and its relationship to the From domain.
Illustrative scenarios, not live results for the addresses or records shown. Open a scenario to see the next action.
This policy asks for no DMARC-based quarantine or rejection.
Next action Use reports to assess your legitimate senders.
Receivers apply their own local policies as well.
Next action Check that intended senders authenticate and align.
This tool does not evaluate organisational-domain fallback.
Next action Review the parent-domain policy with your mail administrator.
Read the current policy before tightening it. Test every legitimate sending stream.
Compare the published request with the authentication outcomes in real headers.
No. Receiver policy and authentication behaviour still matter.
No. Use received message headers for that evidence.
That can disrupt legitimate mail. Inventory and test your sending services first.