> For the complete documentation index, see [llms.txt](https://docs.mailtrap.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mailtrap.io/email-sandbox/testing.md). # Testing Features Comprehensive email testing tools for quality assurance Email Sandbox provides a complete suite of testing tools to ensure your emails look perfect and function correctly across all email clients and scenarios. ## Testing Capabilities


Email Template Inspector	Analyze your email templates in detail. Check rendering, validate structure, and ensure compatibility across different email clients.	Email Template Inspector
HTML Check	Validate your HTML email code for errors and compatibility issues. Get recommendations for improving email client compatibility.	HTML Check
Email Headers and Bcc	Inspect all email headers including hidden Bcc recipients. Verify that your email configuration is correct and secure.	Email Headers and Bcc
Deliverability Tests	Run comprehensive deliverability tests to predict how your emails will perform in production. Check spam scores, authentication, and more.	Spam & Blacklist reports
Bounce Emulator	Simulate various bounce scenarios to test your application's bounce handling. Ensure your system properly processes different bounce types.	Bounce Emulator
Load Testing	Test your email system under high load. Verify performance and identify bottlenecks before they impact production.	Load Testing

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.mailtrap.io/email-sandbox/testing.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.