SHA256 hash

SHA256 encoded string


Your last 10 encodings

sha256['GBCI' 'CFB' 'WETF']fd74d7a0d30c5c45f88b7325f2fcd6e669f390ed401eab8c5f99b7077c95242d

String "['GBCI' 'CFB' 'WETF']" encoded to other algorithms

Here you can view hashes for "['GBCI' 'CFB' 'WETF']" string encoded with other popular algorithms

MD2 1745ea0ccac185eca11ec2734d264959
MD4 ce22f8811ceb2f58534b2737dc50b1f8
MD5 86f69affc8390b3243e245d471b21d67
SHA1 cb827c500b2419916cd8899bda6171aba667d611
SHA224 6a02ba7f48ec73aada981b5fc428c7ee6d6e3c3992074243ead1889c
SHA256 fd74d7a0d30c5c45f88b7325f2fcd6e669f390ed401eab8c5f99b7077c95242d
SHA384 05dbc77c4e21c43ef747bb58ac6d90b348b83fe0af9309679fb162c553a0a5b2ae9fe26a2d88bc973f554703f12f12a5
SHA512/224 21b9bb94a3b64403c7b6f6dabf96f3f11f6c3a1f1c1952297ab210a9
SHA512/256 0f1d6291310073cc9bcc1c1e58f24dd580d343447ef2a57539a9eb5bdfe8dd19
SHA512 3911aa94794afa12b77cabdc42ad648f938acf0dd5c3db45986788de2845079f998a2bc03d3682aafbe5dc64c5a0c5d2be459d3eced85829a49e8928f7deaed4
SHA3-224 cd8111cbfc976291616b58f43d3803528ccb067f0f8222a20cb509f9
SHA3-256 157f06190556b72be6e7fb18d490d3ecfca6ff948d46ca95ea5a99bcffb7ad71
SHA3-384 c1b1703f9502a48b5dc379a0a8f0a30d766db382e24a890c2f74f1d00d166fcb4f2648d649bf83cab4d532b4c5ee7b48
SHA3-512 475ad12e7be43911536bf709724abf123d76e34cc228e86a8a2d443b66f714a44f541788f2f58c6fb867e20879434db41b8aca7c6003933a61c08ee080e94e5d
RIPEMD128 b00e60ec38a24a570ed7ab22c0f2a2c4
RIPEMD160 ed70b82157251f15b6aff123b165d38bc49545c7
RIPEMD256 b9b4e6b569dfbeb631409e41855ca10b5dde91909354e54b323c388d4200cc9a
RIPEMD320 28509bfe7bae9622e73faedf09d453eaba71e0dbb98e6c3497315342aac2f3dc6d33df700e3c1702
WHIRLPOOL 761015afb157c60b512346be49a49312647db387bb8e878cea8dfc033fd2b521c3eeb58744837de8c7fab4fbcd27e6952f636a9f4800fbddde599987b79fe250
TIGER128,3 12bb3a14864c97557f0349561b3a4ce9
TIGER160,3 12bb3a14864c97557f0349561b3a4ce95521e7dc
TIGER192,3 12bb3a14864c97557f0349561b3a4ce95521e7dcca06558c
TIGER128,4 d683d2f7c3a83172adda4a1f48f9689d
TIGER160,4 d683d2f7c3a83172adda4a1f48f9689d5301392a
TIGER192,4 d683d2f7c3a83172adda4a1f48f9689d5301392ab5d8cefc
SNEFRU e93f38704877cbdc325158ba74f19bfe47ca4099d1fbbd31514db3d6fa16e559
SNEFRU256 e93f38704877cbdc325158ba74f19bfe47ca4099d1fbbd31514db3d6fa16e559
GOST 96bea61c791c9c0170a0c098f660ee26e94f94ae3fa0e7e01f87aa8a6be98f50
GOST-CRYPTO d4b3b3b7c3a8ce6ce7680f0a5a73f7a9b73faf863962afda027d0bdf8ee0f19d
ADLER32 35e204f9
CRC32 0b3ec4d1
CRC32B 8602ab7c
FNV132 1abea123
FNV1A32 2e32cf57
FNV164 f1d75da067cb1303
FNV1A64 9345f868c40d0a77
JOAAT 2cccd826
HAVAL128,3 58584db89e7455bac5b1e55a4113309f
HAVAL160,3 3eb6242325db91c72966803e393cb2a7656a993e
HAVAL192,3 d33624e90aee06fa69f3db8e6d220ed73fde6ec9477148a7
HAVAL224,3 ca70ae75d31cc1263e781944e50033091d6e3aa60bf8a5963b96f61e
HAVAL256,3 9207de47a25161381aded60bf80450a731b2399573e0e58764a16f36600bdd32
HAVAL128,4 7dfa8056e598a4f2cb5aabc543085912
HAVAL160,4 f7b6fd4ffd0d43b2ef95fa8806facf856168a284
HAVAL192,4 21252ef5df9cc5eb75bef3c3377ca9b2ca87e9cb6b8ccd11
HAVAL224,4 11aa0d73c77b1ed4dc6df4723d9c623b9ec8ff05fbe5c97b95179642
HAVAL256,4 a22eab2c7445502032d01fd263167d3174d43375a4f09a9371b6e8369f9b69d1
HAVAL128,5 d314b806286706e5d234ad73d05ae02c
HAVAL160,5 4ae25a681bb406b812dc8676e27d0f8b258f10c9
HAVAL192,5 eab8f4519f5cc4ab7e41755166983d4285c01d1e8a2242d3
HAVAL224,5 de27788f4411dd951127212981cd6563bdb7a7e47ec22604fad3888e
HAVAL256,5 553c75f486a0af219622f21a186b5f6fdd304506241e1eefeef3fbfbb3ba0201

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