Where can I report a reproducible issue?
Email support@sha256online.com or follow Yida-Dev on GitHub below. Include a minimal public-data reproduction, not private files or secrets.
What should a bug report include?
Include the browser and OS version, the page path, selected algorithm, approximate size and exact reproduction steps using nonsensitive example data.
Should I attach the original private file?
No. Reproduce the issue with an empty file or abc whenever possible. There is no file-attachment endpoint here.
Should I include an HMAC secret?
No. Use a made-up key for a reproducible example and never disclose the actual shared secret.
How can I report a mismatching result?
State the algorithm, input encoding and whether HMAC was enabled. Use a public test string and independently reproducible expected value.
Can I submit a problem through a form?
This page has no submission form or automatic feedback recorder. It links the maintainer’s profile instead.
Will a support link transmit my current input?
The profile link is a fixed URL with no query containing your inputs. External references use a no-referrer policy.
Is there a guaranteed response time?
No response-time commitment is published. A clear, minimal reproduction makes an issue easier to assess.
SHA256 Online