Talk about a "certificate" with an entrepreneur or accountant in Uzbekistan and they will probably think of their ERI key, the electronic digital signature used for tax reports and government services. A web developer hears the same word and thinks of the padlock in the address bar, the SSL certificate. Both rely on public-key cryptography, and both involve a certificate plus public and private keys, so they're easily confused. Some customers even ask whether they can put their ERI key on their website. Here is the difference in plain terms.
What ERI is and what it proves
An electronic digital signature (ERI) proves that a document was signed by a specific person or organisation and hasn't changed since. In Uzbekistan, ERI keys are issued by registration centres operating under national law and are tied to an individual or to an organisation's head or employee, carrying identifiers such as full name, personal ID number (PINFL) or the company's tax number (STIR). Under the law, an ERI-signed electronic document is recognised as equivalent to a hand-signed paper one; check the current legal text for the exact conditions. ERI is used for tax filings, e-invoices and contracts, government portals and banking. The key usually sits as a password-protected file on a computer, a USB stick or a token, and browser signing works through a local application, the E-IMZO module.
What an SSL certificate is and what it proves
An SSL (more precisely TLS) certificate proves a domain name, not a person. It assures the browser that you really reached example.uz and that the connection is encrypted. These certificates come from international CAs trusted by browsers and operating systems, which follow shared industry rules and are audited regularly. The common DV (Domain Validation) type, like free Let's Encrypt certificates, contains only the domain. OV and EV types also verify the organisation, but their job is still securing connections, not signing documents.
Key differences
| Criterion | ERI key | SSL certificate |
|---|---|---|
| Proves | A person or organisation | A domain name |
| Issued by | Registration centres in Uzbekistan | International browser-trusted CAs |
| Used for | Signing documents, taxes, e-government | Websites, APIs, mail servers |
| Trusted by | The state and connected systems | Browsers and devices worldwide |
| Stored on | Owner's PC, USB stick or token | The web server |
Why an ERI key can't go on a website
First, purpose: an SSL certificate must contain the domain name that the browser compares with the address bar, while an ERI key names a person. Second, the chain of trust: browsers accept only certificates from CAs in their root stores, and ERI runs in its own separate trust infrastructure. Third, ERI systems may use national cryptographic standards, while TLS expects international algorithms such as RSA and ECDSA. Finally, it would be a security blunder: your ERI private key is your legal signature, and putting it on an internet-facing server is like handing it to strangers.
Example: a garment workshop in Namangan
A small sewing company in Namangan launched misol.uz, and the accountant suggested using the company's ERI as the site's certificate. Their developer explained that the ERI key signs invoices and contracts on the company's behalf and must stay on the accountant's computer, while the site needs a separate domain SSL certificate issued and renewed automatically by the host. Now the company has both: the ERI key is renewed at a registration centre before it expires, and on sayt.uz hosting the SSL certificate renews itself through free 90-day Let's Encrypt certificates.
When a website needs to work with ERI
Some business portals let users log in or sign contracts with ERI. Even then the site itself is protected by an ordinary SSL certificate, and ERI signing happens separately through software on the user's computer. Signature verification should use the official integration tools and documentation; confirm the requirements with the ERI system's official sources. In short, ERI answers "who signed this?", while SSL answers "which site am I connected to, and is the connection safe?" Both matter, and neither replaces the other.