Contact

How to reach us

Subscribe to the update list on any page and reply to the confirmation message; replies go to the site owner. Plain Dev Tools is run by one person, so replies can take a few days. Include the page address and, for a wrong result, the exact input and what you expected.

Reporting a bug

If a tool gives a wrong answer, that is a bug we want to fix. The most useful report has the tool name, the input that caused it (remove any secrets first), the output you got, and the output you expected with a link to the specification or documentation that says so.

Suggesting a tool or a guide

New tools are chosen for being useful, small and able to run entirely in the browser. Tell us what you do with the tool, which tool you use now, and what annoys you about it. Guides are written from the specifications and vendor documentation they cite, and corrections to a guide are welcome with a link to the source.

What we cannot do

We cannot debug your own code or review configuration with secrets in it. Please do not send tokens, passwords or customer data by email; the tools work on a copy with the sensitive parts replaced.

Who runs the site

See the about page for who builds the site, how it is paid for and how the tools are tested.