Tooleux

Contact

Bug reports, tool requests, corrections, and anything else - every message is read.

Email

The best way to reach me is by email:

contact@tooleux.com

Every message is read. Replies depend on the volume of mail, the time of year, and whether the message requires any research. Most get a reply within a week; some take longer; a few get no reply at all (see below for what those tend to be).

What is welcome

Bug reports. If a tool produces the wrong output, throws an error, or behaves differently from a reference implementation, please say so. The most useful bug reports include: the tool name, the exact input you used, the output you got, and the output you expected. If the output is cryptographic, include the test vector if you have one.

Tool requests. If there is a tool you need and this site does not have it, ask. Not every request can be built, but all are read, and many of the tools on the site exist because someone asked.

Corrections to documentation. Typos, wrong explanations, missing caveats, outdated RFC references - anything wrong on a page is worth fixing.

Security disclosures. If you find a security issue in the site itself (not in the algorithms it implements - those are public standards), please disclose it responsibly by email before publishing. Do not open a public issue first.

General feedback. If the site is useful to you, or if it is not, either is useful to hear.

What will not get a reply

To set expectations honestly, the following tend not to get replies:

  • Requests for help with homework, CTF challenges, or exams.
  • Requests to break, crack, or bypass something you do not have permission to access.
  • Legal, tax, or professional advice questions - I am not qualified to give them.
  • Requests to add advertising, tracking, or analytics to the site.
  • Offers to purchase or acquire the site.
  • Mass-mail, marketing, or SEO solicitations.

Security disclosures

If you find a vulnerability in the site, please email contact@tooleux.com with:

  • A description of the vulnerability.
  • Steps to reproduce it.
  • An assessment of the impact.
  • Your name and how you would like to be credited (optional).

Please do not publish the details publicly until there has been a reasonable opportunity to investigate and fix the issue.

Elsewhere

There are no official social media accounts. This site and its email address are the only official channels.

Last updated: 2026-10-11