🛰️

PingForge

The internet isn’t a cloud. It’s real machines you can count the hops to — follow your data across them.

Follow a request across the internet

When you open a page, your data doesn’t float in a "cloud" — it travels a real path between real computers, one hop at a time. First DNS turns the site’s name into a number (its address). Then a packet hops from router to router toward that address, carrying a TTL hop-budget so it can’t get lost forever. A quick handshake says hello before any real data flows. A cache nearby might hold a copy so you skip the long trip, and a firewall checks each packet’s port and lets it through — or doesn’t. PingForge lets you predict each step, then trace the whole route yourself.

Name → number. DNS looks up the site’s real address before anything is sent.
Hop by hop. Routers hand your packet along a chain of real machines.
Hop budget. TTL counts down each hop, so a lost packet stops instead of circling forever.
Shortcuts & gates. A cache saves a trip; a firewall allows or blocks by port.

Everything runs on your device with exact arithmetic — no library, no network.

Meet the pieces of the internet

Packet — the little bundle carrying your data toward an address.
Router — a crossroads that reads each packet’s address and forwards it one hop closer.
DNS — the phone book that turns a site’s name into its numeric address.
TTL — the packet’s hop budget; it drops by 1 each hop, so a lost packet can’t wander forever.
Handshake — the quick hello (SYN · SYN-ACK · ACK) before any real data is sent.
Cache — a nearby copy that saves the long trip to the far server.
Firewall — the gatekeeper that allows or blocks each packet by its port.

Illustrated portraits for the cast are on the way — for now the pieces are described in words.