FIPS 140 certificate tracker
Every NIST FIPS 140 certificate, plus the modules-in-process queue NIST publishes only as a page.
| Endpoint | https://fips.808bits.com/mcp (streamable-http) |
|---|---|
| Registry version | 0.1.0 |
| Now | 6 tools · grade C (73) · pin ts_a737ae0bef2d6c2a1776e7ceca66a892 · protocol 2025-06-18 |
| First / last listed | 2026-10-24 21:33 UTC / 2026-10-24 21:33 UTC |
| Grade over time | 2026-10-24: C (73), 6 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: fips_cert fips_search fips_in_process fips_vendor fips_cve fips_sunset
fips_cert | Look up one FIPS 140 cryptographic module validation by certificate number. Returns status (active, historical or revoked), overall level, sunset date, validation history, approved algorithms and tested configurations. params: number* |
fips_search | Search FIPS 140 validations by module name or vendor. Use this to answer whether a given product or vendor holds a current validation, and at what level. Results are ordered by status, then how well they match, then newest first, so the current validations lead. params: query*, status, standard, level, limit |
fips_in_process | Search NIST's Modules in Process queue: submissions awaiting FIPS 140-3 validation, with the review phase each one is sitting in. Use this when a vendor claims a validation is 'coming' and you need to know whether it has actually been submitted, and how far along it is. params: query, phase, limit |
fips_vendor | Everything one company holds, grouped across the spelling variants NIST filed it under. Cisco alone appears as three different strings. Returns a breakdown by status and standard plus the certificates themselves. Note this groups spellings of one registration, not corporate families: the nShield line sits under nCipher, Thales and Entrust separately, because the product changed owner. Groups large params: vendor*, limit |
fips_cve | Which FIPS-validated modules are associated with a given CVE, or which CVEs are associated with a vendor's modules. Answers 'we have a validated module, is it caught up in this advisory'. The association is name-based against the product CPE, so read it as a pointer to check rather than a finding. An empty result means nothing matched by name, not that the module is unaffected: only 4 of the 712 a params: cve, vendor, min_cvss, limit |
fips_sunset | List active FIPS validations by sunset date, the day each moves to NIST's historical list and stops being valid for new procurement. Answers 'what expires before date X' and 'which vendors are about to have nothing valid'. A certificate listed here may already have a 140-3 successor: check fips_search for the same module name before reporting a gap. params: before, standard, vendor, limit |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.