csr1.1 KB

SAMPLE CSR — Wildcard

A wildcard certificate request covering *.csr.pki.sample.example plus the apex. CA policy engines usually treat wildcards specially, so this is the input that exercises that branch.

Certificate & key testing

Preview — first 19 linescsr

Specifications

Format: PKCS#10 (PEM)
Key: RSA-2048
Cn: *.csr.pki.sample.example
San: *.csr.pki.sample.example, csr.pki.sample.example
Sample Only: true
Seed: 70117

Testing contract

Expected to pass

Scenario: Run the CSR through the issuance policy check under test.
Expected result: The wildcard name is recognised as a wildcard request and routed to the policy branch rather than treated as a literal hostname.

What is a .csr file?

A CSR (Certificate Signing Request, PKCS#10) is a PEM-encoded request a party sends to a certificate authority to be issued a certificate. It contains the subject distinguished name and public key, self-signed with the matching private key to prove possession, but has no validity dates or issuer.

How to use this file

Use an example .csr to test CSR parsers, certificate-authority intake flows, and PKCS#10 decoders, or to verify subject and public-key extraction. Sample request only.

How to use this file for testing

“SAMPLE CSR — Wildcard” is a deterministic Novus Examples fixture for Certificate & key 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 · PKCS#10 (PEM). 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.