Written by the people who run it
The engineers building RUA•Watcher operate production mail infrastructure themselves. Every check exists because someone needed it during a real incident, not because it looked good on a feature list.
Why this exists
We built this for our own mail first
We needed to know when our own authentication broke, and we needed to know before a customer told us. Nothing here was designed to demonstrate a feature. Each check was added the day somebody wished it had existed.
Built by engineers, for engineers
RUA•Watcher checks the DNS, mail and TLS records a domain needs before receivers will accept its mail, and tells you which one broke. Twenty one checks, the mail and DNS ones every ten minutes, with the reports from receivers parsed into something you can read without opening an attachment.
We are a small team and we say so. What we can promise is that the checks are honest about what they found, that a number on this site can be traced to the code that produces it, and that we answer technical questions within a day.
Built for our own domains first
RUA•Watcher began as internal tooling for the mail we send ourselves. It earned its place well enough that we opened it up instead of keeping it behind our own walls.
We are the first to feel a bug
Every change lands on our own monitoring before it reaches anyone else, so a rough edge is our problem before it is yours. That is also why the checks keep getting sharper.
Start with the domain you worry about most
We built these checks for our own mail and run them against our own domains every day. The free plan covers one domain and needs no card.