deliverlensStart with your message.
Send through the platform you already use. Read the authentication, content and spam findings in one report.
Test an emailKnow what your
email is telling you.
Send one message through your usual platform. See the authentication and content evidence, then choose one useful change for the next send.
Check your foundations.
Inspect your SPF, DKIM, DMARC and BIMI records. Understand each finding before changing your DNS.
Explore the toolsMake the knowledge yours.
Build practical email skills with step-by-step lessons, useful guides and answers to common questions.
Visit the AcademyYour next send starts here
One email.
A practical next step.
Create a test address and send a sample email. Your report will help you understand the checks and decide what to improve.
Choose your starting point
Nine tools. A check for each question.
Investigate a domain, an email address or a sending IP. Open a service to see what it checks and get started.
Email Verifier
Check address formatting and whether its domain is set up to receive email.
Verify an emailSPF Checker
Find your published SPF policy and spot duplicate records or configuration problems.
Check SPFDKIM Checker
Look up the public signing key for your domain and DKIM selector.
Check DKIMDMARC Checker
Review your DMARC policy, alignment settings and reporting addresses.
Check DMARCBIMI Checker
Inspect the BIMI DNS record that points to your brand’s email logo.
Check BIMIDomain Blacklist Checker
Look up your domain on the reputation sources connected to Deliverlens.
Check a domainEmail Blacklist Checker
Review the domain reputation associated with an email address.
Check email reputationIP Blacklist Checker
Check a public sending IP against the connected blocklist sources.
Check an IPInbox Placement
Learn how placement testing measures where a test email lands and check current availability.
Explore inbox placementInside your email report
Understand the finding.
Choose your next fix.
A score is a starting point. The individual checks help you understand what happened to your message and where to investigate next.
Authentication
See the SPF, DKIM and DMARC findings for the message you sent, including the identities used to authenticate it.
Content and structure
Review the subject, message structure and link findings. Follow up on the specific issues highlighted in your results.
A focused retest
Make one change, send a fresh message through the same platform and compare the relevant findings.
For the people behind the send
Make testing part of your workflow.
Whether you send campaigns, build transactional emails or look after client domains, start with a repeatable check.
Check the campaign before you send.
Send a sample from your usual platform. Review its authentication and content findings while there is still time to make a change.
Test a campaign emailInvestigate the emails your app sends.
Test a receipt, signup message or password reset. Follow the sending identities, inspect DNS records and bring checks into your integration.
Explore API and MCP setupGive every client a consistent checklist.
Work through authentication and reputation checks for the domains you manage. Retest after a DNS change or a move to a new sending platform.
Find the right checksBuilt for your application and your agent
Bring email checks into the way you work.
Call the REST API from your server, or connect Cursor, Claude Code or another compatible MCP client. Use your own API key with the permissions and allowances attached to your account.
Estimate your API costs“Check fintrate.com’s SPF and explain what needs fixing.”
- 1
Choose an available service
Check access and remaining allowance.
list_services - 2
Start the check
Submit the domain with a unique request identifier.
check_spf - 3
Read the result
Retrieve the findings and discuss the next step.
get_check_result
Learn it. Check it. Put it to work.
A practical place to build your email skills.
Start with the message
Read an email authentication header
Find the SPF, DKIM and DMARC results in a received message and identify the domains behind them.
Solve an SPF problem
Fix multiple SPF records at one DNS name
Understand why duplicate policies fail and work through a safer way to consolidate your senders.
Connect the results
Understand DMARC alignment with one example
Compare the visible From domain with the identities authenticated by SPF and DKIM.
Before your first test
A few questions,
answered.
Start here, or visit the FAQ for more help with tests, authentication and your account.
Browse all FAQsDo I need an account to test an email?
You can start a message test on the website without an account. Create an account to manage API keys, view your workspace and use services included in your plan.
Should I send an email or use a domain checker?
Send a message when you want to inspect what your sending platform actually produces. Use a domain checker when you want to investigate a specific published setting, such as an SPF policy or DKIM key.
Does a good score guarantee inbox delivery?
No. The score summarises the checks performed on that message. Use the individual findings to investigate problems; recipient filters, sender reputation and subscriber behaviour also affect delivery.
Does Email Verifier prove that a mailbox exists?
No. It checks the address format and the domain’s mail routing. It does not contact the recipient’s mailbox or confirm that a future message will be accepted.
Can I use Deliverlens in my application or AI agent?
Yes. Use a named API key for the REST API, or connect a compatible MCP client such as Cursor or Claude Code. The same account permissions, API limits and service allowances apply.
How much does testing cost?
Visit pricing to compare the testing options and estimate API costs. Your account shows the service allowances attached to your current plan.
Your next send starts here
Start with one email.
Send it through your usual platform. Read the findings. Decide what to improve.