Contact

Send bug reports, feature requests and site feedback.

For support and feedback, contact fuquanbusiness@gmail.com. Clear reports get a faster, more useful reply.

What to include in a bug report

Tool processing happens in your browser, so a good report needs context I cannot see on my side. Including these details means I can usually reproduce the issue on the first try.

The page URL where the problem happened.
Your browser and version, plus desktop or mobile.
The kind of input you used (no need to share sensitive payloads).
What you expected to happen and what actually happened.

Try a quick self-check first

Many reports turn out to be data issues that these tools surface in seconds. Worth a look before you write in.

Self-check Validate the payload first

Run broken JSON through the formatter to see the exact parser error and line.

Self-check Decode encoded values

Check Base64, URL or HTML-entity values before reporting a data mismatch.

Self-check Check timestamps

Confirm seconds vs milliseconds and timezone before blaming the API.

Self-check Look up the status code

Match the HTTP status against the reference table for likely causes.

Feature requests and feedback

Ideas for new tools, references or workflows are welcome.

Suggest a tool Tell me what you keep reaching for

If a debugging task forces you to leave the site, that is a strong candidate for a new tool.

Improve a reference Flag anything inaccurate or missing

Reference tables should match real-world behavior. Corrections with a source are especially helpful.

Response time Replies are best-effort

This is a focused side project, so expect a thoughtful reply rather than an instant one.

No account is required, and pasted tool input is not saved by this site. Please avoid emailing real secrets, access tokens or private keys when describing an issue.