Base URL
Endpoints Overview
Method | Endpoint | Description |
---|---|---|
GET | /hash/ | Generate hash with query parameters |
POST | /hash/ | Generate hash with JSON body |
GET /hash/
Generate a hash using query parameters.Query Parameters
Parameter | Type | Default | Description |
---|---|---|---|
input | string | required | Text to hash |
algorithm | string | sha256 | Hash algorithm |
salt | string | none | Salt to prepend |
iterations | integer | 1 | Number of iterations (1-10000) |
format | string | hex | Output format |
uppercase | boolean | false | Convert to uppercase |
Supported Algorithms
Algorithm | Output Length | Security Level | Use Case |
---|---|---|---|
md5 | 32 chars | Low | Legacy compatibility |
sha1 | 40 chars | Low | Legacy compatibility |
sha256 | 64 chars | High | General purpose |
sha512 | 128 chars | Very High | High security |
sha3-256 | 64 chars | High | Modern alternative |
sha3-512 | 128 chars | Very High | High security |
blake2b256 | 64 chars | High | Fast and secure |
blake2b512 | 128 chars | Very High | Fast and secure |
whirlpool | 128 chars | High | Alternative to SHA |
ripemd160 | 40 chars | Medium | Bitcoin compatibility |
crc32 | 8 chars | None | Fast checksum |
adler32 | 8 chars | None | Fast checksum |
fnv1a32 | 8 chars | None | Fast hash |
fnv1a64 | 16 chars | None | Fast hash |
Format Options
Format | Description | Example |
---|---|---|
hex | Hexadecimal (default) | a591a6d40bf420404a011733cfb7b190d62c65bf0bcda32b57b277d9ad9f146e |
base64 | Base64 encoded | pZFq1Av0IEAKQBFzPPt7GQ1ixlvwvNozW1snfZ2vFG4 |
binary | Binary representation | 101001011001000110100110110101000010111111010000100000010000000100101000000001000101110011001111101101111011000110010000110111010110001011000110101111000010111100110110100010001100101011010111110010011110110100110110111110001010001101110 |
Example Request
Response Format
POST /hash/
Generate a hash using JSON body parameters.Request Body
Example Request
Response Fields
Field | Type | Description |
---|---|---|
input | string | Original input text |
hash | string | Generated hash value |
algorithm | string | Hash algorithm used |
salt | string | Salt used (if any) |
iterations | integer | Number of iterations performed |
format | string | Output format used |
uppercase | boolean | Whether output was converted to uppercase |
length | integer | Length of the hash in characters |
timestamp | string | Generation timestamp |
Error Responses
Missing Input (400)
Invalid Algorithm (400)
Invalid Iterations (400)
Invalid Format (400)
HTTP Status Codes
Code | Description |
---|---|
200 | Success - Hash generated |
400 | Bad Request - Invalid parameters |
500 | Internal Server Error |
Rate Limits
No rate limits! You can make unlimited requests to our API.Security Considerations
Algorithm Selection
Cryptographically Secure (Recommended for security):sha256
,sha512
,sha3-256
,sha3-512
blake2b256
,blake2b512
,whirlpool
md5
,sha1
- Cryptographically brokenripemd160
- Limited security
crc32
,adler32
,fnv1a32
,fnv1a64
- Fast checksums
Salt Usage
Always use salt for:- Password hashing
- Security-critical applications
- User-generated content
- Use unique salt per hash
- Use at least 16 characters
- Use cryptographically secure random salt
- Store salt alongside hash
Iterations
Recommended iterations:- Passwords: 10,000+ iterations
- API keys: 1,000+ iterations
- General purpose: 1-100 iterations
- Fast checksums: 1 iteration
Best Practices
Password Hashing
Data Integrity
API Security
Performance Considerations
Algorithm Performance
Fastest to Slowest:crc32
,adler32
,fnv1a32
,fnv1a64
(very fast)blake2b256
,blake2b512
(fast)md5
,sha1
(medium)sha256
,sha512
(slower)sha3-256
,sha3-512
,whirlpool
(slowest)
Large Input Handling
For large inputs:- Use POST requests instead of GET
- Consider using faster algorithms for non-security-critical applications
- Use fewer iterations for performance-sensitive operations