Generate SHA-1

Compute the SHA-1 digest of text. SHA-1 outputs a 160-bit (40 hex character) value and was long the default for Git object IDs and older TLS certificates. Like MD5, it is deterministic and fast, but it is no longer considered secure against well-resourced collision attacks.

Algorithm

SHA-1 belongs to the SHA-1 family defined in FIPS 180: padded message blocks feed a Merkle–Damgård compression function that updates five 32-bit words. This tool returns the hex encoding of that 160-bit state for your input string. Identical inputs always match; any bit flip in the input avalanche-changes the digest.

When to use it

• Verifying legacy SHA-1 checksums still published by older software
• Exploring Git-era object naming concepts in a controlled demo
• Migrating inventories that list both SHA-1 and newer hashes side by side

Limitations

SHA-1 collision attacks are practical; do not use it for new security protocols, certificate signatures, or password hashing. Prefer SHA-256 or SHA-3 for integrity. Browser computation is fine for short strings; multi-megabyte pastes may lag.

Example

Hello yields SHA-1 digest f7ff9e8b7bb2e09b70935a5d785e0cc5d9d0abf0.

This skill is available over A2A JSON-RPC and REST. When you already know the skill id and export, call execute directly—no discovery step required.

REST example

curl -sS -X POST https://toolplaza.app/api/helpers/execute \
  -H 'Content-Type: application/json' \
  -d '{"skillId":"hashing__SHA-1","export":"hashSha1","args":["Hello"]}'

A2A JSON-RPC example

Send POST https://toolplaza.app/api/a2a with:

{
  "jsonrpc": "2.0",
  "id": "1",
  "method": "message/send",
  "params": {
    "message": {
      "messageId": "uuid",
      "role": "user",
      "parts": [
        {
          "kind": "text",
          "text": "ignored"
        }
      ]
    },
    "metadata": {
      "toolplaza": {
        "skillId": "hashing__SHA-1",
        "export": "hashSha1",
        "args": [
          "Hello"
        ]
      }
    }
  }
}

Full Agent API guide · Skill schema