Skip to content
Novus Examples
der903 B

X.509 Certificate (DER)

The binary DER encoding of the same certificate — for testing ASN.1/DER parsers, Java keystores, and DER-to-PEM converters. Published sample certificate, not a real identity.

Preview — schema + first 9 rowsder
FieldValue
TypeX.509 certificate (DER, binary)
SubjectCN=sample.example, O=Novus Examples (Sample), C=US
Issuer(self-signed) CN=sample.example
Serial5642823782587783233
Valid from2026-01-01
Valid to2036-01-01
Public keyRSA 2048-bit
Signaturesha256WithRSAEncryption
SANsample.example, www.sample.example
Published sample certificate — self-signed, not a real identity.

Specifications

Format
X.509 v3 (DER, binary)
Subject
CN=sample.example
Key
RSA 2048
Note
binary encoding of the PEM twin
Sample Only
true

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

“X.509 Certificate (DER)” is a deterministic Novus Examples 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: X.509 v3 (DER, binary). 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.