Disclaimer

Not professional advice

Everything on Stackblip — the tools, the explanations, the reference content — is provided for general informational purposes. It is not security advice, legal advice, or financial advice, and using it does not create any professional relationship. A decoded token, a computed hash, or a status-code explanation is a starting point for your own judgment, not a substitute for it.

Accuracy of tool output

The tools are built carefully: the hash engines are checked against published test vectors, the cron engine follows standard semantics including the day-of-month / day-of-week rule, and the reference content tracks the official IANA registry and current RFCs. But software can contain bugs, specifications do change, and edge cases exist.

For anything consequential — a release checksum, a production token, a schedule that pages people — verify with a second, independent source before you act. The thirty seconds that takes is the cheapest insurance in this profession.

Your responsibility

You are responsible for what you enter into the tools and for how you use their output. The tools run entirely in your browser and never transmit your input — but as a habit, treat any secret you paste into any website, this one included, as potentially exposed, and rotate it if it matters. Decoding a JWT is not the same as verifying it, and a hash on this page is not a substitute for your own security review.

External references

Content on this site references external standards and specifications — RFCs, the IANA registry, vendor documentation — and may link to them. Those references are citations, not endorsements; external sites are outside our control, and specifications evolve. When in doubt, the primary source wins over anything written here.

Trademarks

Product and technology names mentioned on this site — JWT, cron, GitHub Actions, Kubernetes, Cloudflare, Let's Encrypt, and others — are the property of their respective owners. Their use here is purely referential and implies no affiliation or endorsement, in either direction.

Contact

Questions about this disclaimer, or something you believe is wrong on the site: [email protected] or the contact page. Corrections are genuinely appreciated — they make the site better for everyone.