b2KIT

Cryptographic Key Inspector

Paste any cryptographic key (RSA, EC, Ed25519) to inspect key type, size, curve, and public key components.

Tested tool guide Tested browser tools Checked August 16, 2026

What Cryptographic Key Inspector does and how it behaves

Cryptographic Key Inspector answers a structural question: what key is contained in the text you pasted? Once it recognizes the encoding, it reads the algorithm-specific fields and presents the key family, bit size, named curve where applicable, and public components. RSA, general elliptic-curve keys, and Ed25519 do not expose the same fields, so inapplicable values are not missing data. The common surprise is that a successfully parsed key is not thereby trusted, matched to a certificate, or judged secure for a particular policy.

How the result is produced

1

Algorithm-specific fields

The inspector recognizes the pasted key representation and decodes its algorithm identifiers and parameters. It then classifies the key as RSA, EC, or Ed25519 and reports properties relevant to that family. RSA public components are a modulus and exponent; an EC key identifies a curve and public point; Ed25519 carries an Ed25519 public value.

2

Meaning of key size

Key size is interpreted in the algorithm's own terms, not as a universal strength score. For RSA it refers to the modulus length. For a named-curve EC key, the curve determines the relevant field size. Ed25519 uses a fixed parameter set, so it does not offer a choice of named curves in the way general EC keys do.

Good uses

  • Confirm whether a received key is RSA, EC, or Ed25519 before choosing compatible signing or verification settings.
  • Identify the named curve of an EC key when its filename or surrounding message does not specify one.
  • Record an RSA modulus and exponent or an EC public point for comparison with another copy of the key.

Limits and checks

  • Successful parsing does not prove ownership, establish trust, validate a certificate chain, or check revocation.
  • Bit counts from RSA, EC, and Ed25519 are not directly comparable measures of security strength.
  • A parse failure can result from the pasted encoding, wrapper, or damaged text rather than the underlying key algorithm.

Common questions

Can I paste a private key safely?

The inspector runs entirely in your browser, so the pasted key is not uploaded by this tool. That does not make copying a private key risk-free: clipboard history, screen sharing, browser extensions, or a compromised device can still expose it. Prefer a public key whenever its fields are sufficient for your check.

Does a recognized key mean the key is valid and secure?

No. Successful parsing only shows that the text contains a key structure the inspector recognizes and can decode. It does not establish who created the key, whether the expected party controls its private counterpart, whether a certificate trusts it, whether it has been revoked, or whether its size and parameters meet your policy.

References and verification

The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools