The web is not just “the internet.” This confusion, prevalent even in technical documentation, obscures a precise architecture: the World Wide Web is an application service that runs on top of the TCP/IP stack, just like email or file transfer. Understanding the web means first grasping this distinction between the network infrastructure and the software layer that utilizes its protocols.
DNS Resolution and HTTP Negotiation: What Happens Before a Page is Displayed
When a user enters a URL in their browser, the first operation has nothing to do with HTML. The browser queries a DNS server to convert the domain name into an IP address. This resolution goes through several relays (recursive resolver, root servers, TLD servers, authoritative server) before returning the address of the target server.
Read also : The Rarest Cars to Know: Exceptional Models and Automotive Rarities
Once the IP address is obtained, the browser opens a TCP connection, then initiates a TLS negotiation if the URL starts with HTTPS. It is only after this exchange of certificates and keys that the HTTP request actually goes to the server.
The server responds with a status code. A code 200 means that the requested resource is available. A 301 indicates a permanent redirect, a 404 a resource not found. We observe that the majority of performance issues perceived by users stem from this resolution and negotiation phase, not from the HTML rendering itself.
Related reading : The ethical and collaborative search engine: a privacy-respecting alternative
To delve deeper into the definition of the web on Wiki Dark, it is essential to start from this network mechanism rather than the usual metaphor of a spider web.
Client-Server Architecture of the Web: The Role of the Browser and HTML Code
The web is based on an asymmetric client-server model. The client (the browser) sends requests, the server returns resources. These resources are not just pages: an HTML document references images, CSS stylesheets, JavaScript scripts, fonts. Each element is the subject of a distinct request.
HTML structures the content, CSS styles it, JavaScript makes it interactive. This separation of responsibilities remains the fundamental principle of the web, even if modern frameworks blur it by generating HTML on the server or client side depending on the case.
What the Browser Actually Does
The browser is not just a display tool. It analyzes the HTML to build a DOM tree, calculates the CSS styles to produce a render tree, executes the JavaScript that can modify these two trees in real-time. This rendering pipeline explains why the same HTML code can display differently depending on the browser used.
Web developers systematically test their sites on multiple rendering engines (Blink for Chrome and Edge, Gecko for Firefox, WebKit for Safari). Differences in CSS interpretation or JavaScript APIs between these engines are a constant source of visual bugs.
Open Web vs. Closed Platforms: A Fundamental Issue for Online Content
Since the early 2020s, a growing share of time spent online is shifting towards closed environments: mobile apps, messaging, social networks. These platforms do not operate like the web. Their content is not indexed by search engines, is not linked by open hyperlinks, and relies on a single operator.
The open web is based on three pillars that these platforms do not respect:
- Universal addressability: each resource has a URL that anyone can share, without registration or dedicated application
- Interoperability: a browser is sufficient to access any site, regardless of the operating system or device manufacturer
- Indexability: search engines crawl the web by following hyperlinks, making content discoverable by all
This distinction has direct consequences for communication and visibility online. Content published on a closed platform exists only for users of that platform. Content published on the open web is potentially accessible to all connected users.
Web Portal and Web Apps: The Boundary Between Site and Application is Blurring
A website is no longer simply about publishing static HTML pages. Publishers like Jahia describe the web portal as a unified access point to personalized services, integrating authentication, internal data, and business applications. The boundary between a content site and a complete software application has become blurred.
This evolution changes the very nature of what we call “the web.” E-commerce sites manage carts, payments, customer spaces. Institutional sites offer dynamic forms and automations. These functionalities were reserved for software installed on a workstation just a few years ago.
Consequences for Web Development
This complexity explains the growing specialization of the web developer profession. The CNED notes that this profession now covers skills ranging from front-end integration to back-end development, including database management and deployment on hosting servers.
Web hosting itself has transformed, evolving from simple storage spaces for HTML files to infrastructures capable of running complete applications, with load management and geographical data distribution.
The web remains, despite these changes, the only digital communication system where a user can access content or a service without installing anything, from any device with a browser. This architectural characteristic, inherited from its original design, is precisely what distinguishes it from all proprietary platforms that attempt to replace it.