TASK

Install a TLS certificate on your server

After receiving a signed certificate from a CA, install it with the correct chain order and verify the deployment with a TLS handshake.

1

A complete TLS deployment requires: the server certificate, the private key, and the intermediate certificate chain. The chain must be in order: server cert first, then intermediates up to the root. A missing or out-of-order chain causes "untrusted certificate" errors in browsers.
2

RSA Tool →
Verify your private key matches the certificate by comparing the public key modulus. If they do not match, the certificate was generated with a different key and will not work.
3

Hash Calculator →
Compute the SHA-256 fingerprint of the certificate to verify it matches what the CA issued. This detects corruption or tampering during download.
4

After installation, test with a TLS client (e.g., openssl s_client, curl, browser). Verify: the chain is complete, the certificate is not expired, the hostname matches a SAN, and OCSP stapling works. Monitor expiration and set renewal reminders.

Frequently asked questions

Why do browsers show "untrusted" even with a valid certificate?: The most common cause is a missing intermediate certificate. The server must send the full chain (server + intermediates). The root is not sent — it must already be in the browser's trust store.
How do I automate renewal?: Use ACME (Let's Encrypt) with a client like certbot or acme.sh. Set up a cron job to renew 30 days before expiration. For paid certificates, use the CA's API or set calendar reminders.

Workflows that solve this

Hash content and encode as Base64

Compute a hash of the input and encode the hash digest as Base64 for compact transport.

Hash text and verify integrity

Compute a hash of the input text and compare it against an expected hash to verify integrity.

Hash text and verify with CRC32 checksum

Compute both a cryptographic SHA-256 hash and a CRC32 checksum for data integrity verification.

MD5 Hash then Base58 Encode

Compute MD5 hash then encode as Base58 for compact representation.

Multi-hash speed comparison

Hash the input and benchmark multiple hash algorithms to compare their speed and output.

Generate Password and Hash

Generate a random password then hash it for secure storage.

SHA3-256 Hash with CRC32 Checksum

Compute SHA3-256 hash then CRC32 checksum for dual integrity verification.

SHA-512 Hash then Hex Encode

Compute SHA-512 hash then encode as hex for readability.

Reverse Text and Hash

Reverse text then compute SHA-256 hash of the reversed result.

Scramble Text and Hash

Scramble text then hash the scrambled result.

Learn more

Want to understand why?

Comparing Symmetric vs Asymmetric Encryption

Understand the strengths, weaknesses, and use cases of symmetric and asymmetric cryptography.

How to Encrypt Large Data

Encrypt files or data larger than the RSA key size using hybrid (envelope) encryption.

Accountable Encryption

Accountable encryption ensures that key leaks can be traced to a specific responsible party by embedding user-specific ciphertext marks with watermarking or fingerprinting techniques.

Acoustic Attack

An acoustic attack exploits the correlation between key material and sounds emitted during cryptographic operations (coil whine, capacitor vibration) to recover keys via a side channel.

Related tools

RSA key generation, encryption, decryption, signing, and verification using Web Crypto API. Free, private, and 100% client-side.

Hash Calculator

Compute MD5, SHA-1, SHA-256, or SHA-512 hashes with hex or Base64 output. Free, private, and 100% client-side.

Generate HMAC (Keyed-Hash Message Authentication Code) with SHA-1/256/512. Free, private, and 100% client-side.