SAMPLE OCSP Request (DER)
The DER OCSPRequest a client sends when checking the reference leaf, with the SHA-1 CertID that RFC 6960 mandates and no nonce extension. POST it at a stub responder to exercise request parsing without a live CA.
| Field | Value |
|---|---|
| Type | OCSP request (DER, RFC 6960) |
| Requested serial | 0x701001 |
| Issuer name hash | SHA-1 of the SAMPLE intermediate subject |
| Nonce extension | absent |
| Bytes | 70 |
Specifications
- Format
- RFC 6960 OCSPRequest (DER)
- Cert Id Hash
- SHA-1 (as RFC 6960 requires)
- Serial
- 0x701001
- Issuer
- Novus Examples SAMPLE Issuing CA I2
- Nonce
- false
- Sample Only
- true
- Seed
- 70117
Testing contract
Expected to pass- Scenario
- Parse the request and read back the CertID serial number and hash algorithm.
- Expected result
- The parser reports serial 0x701001, a SHA-1 CertID, and no nonce extension.
What is a .der file?
DER (Distinguished Encoding Rules) is the binary encoding of an X.509 certificate (or other ASN.1 structure) — the same data a PEM file Base64-wraps, without the text armour. A .der certificate is compact and byte-exact, common in Java keystores and Windows tooling.
How to use this file
Use an example .der certificate to test binary X.509 parsers, ASN.1 decoders, and DER-to-PEM converters, or to confirm a tool reads raw certificate bytes. Published sample certificate, not a real identity.
How to use this file for testing
“SAMPLE OCSP Request (DER)” is a deterministic Novus Examples fixture for Certificate & key testing, API testing. Self-signed X.509 certificates (PEM, CRT, DER), a CSR, RSA and Ed25519 keys, an SSH public key, a PKCS#12 bundle, and an htpasswd file — all published sample-only material, for testing certificate parsers, TLS tooling, keystore importers, and PEM/DER decoders.
Documented properties for this file: seed 70117 · RFC 6960 OCSPRequest (DER). Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
This is published, SAMPLE-only security material — never a real secret. Point certificate, key, or token parsers at it, test PEM/DER decoding and PKCS handling, and confirm your tooling reads the documented fields; any sample password is printed on this page.
This is a published, sample-only certificate/key. Parse it, verify the chain or signature, and test PEM↔DER conversion — never deploy it anywhere real.
Related files
- jsonCRL Metadata JSON — SAMPLESAMPLE CRL metadata JSON (no binary CRL) for revocation-list UI and loader tests.
- keyEd25519 Private Key (PEM) — SAMPLEDeterministic SAMPLE Ed25519 private key for SSH/TLS tooling tests.
- keyEncrypted PKCS#8 RSA Key — SAMPLEPassword-encrypted SAMPLE PKCS#8 private key (password printed in specs) for decrypt-import tests.
- csrPKCS#10 CSR — Security SAMPLEPKCS#10 certificate signing request SAMPLE for CSR parsers and CA tooling smoke tests.
- p12PKCS#12 Bundle (.p12) — SAMPLESAMPLE PKCS#12 keystore (password `novus-sample-wg`) for keystore importer tests. Not byte-stable.
- keyRSA-2048 Private Key (PEM) — SAMPLEPublished SAMPLE RSA-2048 private key (PKCS#8 PEM). Never use for a real identity.
Generated by generation/security_p7.py. Free for any use, no attribution required — license.