What is the difference between self-signed and Let's Encrypt SSL?

Both create an encrypted HTTPS connection, but only one is trusted by browsers, which makes all the difference for a public website.

Self-signed certificate. You generate it yourself, and you are the only one vouching for it. Because no recognised authority has verified it, browsers show a big security warning ("your connection is not private") and visitors must click through it. This is fine for a private test server, but unacceptable for a live business site.

Let's Encrypt certificate. Issued by a trusted, browser-recognised certificate authority after verifying you control the domain. It produces a clean padlock with no warnings, and it is exactly what Dirham A Day issues free on every site, with automatic renewal.

Quick comparison:

• Trust: Let's Encrypt is trusted everywhere; self-signed triggers warnings.
• Cost: both are free.
• Use case: Let's Encrypt for any public site; self-signed only for internal testing.

You never need to create a self-signed certificate on our hosting, because the trusted free option is automatic. If you have inherited a self-signed certificate causing warnings after a migration, just run AutoSSL to replace it, or contact WhatsApp +971 58 553 6767 or support@dirhamaday.ae.