The Internet was originally developed to simply send data from one machine to another, usually requiring that data to be routed through several intermediary machines on the way. The original (and most basic) functions associated the Internet are web browsing and email. The original networks the Internet was deployed on had their access physically limited; no one unauthorized to see data had access to a computer. This means that standard web browsing pays no mind to privacy and security.

These days we have all sorts of methods to help with the various programs that partake of the network that brings us all together. Most of these applications are associated with a specific protocol, which is written to send or receive data in the best manner for its function.

Protocols each lay claim to a unique numbered port, so the sea of Internet traffic entering a PC doesn’t stop its data from finding the right place to enter. These ports may be fixed or randomly chosen. As the methods used to transport data vary greatly from protocol to protocol, so too does the level of privacy offered.

Web browsing is most commonly done over the HTTP protocol, which works through port 80. This has been shown to be vastly insecure, with information sent clearly, in plain text, to an easily identifiable recipient, from an easily identifiable source. So when you write your plans for the evening on a forum all the information is sent through the old tubes essentially just as written.

It’s not exactly shouting across a filled auditorium but anyone with a little time can patiently listen and pick up some details. Fortunately enough, it’s not all doom and gloom; most websites discreetly handle securing connections with more secure protocols.

HTTPS is HTTP’s secure cousin, commonly used when a user goes shopping or logs into a website with private data. It’s a little smarter, for example its default port is 443, but this can be changed, just to keep would-be hackers guessing.

On top of this, there’s an extra layer of processing performed on each packet of data, enabling both encryption and authentication. Being sure of exactly to whom you’re talking during a transaction is obviously vitally important when purchasing or providing personal details. Generally a web browser will let its user know is browsing a HTTPS secure site with a lock image (on the status bar). This is just in case the user doesn’t notice that the address begins with ‘https’.

FTP, the File Transfer Protocol is frequently used to upload files to websites. It ensures data is transferred absolutely correctly (hence its usage in file transfer). Unfortunately, it’s another relic from a less security-conscious age. It too was designed to help information get from a known point A to a known point B.

Thankfully these days there are more secure options, such as SFTP. SFTP helps make sure data is kept away from prying eyes by using SSH2(secure shell) and the methods of security it provides to keep information secure.

Other protocols aren’t as open about their inner workings. Bittorrent’s algorithm for distributing files is closed, so the specific details aren’t known. What is known is that it connects to many other users who have sections of the file being downloaded and takes what they have to assemble a completed file. While this is fast, it makes no attempt to hide the identity of the user whatsoever.