SHA256 hash

SHA256 encoded string


Your last 10 encodings

sha256['ATNI' 'DGICA' 'AVA' 'VVPR']2975e021cebf525777c4738358e3b86b07cb2bfe35ad28433e0c5af092d2bd05

String "['ATNI' 'DGICA' 'AVA' 'VVPR']" encoded to other algorithms

Here you can view hashes for "['ATNI' 'DGICA' 'AVA' 'VVPR']" string encoded with other popular algorithms

MD2 aebf174a7286531eeb79eb4bd2bbd17c
MD4 079742ec329510cfc17c4abcde9fdbd8
MD5 2b9d91410e9923f48b8a010e92c48048
SHA1 a2e5ad11a19822d20cf694b40113ad0f22591303
SHA224 4e59d287f4663ca07c5130fd3ce9673fd86353ad7852b6858e2ec7ca
SHA256 2975e021cebf525777c4738358e3b86b07cb2bfe35ad28433e0c5af092d2bd05
SHA384 3d03fc7627e5ec20511c15e128fe11cb1723bb6f5ba285a8295c0d9674c186631d0f142ca9ea42f49a7de53c97f37d6c
SHA512/224 a7ad490e37f10260a533500225313aae97109054d7971a70756f2f91
SHA512/256 65bfc87c40528650e48e24a71e92f72654fc2dfcaa265500bb9c4e7fc0e4b6f4
SHA512 7e23ae32452491a66e2d78324690aa39d64bb5a266dcbfb5ce1cb0e9a8f5b67bd146e72bdd8b9c1f4714a2f86b1ecf909e72bb4856a9f0dc9f99ee3f38065c67
SHA3-224 8b1bb03e482c9c981ea2c81c072e6364d70a9b3b6107ca37693420fb
SHA3-256 10b9952b7e117c5dfa5cb63fe98f203cc6b756f9333c614c06ea86b7f2a4c46c
SHA3-384 9ef0d9075cae0611fb32017794ded30e7bf36a11e89939f7ae17eaf24b44be7e5631716c8b41cb7a30531b1f3db29be0
SHA3-512 557611c201eca0143657f34515efeeff6f41f9d57067b265af30f66ab79e0bffbb34976ff579ab4b051aa6a4e5be3a75d495a74cc296b11c8f05387d5f30447f
RIPEMD128 d09e356b111f346e0ba0e71443539e4f
RIPEMD160 663961d66f81edeb366a135064835846be61a5ce
RIPEMD256 36a13606dd79f6d6f7462bb97f7e520866fe0da36ff9dfcade01315cc4f27990
RIPEMD320 e43b2a3cbc3da7941397ed3f49f567728eededacda44390ce4c2223bea90320c769697bd2b11a28c
WHIRLPOOL cd31d37aa45b06f3c8ec8d877267f6a128043477cd2e7f408612ca7d6c42282c1b967a7ae29d2b9d94e410448addeed91b1ba5107b94db7e0f0c592b806a501e
TIGER128,3 01358d6e468cef8c41ef5e9f6a236124
TIGER160,3 01358d6e468cef8c41ef5e9f6a2361244e2c264a
TIGER192,3 01358d6e468cef8c41ef5e9f6a2361244e2c264a27370fe4
TIGER128,4 62918d6afff1933810572ca07f7dd154
TIGER160,4 62918d6afff1933810572ca07f7dd15433db3505
TIGER192,4 62918d6afff1933810572ca07f7dd15433db3505a8d71f03
SNEFRU 5283655209fb3a0430a77703ed07b1107bd71b6d0e94444ce26f683809f3cd48
SNEFRU256 5283655209fb3a0430a77703ed07b1107bd71b6d0e94444ce26f683809f3cd48
GOST 2e17cae38a3e0d463966feb1f6febc5e1c89ffd541837c0151b32fcee807ac5a
GOST-CRYPTO 42d7fdc2c36270ad2fa806142437ca5af91deaee1aea0eaa8c504af2643ade29
ADLER32 678606fb
CRC32 6ca26b61
CRC32B 38b4587b
FNV132 438b8a65
FNV1A32 7e4fee21
FNV164 6a54dabea77078c5
FNV1A64 c67370458aafa1c1
JOAAT ec83975f
HAVAL128,3 d93cc3c61b5fcd9648080093dec387f9
HAVAL160,3 0d8b796aa03efb85bfc4548a72a38d12bd11d11b
HAVAL192,3 fb0ce00e6be0547f8c07cfbe2c6c5c437b9583a2f880c69e
HAVAL224,3 543e55b3c8f84dcedc3a59b215b2d0192a179873fca6dec1bfc462cc
HAVAL256,3 cb0df723c9ecff300f1cd57e56a6b7bf39e6056146355038fafff1598f32a397
HAVAL128,4 bce7b974d0f42ed1477f1cea24cd9401
HAVAL160,4 1d50898f5cfabac0e36cb5121cf36f0c7be01cf9
HAVAL192,4 2e83e4d0da6e7c6ee917958f34bac9efbaeb7f672df64bbf
HAVAL224,4 c5ec507bace4c7967d6a6dd12fd33ab5c9f76e95a065f43bf045e8b3
HAVAL256,4 37ed3fbeb0bb4411110889a10b336cc821950af93d33dff352bc2de973e2c542
HAVAL128,5 60cf18d5563e01ac1990d12b20f68c2d
HAVAL160,5 8a0205987605fc03ad1fa297e8d00a529e2ece1f
HAVAL192,5 2230c1f6d27bed76527019e72ae732f03f788bfa12964cc5
HAVAL224,5 0194dfbc57a975727b7f89371fa65576c1ca54b7eee9a203cb518725
HAVAL256,5 ed7c56c206198afdc13338e503c840e9cdccb443d0164ef8b0b0900ff6ef49db

Usage FAQ

Usage from Address Bar

You can use direct access to this page from your browser address bar. Type string that you need to encode with algorithm according to next schema:<ALGORITHM>/<PHRASE> For example to visit page that contains hash of "hello world" you can just visit url: The another cool thing is that you can specify "json" or "plain" mode into URL and you will get only HASH in response. Schema of this future:<ALGORITHM>.<OUTPUT:plain|json>/<PHRASE> Example: Will output only: "5eb63bbbe01eeed093cb22bb8f5acdc3"

If you have string that contains complicated urlencoded characters you can send it directly via params to avoid processing of our url parser. Use:
str - for string to encode
algo - for algorithm
output - for output type (empty, "json" or "plain")<ALGORITHM>&str=<PHRASE>&output=<OUTPUT:plain|json>

Usage from Javascript

We have removed CORS restriction so you can use direct access to hash calculator in your javascript applications via AJAX.


var toEncode = 'hello world';
var xhr = new XMLHttpRequest();
xhr.onreadystatechange = function () {
if (xhr.readyState == 4 && xhr.status == 200) {
console.log('JSON of "'+toEncode+'" is "'+JSON.parse(xhr.response)+'"');
};'GET', ''+encodeURIComponent(toEncode), true);
Will output: JSON of "hello world" is "5eb63bbbe01eeed093cb22bb8f5acdc3"

Usage from PHP

You can use direct access to hash in your applications.

PHP Example: <?php
$str = 'hello world';
$url =''.urlencode($str);
$md5hash = file_get_contents($url);
echo 'Hash of "'.$str.'" is "'.$md5hash.'"';
Will output: Hash of "hello world" is "5eb63bbbe01eeed093cb22bb8f5acdc3"

Chains of algorithms

In some cases you can need encode string with two or more algorithms. For these cases we have introduced chains of algorithms. For example if you need to encode string according to this schema md5(sha512(sha1('hello world'))) you can do this by connecting algorithms with a double dash: If you will do this in your address bar you can also use semicolon instead of double dash.;sha512;sha1/hello+world Pay attention that semicolon should be encoded in url, so if you use it not in your browser, you should use '%3B' instead Such approach can be also used with "plain" and "json" mode;sha512;sha1.json/hello+world

You can also use special chain item "b64d" or "base64decode" to make base64 decode. It can help to hash any of not printable characters. Example: will be the same: 5eb63bbbe01eeed093cb22bb8f5acdc3

Carriage Return and Line Feed characters

At present time our text editor doesn't have functionality that can take into account which of those characters you want to keep in string. This problem come from browsers which normalize all of the line endings to "CRLF" ("\r\n") format according to "HTML specification". It means that if you paste from buffer string
"hello\nword" and press "Encode", your browser will convert it to "hello\r\nword" and only after this your browser send FORM to us. As a result we will show you hash of "hello\r\nword" but not "hello\nword"

You can avoid this with encode string to "base64" on your side and use "Chains of algorithms" that described above.

Example 1: Hash from string with only Line Feed (LF) character Text: hello\nworld
Text encoded to BASE64: aGVsbG8Kd29ybGQ=
RESULT: 9195d0beb2a889e1be05ed6bb1954837

Example 2: Hash from string with Carriage Return (CR) and Line Feed (LF) character. This result you will have if you use editor with CR, LF or CRLF symbols.
Text: hello\r\nworld
Text encoded to BASE64: aGVsbG8NCndvcmxk
RESULT: 6a4316b18e6162cf9fcfa435c8eb74c1

How to calculate sha256 hash in PHP with hash function

Since version 5.1.2 PHP contains function hash() that you can use to get sha256 hash from strings.

    $str = '¡Hola!';
    $hash = hash('sha256', $str, false);
    echo '<pre>';
    echo $str.PHP_EOL
         .' &rarr; '.$hash.PHP_EOL
    echo '</pre>';
Please read the privacy policy (agreement of the cookies usage, other websites embedded content, etc.). If you continue to use the site, we will assume that you agree with our privacy policy.
OkPrivacy Policy