About ECDSA Verify
Verify a message against a signature and a public PEM encoded EC key.
Input: text. Output: text.
Format reference: ECDSA Verify background and specification
Example
Use “Try example” to load this public sample and its settings, then run it.
Settings used in this example
| Parameter | Example value | Input and choices |
|---|---|---|
| Input Format | Auto | Auto, ASN.1 HEX, P1363 HEX, JSON Web Signature, Raw JSON |
| Message Digest Algorithm | SHA-256 | SHA-256, SHA-384, SHA-512, SHA-1, MD5 |
| ECDSA Public Key (PEM) | "-----BEGIN PUBLIC KEY-----\nMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEDUc8A0EDNKoCYIPWMHz1yUzqE5mJ\ngusgcAE8H6810fkJ8ZmTNiCCa6sLgR2vD1VNh2diirWgKPH4PVMKav5e6Q==\n-----END PUBLIC KEY-----" | Text |
| Message | "A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools." | Text |
| Message format | Raw | Raw, Hex, Base64 |
Sample keys and passwords are public. Never use them to protect real data.
Input
3046022100e06905608a2fa7dbda9e284c2a7959dfb68fb527a5f003b2d7975ff135145127022100b6baa253793334f8b93ea1dd622bc600124d8090babd807efe3f77b8b324388d
Result
Verified OK
Parameters
| Parameter | Default value | Input and choices |
|---|---|---|
| Input Format | Auto | Auto, ASN.1 HEX, P1363 HEX, JSON Web Signature, Raw JSON |
| Message Digest Algorithm | SHA-256 | SHA-256, SHA-384, SHA-512, SHA-1, MD5 |
| ECDSA Public Key (PEM) | "-----BEGIN PUBLIC KEY-----" | Text |
| Message | "" | Text |
| Message format | Raw | Raw, Hex, Base64 |
Before interpreting the result
Parsing a certificate shows its fields; it does not establish trust in the issuer or validate a certificate chain. Signing and verification require the algorithm and key format expected by the other party.
How to use this page
- Paste your input or open a local file.
- Adjust tool options if needed, then choose Run tool.
- Copy the result or download the original output bytes.
Inputs and results are not added to the public catalogue or saved in the URL. Processing happens in your browser; HTTP Request and DNS over HTTPS send the requests you explicitly run. Files up to 128 MiB can be opened; decompression and image tools may have smaller processing limits. Large results have a shortened preview. Text and HTML downloads use UTF-8; binary downloads preserve output bytes. Pasted text follows browser newline handling; open a file when exact input bytes matter.