Good reasons to write: a check you think is wrong, a citation you think is wrong, a report that never arrived, a question about the API or the MCP server, an idea for a check that isn't there yet. Press and partnership questions are fine too. I'm reachable, just slower on those.
If you're reporting a bug, include the report link when you have one. It's the fastest way for me to see what you saw. Bear in mind that the link shows the subject and the sender of the message you tested, so send it only if that's fine with you. A screenshot of the finding works when it isn't.
Elsewhere
- GitHub, for code that talks to the API, the MCP server, and issues if you prefer them to email.
- LinkedIn, where I post when something new ships and write about what I'm seeing on real mail.
Two things I don't do
I don't sell consulting through this page, and I don't read tested messages beyond what a bug report needs. Reports are stored so their links keep working, and that is the extent of it. The privacy page has the details, in plain words.
If somebody tested a message of yours and you want that report gone, write from an address at the sending domain, or forward me the report link. I'll remove it.
How long a reply takes
Usually a day or two. If the site itself is down, the health check at /health will tell you before I can. Fixes that make it into the code end up on the changelog, with the date.