CIRCUITO
CARIOCA TI · DOCUMENTATION
♙
Developer tool

Hash & HMAC Tool

Generate and verify SHA-2, SHA-3, HMAC and legacy digests for integrity checks and interoperability.

SHA-256SHA-512SHA-3HMACMD5SHA-1

Hash / HMAC tool

Generate a hexadecimal digest or compare an existing digest using the selected algorithm.

The exact bytes matter: capitalization, spaces and line breaks change the digest.
Required only when HMAC is enabled. Avoid using production secrets in third-party web tools.
HASH

A hash is not encryption

A cryptographic hash maps arbitrary input to a fixed-size digest. It is designed as a one-way transformation: there is no decryption key that recovers the original input from the digest.

SHA-2 / SHA-3

Prefer modern algorithms for new integrity uses

SHA-256 and SHA-512 belong to SHA-2, while SHA3-256 and SHA3-512 belong to SHA-3. Both families are suitable modern choices for cryptographic hashing when the surrounding protocol and implementation are appropriate.

HMAC

HMAC adds authentication with a shared secret

HMAC combines a cryptographic hash function with a secret key. It is used when integrity alone is not enough and the recipient also needs evidence that the message was produced by someone who knows the shared secret.

LEGACY

MD5 and SHA-1 remain only for compatibility

MD5 and SHA-1 are available here to reproduce or verify values encountered in legacy systems. They should not be selected for new applications that depend on collision resistance.

PASSWORDS

Raw hashes are not password storage functions

Passwords should be stored with a password hashing function designed to be deliberately expensive, such as Argon2id or bcrypt through PHP password_hash(). SHA-256, SHA-512 and SHA-3 are fast general-purpose hash functions and are not substitutes for a password hashing scheme.

EXACT INPUT

One invisible character changes the result

Hashing operates on bytes. A trailing space, a newline, different character encoding or a capitalization change produces a different digest. When comparing values between systems, confirm exactly what data each side hashes.

FAQ

Frequently asked questions

What is the difference between a hash and HMAC?+

A hash depends only on the message. HMAC also depends on a shared secret key, providing message authentication in addition to integrity checking.

Should I choose SHA-256 or SHA-512?+

Both are members of SHA-2 and remain suitable modern hash functions. The right choice normally depends on protocol requirements, interoperability, performance and the required digest size.

Is SHA-3 better than SHA-2?+

SHA-3 is a different standardized design, not a mandatory replacement for SHA-2. SHA-2 remains widely used and approved for modern applications.

Why are MD5 and SHA-1 still offered?+

Legacy systems, old checksums and protocols can still expose these digests. They are included for compatibility and verification, not as recommendations for new collision-resistant uses.

Can I store passwords with SHA-256?+

No. Use a password hashing function such as Argon2id or bcrypt through password_hash(). Fast general-purpose hashes are unsuitable for password storage by themselves.

Why does adding a line break change my hash?+

Because hashes operate on the exact byte sequence. A newline is additional input data, so the resulting digest changes.

Is hexadecimal case significant during verification?+

No. Uppercase and lowercase hexadecimal text can represent the same digest bytes. This tool normalizes hexadecimal case before constant-time comparison.

Does HMAC hide the message?+

No. HMAC authenticates the message; it does not encrypt it. Confidentiality requires an encryption mechanism.