Extension NavigatorFILE EXTENSION LIBRARY
日本語
Home›Certificates & Keys›.cer
THE FILE FIELD GUIDE
.cer

Certificate File

Certificates & Keys

CER commonly names a certificate but may use PEM or DER. Inspect subject names, issuer, validity and usage. Viewing need not require importing; inspect before changing trust settings.

What it is used for
Distribution and inspection of public certificates
What the file contains
Producer-dependent
All sections, questions and sources

Content reviewed： · Editor：Kai

Opening steps

Choose your environment or purpose to see its steps.

Inspect encoding and details

CER does not prove DER encoding.

  1. Inspect provider and intended use.
  2. Distinguish encoding through labels or supported inspection.
  3. Inspect issuer, names and dates without importing trust.
Identify intended certificate role

Usage is separate from the suffix.

  1. Check the consumer’s required format.
  2. Inspect names, usage and chain.
  3. Locate authorized matching key material when required.
Compare before trust configuration

Verify provenance and fingerprint.

  1. Obtain the expected fingerprint from a trusted source.
  2. Compare SHA-256 fingerprints.
  3. Identify the required store through administrator guidance.

Menu labels and support vary by app, OS and version. Preserve the original before making changes.

Troubleshooting by symptom

  • DER parsing fails: check for PEM text labels.
  • Name mismatch: compare covered names and intended usage.
  • Still untrusted after import: inspect issuer/chain requirements through legitimate documentation.
  • Digest mismatch: distinguish certificate fingerprint from file hash.
  • Multiple candidates: compare identity, usage and issuer.
  • No authentication key: inspect separate private-key storage.

CER → required PEM / DER encoding

  1. Establish encoding and export the certificate appropriately.
  2. Compare identity, validity and public key.
  3. Reinspect output names and fingerprint.

Renaming does not change encoding/trust; a certificate without its key cannot create a key-containing P12.

Suffix versus internal encoding

Inspect encoding/object type rather than relying on the suffix.

Example: encoding changes file hashes; compare certificate fingerprints using the same algorithm.

Source for these steps：OpenSSL Project · openssl-x509 / IETF / RFC Editor · RFC 7468 — Textual Encodings

Public certificate versus private credentials

Distinguish certificate delivery from private-key transfer and identify what authentication requires.

Source for these steps：OpenSSL Project · openssl-x509 / IETF / RFC Editor · RFC 7468 — Textual Encodings

Related-format differences

Related-format differences
Format / methodRoleWhat to verify
CER / CRTCertificate suffixesContents/encoding
DER / PEMEncodingIdentity after conversion
PFXCertificate/key containerKey/protection

Handling and security

Do not add unknown certificates to trusted stores merely for inspection; verify issuer trust separately.

Questions and answers

Is CER always DER?

It may be PEM.

Will renaming to CRT work?

Check required content/encoding.

Does viewing change trust?

Viewing and importing are separate operations.

Are matching CER/CRT fingerprints the same certificate?

Compare certificate fingerprints with the same algorithm; encoding/name can differ.

Is a file hash the same as a certificate fingerprint?

File hashes depend on encoding/newlines; certificate fingerprints compare its DER representation.

Format facts: name, steward and MIME type
Formal name
X.509 certificate (common CER use)
Steward / specification
Issuing certificate authority / IETF standards
MIME type
Depends on the producer or server; an extension alone does not establish a MIME type.

Primary and official sources

  • Project documentationopenssl-x509

    Reference for certificate inspection and PEM/DER conversion.

    OpenSSL Project · Link checked：
  • StandardRFC 7468 — Textual Encodings

    Defines textual encodings for certificates, keys and requests.

    IETF / RFC Editor · Link checked：