MD4 hash
ClientCompute MD4 hex for legacy Windows NTLM or old protocol compatibility—modern systems should prefer SHA-256.
About MD4 hash
Legacy MD4 digest (hex) for interoperability checks—do not use for new security. The interactive transform on this page runs in your browser tab—Toolcore does not need your paste for the core operation described above.
How to use this page
Paste or type in the main workspace, run the primary action from the toolbar, then copy or download the result. Use Load example when the page offers it, or URL prefill (?q= / ?qb=) so agents and tickets open the same input.
Limits and safety
Utilities here are for development and inspection—do not paste live production keys, PANs, or recovery codes into any browser tab you do not control.
b2cfcd68ff7f40aefc81b6efe7baccd3
Nearby workflows on Toolcore
- Hash identifier — Guess digest type from hex length, Base64 shape, or bcrypt/Argon2 prefixes—heuristic, local only. before you trust a token, digest, or key material in production.
- CRC-32 & CRC-32C — IEEE CRC-32 and Castagnoli CRC32C on UTF-8 text or raw hex bytes—ZIP/PNG family vs iSCSI/protobuf; local only, complements file checksum for whole-file digests. before you trust a token, digest, or key material in production.
- HMAC (SHA-256 & more) — HMAC-SHA-256/384/512/1 in the browser—hex or Base64 for webhooks, signing, and API docs. before you trust a token, digest, or key material in production.
- Bcrypt hash & verify — bcrypt password digests with adjustable cost (bcryptjs)—hash or verify $2a/$2b strings locally. before you trust a token, digest, or key material in production.
Common use cases
- MD4 hash for quick local checks without uploading data.
- Copy results into tickets, docs, or classroom notes.
Common mistakes to avoid
Unexpected input shape
See the intro and how-to notes for accepted formats.
FAQ
Is processing local?
Yes—this runs entirely in your browser.
Agent prefill?
Use q or qb for the main text field when supported.
More tools
Related utilities you can open in another tab—mostly client-side.
Hash identifier
ClientGuess digest type from hex length, Base64 shape, or bcrypt/Argon2 prefixes—heuristic, local only.
CRC-32 & CRC-32C
ClientIEEE CRC-32 and Castagnoli CRC32C on UTF-8 text or raw hex bytes—ZIP/PNG family vs iSCSI/protobuf; local only, complements file checksum for whole-file digests.
HMAC (SHA-256 & more)
ClientHMAC-SHA-256/384/512/1 in the browser—hex or Base64 for webhooks, signing, and API docs.
Bcrypt hash & verify
Clientbcrypt password digests with adjustable cost (bcryptjs)—hash or verify $2a/$2b strings locally.