Five tools, five different questions
The tools on this page are small, single-purpose utilities. Each one answers a specific question, so picking the right one first saves time. Every tool also has its own page with a detailed explanation of how it works; this overview is meant to help you decide where to start.
- Password generator: you need a new, random password for an account and want to choose its length and character types.
- Data breach checker: you want to know whether a password you already use, or one of your email addresses, appears in known breach data.
- Email validator: someone gave you an address and you want to know whether it is well formed, whether it belongs to a disposable provider and whether its mail server accepts it.
- Spam score checker: you are writing an email and want a quick heuristic review of wording and formatting that often triggers spam filters.
- Email DNS checker: you manage a domain and want to see whether its MX, SPF and DMARC records are published.
Honest limits
These tools are diagnostic aids, not guarantees. A password that is missing from breach data is not automatically strong, and a breach lookup only covers incidents its data source has collected. Many mail servers accept every recipient or deliberately give vague answers, so the validator often reports a mailbox as uncertain rather than confirmed. The spam checker uses a fixed set of pattern rules, while real spam filters also weigh sender reputation, authentication and engagement, which no text-only check can see. The DNS checker confirms that records exist, not that they are correct.
The server-side tools accept ten requests per minute per client to protect the service and the third-party data sources. For bulk list validation or continuous monitoring, use a service designed for that volume.
Using the tools together with a temporary inbox
The tools complement InboxBurnβs main service, the temporary inbox. A common way to test your own sign-up flow: create an inbox on the home page, register with it in your application and check that the confirmation email arrives. Then paste that email βs subject and text into the spam checker and look up your sending domain in the DNS checker. If something looks wrong, you can fix it before real users are affected.