Learn Dark Web

Learning Path

Encryption Fundamentals Path

Encryption is the technology behind almost everything secure on the internet — your passwords, your messages, your banking — and it is widely misunderstood. This path explains it properly: what encryption is, how it differs from hashing and from encoding, why the old ciphers are only toys now, and why an encrypted message can still leak information about you. Everything is hands-on: you will scramble, hash and encode text yourself in the encryption lab.

By Abdul Hannan · Published 14 November 2026 · Updated 14 November 2026

How this path works. Each lesson below is a short summary written for this path, with a link to the full guide. Work through them in order, mark each one complete when you have read the guide, and test yourself with the quiz at the end. Your progress is stored only in your own browser — no account, nothing sent to us. This path teaches understanding, not credentials: completing it does not give you a certificate and does not qualify you for a job.

What you will learn

This path is for readers who are comfortable with the basics from the earlier paths and want to understand the technology underneath them. It is still written in plain English, but it moves faster and expects you to be comfortable with terms like password, key and hash.

  • Explain encryption, hashing and encoding, and tell them apart on sight.
  • Describe symmetric and asymmetric encryption, and say when each one is used.
  • Explain what end-to-end encryption means — and what it does not protect.
  • Understand password entropy and why length beats complexity.
  • Break a Caesar cipher by trying all 25 shifts, and say why that proves it is not security.
  • Explain metadata, and why encrypted does not mean private.

Your progress

0 of 5 lessons complete.

The lessons

Read each lesson summary, then open the full guide it links to. The summaries are written for this path — they do not repeat the guides, they prepare you for them.

Lesson 1: Encryption fundamentals

Encryption is the process of scrambling data with a key so that only someone with the key can read it — and it is reversible by design: the same key, or a matching one, unscrambles it. This lesson explains the two kinds. Symmetric encryption uses one shared key for both scrambling and unscrambling, like a single key shared between two people. Asymmetric encryption uses a pair — a public key anyone can use to scramble, and a private key only the recipient holds to unscramble.

You will learn why both kinds are needed: symmetric encryption is fast but has the problem of sharing the key safely, while asymmetric encryption solves the sharing problem but is slower. In practice the two are combined — asymmetric encryption exchanges a fresh symmetric key, and the symmetric key does the bulk of the work. The lesson uses the encryption lab so you can scramble a message yourself and see that without the key, the result is unreadable — and with the key, it is not.

Read the full guide: What is encryption?

Lesson 2: Encryption vs hashing

Encryption and hashing are constantly confused, and this lesson separates them for good. Encryption is reversible: with the right key you get the original back. Hashing is one-way: it turns data into a fixed-length fingerprint that cannot be reversed, and changing a single letter of the input changes the whole fingerprint — the avalanche effect. Encryption protects secrecy; hashing protects integrity and stores passwords safely.

You will try both in the hashing explorer: hash the same text with different algorithms and watch one letter change the entire result, then compare the fingerprint with the original to see that the hash contains no trace of it. The lesson also explains why passwords are hashed, not encrypted: a site that encrypted your password would need a key to read it back, and anyone who stole the key would have every password. A hash cannot be reversed at all, which is exactly what password storage needs.

Read the full guide: Encryption vs hashing

Lesson 3: What is end-to-end encryption?

End-to-end encryption means only the sender and the recipient hold the keys, so nobody in the middle — not the messaging company, not the network, not an attacker who intercepts the traffic — can read the message. This lesson explains how that differs from ordinary encryption, where the service itself can read your messages, and why it became the standard for private messaging.

But the lesson also teaches the honest limit in its title: encrypted does not mean private. The message content is hidden, but the metadata is not — who messaged whom, when, how often, and from where can still be visible. A messaging service can know your whole social graph without reading a single word. You will learn to ask two questions about any encrypted service: who holds the keys, and what metadata is still collected? The answers to those two questions tell you what the encryption actually protects.

Read the full guide: What is end-to-end encryption?

Lesson 4: What is password entropy?

Entropy is the number that says how hard a password is to guess, counted in bits — and this lesson is where the concept earns its place in the encryption path, because entropy is what connects passwords to the cryptography underneath them. Each extra bit doubles the guessing work, so a 60-bit password is roughly a billion times harder to crack than a 30-bit one. The lesson explains the counting without mathematics beyond doubling, and shows why length creates entropy far faster than complexity.

It also reconciles the disagreement in the advice: the 50, 60 and 80-bit targets all come from different assumptions about who is guessing, how fast, and for how long. A password that must survive a month against a slow online attack needs far less entropy than a master password that must survive years against an offline attack with stolen hashes. The practical translation is the same as in the password path: a long passphrase of random words reaches the high targets, and a short complex password does not.

Read the full guide: What is password entropy?

Lesson 5: Metadata and privacy

Metadata is data about data: who sent a message, when, from where, how big it was, and how often — everything except the content itself. This lesson explains why metadata is often more revealing than content, with a simple example: a list of who you called and when can reveal a relationship, a medical condition or a business deal, even if nobody heard a single word of the conversations.

You will learn why encryption alone cannot fix this. Encryption hides content but not metadata, because the network needs to know where to deliver a message — the envelope must be readable even when the letter is sealed. The lesson shows which metadata each situation leaks, from messaging apps to web browsing, and what actually reduces it: fewer accounts, less sharing, and tools that are designed for metadata protection rather than just content encryption. It is the lesson that makes the phrase encrypted does not mean private concrete.

Read the full guide: Metadata and privacy

Try the tools

These free tools let you practise what the lessons describe — everything runs in your browser, and nothing you type is sent anywhere.

Check what you learned

Four questions, all based on fictional scenarios. Answer them all, then check your score — each answer explains itself, so a wrong answer teaches as much as a right one.

Answer all four questions, then check your score.

Download your notes

Download a plain-text summary of this path: the lesson list, which lessons you marked complete, and your quiz score. The file is generated on your device — nothing is uploaded.

Key terms in this path

The glossary defines every term this path uses: encryption, end-to-end encryption, password entropy, two-factor authentication. If a lesson uses a word you do not know, look it up there — each term page also explains the idea with an example.

Frequently asked questions

Is encryption the same as hashing?

No. Encryption scrambles data so it can be unscrambled later with the right key — it is reversible. Hashing turns data into a fixed-length fingerprint that cannot be reversed. Encoding, like Base64, is neither: it just changes how data is written down.

If my messages are end-to-end encrypted, am I private?

Your message content is private from everyone except the recipient — but the metadata (who you messaged, when, how often) can still be visible to the service. Encrypted does not mean private, and this path teaches you to ask who holds the keys and what metadata is collected.

Why do you call the Caesar cipher a toy?

Because it has only 25 possible keys, so anyone can break it by trying them all in seconds. It is a wonderful teaching tool — it shows what a key is and what scrambling means — but it must never be used for real messages. The lab labels it clearly as learning only.

What is the difference between symmetric and asymmetric encryption?

Symmetric encryption uses one shared key for both scrambling and unscrambling — fast, but the key must be shared safely. Asymmetric encryption uses a key pair: a public key anyone can use to scramble, and a private key only the recipient holds. In practice they are combined: asymmetric encryption exchanges a fresh symmetric key, which does the bulk of the work.

Is Base64 encryption?

No. Base64 is encoding: it changes how data is written down so it can travel safely in places that only accept plain text. Anyone can decode it instantly, and it protects nothing. Confusing encoding with encryption is one of the most common mistakes in this subject, and the lab shows you the difference hands-on.