Calculators · Security · 1 endpoint
Password Strength
Scored the way an attacker attacks — zxcvbn's pattern matching against common passwords, names, and keyboard walks, with a crack-time estimate.
- Status
- Operational
- Price
- 1 credit / request
- Rate limit
- 300 / 60s
- Cache
- None
- Requests
- 0
Endpoint
How to call it
GET/v1/security/password-strength
Code
Request — cURL
v1
curl https://api.diraz.co.id/v1/security/password-strength \
-H "Authorization: Bearer drz_live_…"For AI agents
Callable through the MCP server with the same key:
call_api {"endpoint":"password-strength","params":{"password":"correct horse battery staple"}}Parameters
- passwordstring · required
- The password to score. Never logged, never stored.
Example response
200 OK
JSON
{
"data": {
"score": 4,
"verdict": "very strong",
"guesses": 10000000000000,
"crack_time": "centuries",
"crack_time_read": "centuries",
"feedback": { "warning": null, "suggestions": [] }
},
"meta": {
"request_id": "req_7Q2fK4mZ"
}
}- score / verdict
- 0-4 and the word for it.
- crack_time
- Offline fast-hashing estimate — the honest threat model.
- feedback.warning / suggestions[]
- What makes it weak and what to do about it.
Errors
When something goes wrong
Every failure carries a stable machine-readable code and the same meta.request_id a success carries — quote it and we can find your request. Errors are never billed.
401 Unauthorized
JSON
{
"error": {
"code": "UNAUTHORIZED",
"message": "The API key is invalid, expired, or revoked."
},
"meta": {
"request_id": "req_7Q2fK4mZ"
}
}- UNAUTHORIZEDHTTP 401
- Missing, malformed, expired, or revoked API key.
- FORBIDDENHTTP 403
- The key is valid but lacks the scope this product needs.
- VALIDATION_ERRORHTTP 422
- A query parameter is the wrong type or out of range.
- RATE_LIMITEDHTTP 429
- Rate limit exhausted. `Retry-After` says how long to wait.
- SERVICE_UNAVAILABLEHTTP 503
- No data recent enough to serve. Carries `Retry-After`, and is never billed.
Health
Is it up?
- Password Strength
1/1 passing