pem178 B

SAMPLE EC P-256 Public Key — SubjectPublicKeyInfo

The P-256 public key in SubjectPublicKeyInfo form, carrying the named-curve OID and an uncompressed point. It matches the EC leaf certificate and the EC entry in the p7 JWK set.

Certificate & key testing

Preview — first 5 linespem

-----BEGIN PUBLIC KEY-----
MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEW+DRtkDz4KfDgUk8eD0xdb+UrRrl
/ciiSWwJ07uX7In0gT7mZotPjI39dNPC5HYASN64Q0pJPAaoYaqGZCWL4Q==
-----END PUBLIC KEY-----

Specifications

Algorithm: EC
Curve: P-256 (prime256v1)
Format: SubjectPublicKeyInfo
Point Format: uncompressed
Sample Only: true
Seed: 70117

Testing contract

Reference control

Scenario: Parse the key and compare its point coordinates with the x and y values in the p7 EC JWK.
Expected result: The uncompressed point decodes to the same 32-byte x and y values the JWK publishes.

What is a .pem file?

PEM (Privacy-Enhanced Mail) is a text container that Base64-encodes DER binary data between BEGIN/END header lines, used to hold X.509 certificates, certificate requests, and keys. A single .pem file may contain a certificate, a chain, or a private key, which makes it the most common format for TLS material.

How to use this file

Use an example .pem certificate to test X.509 and TLS parsers, PEM decoders, certificate-chain validators, and PEM-to-DER converters. This is published sample material — never a real production key.

How to use this file for testing

“SAMPLE EC P-256 Public Key — SubjectPublicKeyInfo” 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 · EC · SubjectPublicKeyInfo. 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.