Skip to content
Novus Examples

Explore the test library

Find files, editable templates and browser test targets by what you need to make or test. Explore complete business kits for connected records, templates and expected results.

135 results

Page 2 of 6; 24 results per page.

Show the canonical directory
Preview of SAMPLE CA Bundle — Root + Intermediate
pem
3.7 KB
Actual file preview for SAMPLE CA Bundle — Root + Intermediate

SAMPLE CA Bundle — Root + Intermediate

The two CA certificates concatenated in trust-store order, the shape a `--cafile` or `ca-bundle.crt` argument expects. Point a client at this and every other valid p7 leaf becomes verifiable.

File
PEM · Pki
Use case
Certificate & key testing· Conversion set
Preview of SAMPLE Certificate Revocation List — Empty
pem
869 B
Actual file preview for SAMPLE Certificate Revocation List — Empty

SAMPLE Certificate Revocation List — Empty

A correctly signed CRL with an absent revokedCertificates field — what a CA publishes when it has revoked nothing. Parsers that assume the list is always present tend to fault here rather than report zero entries.

File
PEM · Pki
Use case
Certificate & key testingError handling· Conversion set
Preview of SAMPLE Certificate Revocation List — Stale
pem
971 B
Actual file preview for SAMPLE Certificate Revocation List — Stale

SAMPLE Certificate Revocation List — Stale

A validly signed CRL whose nextUpdate passed in 2020. Whether a client hard-fails, soft-fails, or silently trusts stale revocation data is a real policy decision, and this is the fixture that reveals which one it made.

File
PEM · Pki
Use case
Certificate & key testingError handling· Conversion set
Preview of SAMPLE Certificate Revocation List (PEM)
pem
971 B
Actual file preview for SAMPLE Certificate Revocation List (PEM)

SAMPLE Certificate Revocation List (PEM)

The issuing CA's revocation list, PEM-armoured, naming the revoked SAMPLE leaf (keyCompromise) plus a second serial with no matching certificate file — because a real CRL lists serials, not certificates. Signed by the same intermediate that issued them.

File
PEM · Pki
Use case
Certificate & key testing· Paired fixture
Preview of SAMPLE Chain — Leaf + Intermediate
pem
3.6 KB
Actual file preview for SAMPLE Chain — Leaf + Intermediate

SAMPLE Chain — Leaf + Intermediate

The bundle a TLS server actually presents: leaf first, then the issuing CA, with the root deliberately omitted because clients must already trust it. This is the correct-by-construction reference for the chain-order fixtures beside it.

File
PEM · Pki
Use case
Certificate & key testing· Conversion set
Preview of SAMPLE Chain — Leaf + Intermediate + Root
pem
5.5 KB
Actual file preview for SAMPLE Chain — Leaf + Intermediate + Root

SAMPLE Chain — Leaf + Intermediate + Root

The same chain with the self-signed root appended. Sending the root is legal and common, merely wasteful, so a verifier must ignore the extra anchor rather than treat it as an error.

File
PEM · Pki
Use case
Certificate & key testing· Conversion set
Preview of SAMPLE Chain — Missing Intermediate
pem
3.7 KB
Actual file preview for SAMPLE Chain — Missing Intermediate

SAMPLE Chain — Missing Intermediate

Leaf plus root with the issuing CA left out — the single most common TLS misconfiguration, and the one that works in browsers with a cached intermediate and fails everywhere else. Use it to prove a client does not silently paper over the gap.

File
PEM · Pki
Use case
Certificate & key testing· Conversion set
Preview of SAMPLE Chain — Wrong Order
pem
3.6 KB
Actual file preview for SAMPLE Chain — Wrong Order

SAMPLE Chain — Wrong Order

The leaf and intermediate concatenated backwards. Strict servers reject the file outright while tolerant path builders reorder it silently, so it cleanly separates the two behaviours.

File
PEM · Pki
Use case
Certificate & key testing· Conversion set