Key Internet Services for Researchers

The internet is often equated with just websites and social media, but for a researcher, it is a layered infrastructure of distinct services. Each service was built to solve a different problem: how to send a message, how to access a file on a remote machine, how to operate a distant computer, and how to link documents across the world. Understanding these building blocks is not a history lesson. It directly shapes how efficiently a research scholar can gather data, collaborate with peers, and share findings. Let’s walk through the core internet services that matter most for academic work.

The internet and the web are not the same thing 🔗

Before discussing individual services, one distinction deserves attention. The internet is the global network of interconnected computers; the World Wide Web is one of many services that run on top of it. Email, file transfer, and remote login are all services that existed alongside – and in many cases before – the Web. Treating them as separate tools helps in picking the right one for a given research task.

Email: the backbone of scholarly communication 🔗

Electronic mail remains the single most widely used research tool on the internet. It is asynchronous, documented, and easy to archive – three qualities that suit the often slow, cross-timezone rhythm of academic work. A researcher in Delhi can send a draft manuscript to a co-author in Berlin at midnight, and the reply arrives whenever the collaborator logs in, without anyone needing to be online at the same time.

The academic importance of email is more than anecdotal. A study on scientific collaboration found that electronic mail was the primary technology used for communication between individual scientists and research teams, and that information technology overall enhanced both research output and the size of collaboration networks. Early-to-mid-career researchers, in particular, benefited in terms of quantity, quality, and the reach of their professional ties.

What email actually does for a researcher 🔗

In practical terms, email supports several overlapping research tasks. It is used to circulate drafts and reviewer comments, to schedule interviews, to request access to datasets, and to distribute questionnaires. Learning resources from the National Institute of Open Schooling describe email as a paperless method of sending messages, notes, or documents to one person or many simultaneously, and note that software and compressed digital images can be attached.

Each email address carries all the information needed to route a message. A typical address has a username, the ‘@’ symbol, a mail server, and a domain type – for example, username@institution.ac.in. The ‘.ac.in’ portion signals an academic institution in the country, which is often the first clue a recipient uses to judge whether a message is worth opening.

Mailing lists and discussion groups 🔗

Beyond one-to-one exchanges, researchers have long used mailing lists – sometimes called listservs – to follow ongoing disciplinary conversations. Historically, networks like BITNET built some of the earliest academic mailing lists, linking thousands of universities and producing archives whose quality reflected the sources contributing to them. The format persists today through subject-specific lists that circulate calls for papers, job openings, and discussion threads.

File Transfer Protocol: moving data across the network 🔗

Long before cloud storage became ubiquitous, FTP was how researchers moved large files across computers. The File Transfer Protocol is a standard communication protocol for transferring files between a client and a server over TCP/IP networks, typically using separate control and data connections.

How FTP works in practice 🔗

FTP operates on a client-server model. A researcher runs an FTP client on their own machine, connects to a remote server, authenticates, and then transfers files. Public archives often allow anonymous login, where users can connect without an account – typically by entering ‘anonymous’ as the username and an email address as the password – and download files freely from public repositories. This model made FTP especially valuable for distributing datasets, software, and preprints in the decades before the Web.

The objectives of FTP, as traditionally stated, are to promote sharing of computer files and programs, transfer data reliably and efficiently, and shield the user from differences in file storage systems between different computers. For a scholar downloading climatological records, genomic sequences, or statistical datasets, that last point matters: FTP lets a Windows user pull files off a Linux server without worrying about the underlying storage format.

Security concerns and modern variants 🔗

Standard FTP has a major flaw for modern use: it transmits data, including passwords, in plain text. This makes it vulnerable to interception on untrusted networks. For this reason, research institutions now typically use SFTP (SSH File Transfer Protocol) or FTPS, which encrypt the connection. A researcher handling sensitive interview data, personally identifiable information, or unpublished results should confirm that whichever service they use encrypts the transfer.

Telnet and remote login: operating a distant computer 🔗

Telnet is a utility that allows a user on one computer to log into and operate another computer over a network, almost as if they were sitting at its keyboard. Open educational material from IGNOU describes Telnet as a client-server service, where the client program runs on the user’s machine and communicates with a server on the remote system.

Why remote login matters for research 🔗

Many research tasks require computational power that a personal laptop simply cannot provide. Climate models, large-scale statistical simulations, and bioinformatics pipelines are typically run on institutional servers or high-performance computing clusters. Remote login lets a researcher connect to those machines from anywhere and run their analyses as if they were on-site.

Telnet was also historically a common way to search remote library catalogues and databases. University library systems across the world offered Telnet-based access so that scholars could query holdings without traveling.

From Telnet to SSH 🔗

Like FTP, Telnet has a serious security weakness: it sends all traffic – including login credentials – unencrypted. For this reason, Telnet has been almost entirely replaced by Secure Shell (SSH) for accessing servers. SSH offers the same remote terminal capability but encrypts the entire session. A scholar accessing a university computing cluster today is almost always using SSH, even if the older terminology of ‘remote login’ or ‘Telnet session’ still appears in textbooks.

The World Wide Web: the researcher’s default workspace 🔗

The World Wide Web is the service most researchers now spend the bulk of their online time on. It is worth remembering that the Web was designed with research in mind. CERN’s own account of the invention of the Web records that Tim Berners-Lee, a British scientist, invented the World Wide Web in 1989 while working there, and that the Web was originally conceived to meet the demand for automated information-sharing between scientists in universities and institutes around the world.

How the Web was built 🔗

According to the short history of the Web published by CERN, Berners-Lee wrote the first proposal in March 1989 and a second in May 1990. Together with Belgian engineer Robert Cailliau, he formalised the management proposal in November 1990, outlining the concepts and terms behind the Web. By the end of 1990, he had the first web server and browser running on a NeXT computer at CERN. In April 1993, CERN released the Web software into the public domain – a decision that allowed the technology to spread freely and is arguably the single most consequential step in its growth.

The Web rests on three technical foundations, all developed in that initial burst of work: HTML to format documents, HTTP to transfer them between computers, and the URL to identify them. Everything else – search engines, social platforms, online journals, institutional repositories – sits on top of those three.

Why the Web changed research 🔗

For researchers, the Web absorbed and extended functions that had previously been scattered across FTP, Gopher, and Telnet. An article in a journal can now be found through a search engine, downloaded through the browser, cited through a reference manager, and discussed through a comment thread – all without leaving the Web. Institutional repositories, preprint servers like arXiv and SSRN, government statistical portals, and open-access journal databases make an enormous body of material directly accessible.

But access is not the same as reliability. Anyone with an internet connection can publish a web page, which means a researcher must evaluate sources critically. Peer-reviewed journals, official government databases at the National Portal, reports from recognised international organisations, and institutional repositories are generally more trustworthy than open-web aggregators or personal blogs. Treating the Web as a starting point, not a finishing line, is part of good research practice.

How these services come together in a research workflow 🔗

In practice, these services rarely operate in isolation. A typical scenario looks something like this. A doctoral student searching for survey data on urban migration might use the Web to locate a dataset hosted on an institutional repository. She downloads the large data files using SFTP – a secure successor to FTP. She emails the dataset’s custodian to request access to a restricted variable. Once access is granted, she uses SSH, the modern form of remote login, to connect to her university’s computing cluster and run the statistical analysis there. Her results are then shared back with her supervisor over email and uploaded to a collaborative Web-based platform.

That single workflow uses every one of the core services discussed in this post. The protocols may have modernised, but the underlying logic – communicate, transfer, compute, publish – is unchanged.

A note on critical evaluation 🔗

The ease of access these services provide can quietly encourage intellectual shortcuts. A search result is not a citation; a downloaded PDF is not necessarily peer-reviewed; a dataset on a public server may still carry licensing restrictions. Good research practice means using these services as enablers while keeping traditional scholarly habits intact: checking authorship, verifying sources, cross-referencing claims, and documenting the route by which information was obtained. Tools change, but the discipline of research does not.

What do you think? Which of these internet services do you rely on most in your own research, and have you found that a particular service has shaped the kinds of questions you are able to ask?

References

1. https://pmc.ncbi.nlm.nih.gov/articles/PMC6948243/
2. http://oer.nios.ac.in/wiki/index.php/SERVICES_OF_INTERNET_-E-mail,_FTP,_Telnet
3. https://hermit.cc/it/inet/netintro.htm
4. https://egyankosh.ac.in/bitstream/123456789/25594/1/Unit-12.pdf
5. https://home.cern/science/computing/birth-web
6. https://home.cern/science/computing/birth-web/short-history-web
7. https://www.india.gov.in