Email

Write to [email protected]. For privacy-specific requests, use [email protected].

Reporting a wrong result

Include these five things:

  • The exact URL of the tool.
  • The exact input, copied rather than retyped, if it is not sensitive.
  • The output you expected and the output you received.
  • Your browser and operating system.
  • Whether the same input works in another browser, if you tried.

Do not send production secrets, private keys, session tokens or personal data. If the input is sensitive, replace it with a minimal example that still reproduces the problem. A wrong result can often be reproduced with three values.

Suggesting a tool

Describe the task, not the interface: what you have, what you need, and what you currently use to do it. A tool that already exists in a good form is a lower priority than one that is missing from every free collection. Include the edge cases you run into; they decide whether the page is worth building.

Response expectations

Email is read in batches. A correction with a reproducible example is usually handled first. Feature suggestions are kept on a list and considered when the site is updated. There is no guaranteed response time and no paid support.

Before you write

Check the relevant guide first. Many questions about cron timezones, JSON errors and 502 responses are already covered in the blog. If the page is wrong, say which sentence is wrong and what it should say; that is easier to fix than a general “this is incorrect”.