# HALOWERK sicherwerk OpenSSL DH Group Check

> HALOWERK sicherwerk OpenSSL DH Group Check is a paid API for AI agents from sicher.halowerk.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-29).

Validates a finite-field Diffie-Hellman group in PEM format using a pinned OpenSSL build, reporting whether the parameters are cryptographically safe (prime modulus, generator order, security level).

## Facts

- Endpoint: POST https://sicher.halowerk.com/v1/oss-openssl-dh-group-check?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-sicherwerk-openssl-dh-group-check-ec29fca7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Srw-yMNf8xLRrG_jrJ9XV

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability halowerk-sicherwerk-openssl-dh-group-check-ec29fca7 -d '<json body>'
```

Example prompt: Can you check whether these Diffie-Hellman parameters are cryptographically safe? Here's the PEM: -----BEGIN DH PARAMETERS-----...-----END DH PARAMETERS----- — I want to know if the modulus is prime, the generator is sound, and it passes OpenSSL's security level before I use it in a handshake.

## When to prefer this

Use this endpoint when you need a deterministic, reproducible cryptographic verdict on finite-field DH group parameters using a pinned OpenSSL version — especially when you want the exact OpenSSL diagnostic text rather than a reimplemented check. Ideal for CI/CD pipelines, pre-deployment audits, or compliance workflows where provenance of the validation tool matters. Prefer over generic crypto libraries when you need OpenSSL-specific security level enforcement and authoritative diagnostic output.

## Known failure modes

- Invalid or malformed PEM input returns an error without a cryptographic result
- Parameters that are syntactically unparseable by OpenSSL yield a parsing error
- Oversized PEM exceeding 262144 bytes is rejected
- Network or payment failure (x402) returns a 402 Payment Required response
- OpenSSL internal error on edge-case parameter shapes may return an opaque failure message

## How this service works

Runs the pinned OpenSSL build's parameter checks over a supplied finite-field Diffie-Hellman group and reports whether it passes, along with the detail output that says why. The point is to catch parameters that are syntactically fine but cryptographically unsafe before they reach a handshake: a non-prime modulus, a generator of small order, a group below the build's security level.

## Output

A pass/fail verdict on the supplied DH group along with the full OpenSSL diagnostic output explaining why — identifying issues such as a non-prime modulus, a generator of small order, or a group that falls below the build's configured security level.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "parameters_pem": {
   "type": "string",
   "maxLength": 262144,
   "minLength": 1
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-sicherwerk-openssl-dh-group-check-ec29fca7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from sicher.halowerk.com](https://www.zero.xyz/host/sicher.halowerk.com/llms.txt)