Skip to content
Testaroo
csr1 KB

Certificate Signing Request (CSR)

A PKCS#10 certificate signing request (PEM) with the subject and SAN, self-signed by the RSA key to prove key possession, for testing CSR parsers and certificate-authority intake flows.

Preview, first 19 linescsr
-----BEGIN CERTIFICATE REQUEST-----
MIICzTCCAbUCAQAwSDELMAkGA1UEBhMCVVMxIDAeBgNVBAoMF05vdnVzIEV4YW1w
bGVzIChTYW1wbGUpMRcwFQYDVQQDDA5zYW1wbGUuZXhhbXBsZTCCASIwDQYJKoZI
hvcNAQEBBQADggEPADCCAQoCggEBANVhf/2r1qPct994DqqBGlBOFH3RGmuKCd8P
obnxB2V8JuzVzMBMlgvhrKhJsYDtipUWqfN2jpImxh+FledR+LHtNDi07fcLWXun
CQqn3Jb/4KUh/3Q8bpVkpGRbIPaKclKihHu5PxNSWxDwn+aGJ/vtENhUtk7dKQiA
56i+/2V6jnoOx1k2Mb2cniMPjJKxpsp6VjzeWIAFv8GTlogV1EV2hWxO/MLdFgrt
IWPkrLKXw8MmcMb77x0B0nXJZnlNHD/d7c7I83NMxl+WbrAEbmQLRwTcoBrCa4cW
xBx19FWwvmzEEyBdLQcdonAM4C1EBR8PWhR7CI3Ka8f3G36jZ9UCAwEAAaBAMD4G
CSqGSIb3DQEJDjExMC8wLQYDVR0RBCYwJIIOc2FtcGxlLmV4YW1wbGWCEnd3dy5z
YW1wbGUuZXhhbXBsZTANBgkqhkiG9w0BAQsFAAOCAQEAXtdxDzGU+JMDsP+jm7/d
E034wish9nKmhNVyOmMduCp5xZwX+3chjwfdWDTRW1hi4i+G3VoyBmbf1RW9IlKl
tpWX4sRDNi1VkpyKZsy9jiVRHjp0RJEIEDE9cYMEpC07ESYqZyvzKgr9SXyQUxHW
utpaPGQT49g/yM5KxVpw3E1UFmMwIHlSPY/JUdT32Zmk1xh15zQ+eE4folV74NAt
QsQlC2HKZrABVjrylKvahNJZqm2MpO07t1PO53Wco4tZU1ogMCBqKYHEQztrFRKu
b7Q+TJmfgyRwFjOUByqbMPcAfdpWkgxqpM5G3BGT07Kh3vYjIsIp3SjQGP8IqN2u
6w==
-----END CERTIFICATE REQUEST-----

Specifications

Format
PKCS#10 (PEM)
Subject
CN=sample.example
Key
RSA 2048
Signature
sha256WithRSA
Sample Only
true

Testing contract

Expected to pass
Scenario
Exercise Certificate Signing Request (CSR) in its security workflow. A PKCS#10 certificate signing request (PEM) with the subject and SAN, self-signed by the RSA key to prove key possession, for testing CSR parsers and certificate-authority intake flows.
Expected result
18 text lines, decoded as UTF-8; first nonempty line is '-----BEGIN CERTIFICATE REQUEST-----'. Declared feature checks: subject=CN=sample.example; key=RSA 2048; signature=sha256WithRSA.

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

“Certificate Signing Request (CSR)” is a deterministic Testaroo fixture for Certificate & key testing, Editor 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: 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.

Data fixtures document their exact quirks (delimiters, encodings, null handling, schema, and row counts) in the spec table. Point your parser or importer at the file and assert it handles the documented edge cases; clean and deliberately-messy siblings make before/after diffs straightforward.

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.

Generated by generation/pki_security.py. Free for any use, no attribution required, license.