Try it.
Then it clicks.

Binary uses powers of two instead of powers of ten. Here the smallest value is 0 and the largest is 255, giving 256 possible values. IPv4 addresses use four octets, each eight bits long. This experiment is a number representation, not encryption.

The three-link path totals 24 ms, the two-link path 34 ms, and the direct link 80 ms. If C–E is offline, the lower path cannot deliver. A route must be usable before its delay matters. Real routers use configured metrics and policies; they do not simply use the model shown here.

Least privilege means granting only the access needed for an assigned task. Blocking everything can prevent useful work; allowing everything exposes information and capabilities unnecessarily. This is a simplified policy exercise, not a security assessment.

Try connecting all twelve nodes using only eleven links. That is enough to make a connected tree. Extra links can create alternate paths; this exercise counts connectivity and does not simulate routing protocols, failures or security controls.

ASCII characters fit in one UTF-8 byte. Other Unicode code points can take two, three or four bytes. Some visible symbols combine multiple code points, so the number of code points is not always the number of symbols you see. The values below each character are hexadecimal bytes.

In #RRGGBB, each pair represents one color channel in base 16. Hexadecimal uses 0–9 and A–F. FF means 255; 00 means zero. This changes a screen color, not the brightness of your physical display.

This uses decimal MB and Mbps and assumes full, steady use of the stated rate. Protocol overhead, congestion, server limits and wireless conditions can make actual performance slower. The animation always lasts three seconds; the calculated time is shown above.

For the ordinary /24 through /30 subnets here, the first address identifies the network and the last is the broadcast address. The other addresses are potential host addresses. Special /31 and /32 rules are outside this exercise. 192.0.2.0/24 is reserved for documentation.

A DNS resolver may reuse a cached answer until its time to live, or TTL, expires. This small model uses one resolver and a 60-second TTL. Real DNS has multiple layers of caching and more involved resolution and failure behavior. No DNS requests leave this exercise.

The usual order is client SYN, server SYN-ACK, then client ACK. It synchronizes the connection before data exchange. TCP alone does not encrypt the data. TLS can add encryption and authentication above the transport connection.

In this simplified ordered rule set, the first matching rule decides the result. A broad block above a narrower allow prevents that allow from being reached. The default is block when nothing matches. Real products also differ in connection state, direction, object matching and evaluation behavior.

This counts different factor categories: knowledge, possession and inherence. Two of the same category do not create two distinct factors. Some real authenticators combine factors, and not all multi-factor methods resist phishing equally. A biometric is normally combined with an authenticator rather than used as a standalone remote secret.

Urgency, a mismatched domain, a misleading destination and requests for secrets are reasons to stop and verify. A familiar logo or polished writing is not proof that a message is legitimate. Use a known bookmark or an independently verified contact, not the message’s link. All addresses in this exercise are examples.

A hash produces a fixed-size digest. It is not something you decrypt to recover the original message. Different inputs usually produce very different digests, but finite-size hashes can have collisions. A trusted comparison digest can help detect changes; a plain hash alone does not prove who created a file. These SHA-256 calculations run locally in your browser.

A usable noon backup restores the state from noon, leaving two hours of later changes to recover elsewhere or recreate. This is the recovery point, not the time needed to finish a restore. Real recovery also depends on backup integrity, access, isolation and testing. Syncing alone does not guarantee a protected backup.

Confidentiality asks who can see information. Integrity asks whether it remains accurate and protected from unauthorized changes. Availability asks whether authorized people can access it when needed. One incident can affect more than one property; these scenarios focus on the most direct effect.