Edge cases
- Network lookups are point-in-time checks and can change after the result is generated.
Network, IP, DNS, And Security Tools
DMARC checker
Look up a domain's DMARC record and review email policy signals. Uses Convurter servers for lookup or processing. Do not enter secrets.
Server ยท Target sent for a server lookup
Waiting
Uses Convurter servers for lookup or processing. Do not enter secrets.
Input
DMARC checker. This lookup uses public network records and responses. Do not enter secrets or private URLs.
Enter a public domain to run this lookup.
Tool notes
Before you share
Result What you get
Look up a domain's DMARC record and review email policy signals.
Input
domain
Output
dmarc-report
Steps Run order and common questions
- Enter domain for a bounded Convurter server lookup.
- Run the inspection lookup and review the point-in-time response.
- Review the dmarc-report result, then copy or download it if the workbench offers that action.
- Use related retained tools for validation, cleanup, conversion, or the next workflow step.
Is DMARC checker free to use?
Yes. The public lookup is free to use with bounded rate limits.
Are my files uploaded?
No files are uploaded, but the entered lookup target is sent to Convurter servers to fetch the public response. Do not enter secrets.
What should I check before using the dmarc-report result?
Lookup results are point-in-time signals, not a continuous monitoring guarantee. Review the final output before using it in production work.
What can I do after this?
Good next steps include Security headers checker, What is my IP?, and DNS lookup.
Notes Limits, accuracy, privacy
Accuracy
- Lookup results are point-in-time signals, not a continuous monitoring guarantee.
Privacy
- The lookup target is sent to Convurter servers to fetch a bounded public response.
- Do not enter secrets, private tokens, or internal-only hostnames.
Fit If you are unsure, use the related tools and family hub to choose the closest workflow before committing to an output.
Best for
- Point-in-time network, DNS, HTTP, email DNS, SSL, redirect, IP, or password checks that need a quick operational signal.
- Support tickets, implementation QA, and configuration review before deeper security testing.
- A focused inspect task where the expected output is dmarc-report.
Before you start
- This tool runs in the browser, so keep the tab open until the result is created and downloaded or copied.
- Use domains, public hosts, and values you are authorized to inspect.
- Avoid pasting private keys, production secrets, or credentials into lookup-style tools.
- Network answers can differ by resolver, cache, region, and timing.
- Use the report as a decision aid, then route to cleanup, conversion, or verification tools if it finds something notable.
Quality checks
- Treat inspection output as a signal report, not as a guarantee that every possible issue was checked.
- Treat results as a point-in-time signal, not a complete security audit.
- Recheck after DNS, certificate, redirect, or header changes have propagated.
- Escalate critical production security questions to a full security review.
- Copy or download the result only after confirming the displayed output matches the task you intended.
Common mistakes
- Assuming one successful lookup proves every region or client sees the same result.
- Treating a header, SSL, or DNS report as proof that the entire application is secure.
- Ignoring caching and propagation windows after configuration changes.
- Skipping input review because the tool feels instant.
- Treating the first result as final without checking the destination requirement.
Continue the workflow
Use these when the current result is only one step in a longer task.
Verify or clean up
Use these when the output needs checking, cleanup, comparison, compression, or a final share-ready pass.
Handoff Before publishing, importing, or sending output
Good uses
- Check whether _dmarc publishes a policy.
- Review p, rua, ruf, pct, and alignment-related tags before rollout.
Bad inputs
- Expecting it to verify DKIM signing or mailbox placement.
- Treating p=none as wrong when monitoring is intentional.
- Expecting the report to prevent spoofing by itself.
Output checklist
- Confirm the record is at _dmarc for the domain.
- Review policy and report destinations.
- Compare results with SPF, DKIM setup, and sender-platform instructions.
Failure modes
- Missing or multiple DMARC records need DNS review.
- Report destinations may require external verification.
- DMARC policy does not by itself prove every sender is aligned.
Runtime limits
- Server lookup.
- Public DNS record parsing only.
- No mailbox-provider placement or anti-spoof guarantee.