Internet and the web

1. The Fundamental Distinction: Internet versus Web#

A common error among beginning technology students is using the terms Internet and World Wide Web interchangeably. They represent two fundamentally distinct layers of computing infrastructure:

• The Internet (The Infrastructure): The vast global physical and logical network of interconnected networks. It encompasses optical fiber cables, undersea pipelines, satellite links, routers, switches, and the core routing protocols (IP, BGP). It serves as the general highway system.
• The World Wide Web (A Service): A specific information-sharing service built on top of the Internet, invented by Sir Tim Berners-Lee in 1989. It is a collection of hyperlinked documents, media, and web applications accessed via web browsers using Uniform Resource Locators (URLs) and the HTTP protocol.

       +-------------------------------------------------------+
       |               THE WORLD WIDE WEB (HTTP/S)             |
       |  (Websites, HTML, CSS, JavaScript, Web APIs)         |
       +-------------------------------------------------------+
       | Other Services Built on Top of the Internet:          |
       |  [ Email: SMTP/IMAP ]  [ File Transfer: SFTP ]        |
       |  [ Voice/Video: VoIP ] [ Remote Shell: SSH ]          |
       +-------------------------------------------------------+
       |                  THE INTERNET                         |
       |  (TCP/IP, Routers, Fiber Optics, Submarine Cables)    |
       +-------------------------------------------------------+

---

2. Anatomy of a Uniform Resource Locator (URL)#

A Uniform Resource Locator (URL) provides the global unique address used by web browsers to locate and retrieve specific resources across the network:

https://www.learnquestly.com:443/subjects/science/?sort=alpha#photosynthesis
\___/   \__________________/\__/ \_______________/\__________/\_____________/
  |               |           |          |             |             |
Scheme         Hostname     Port       Path          Query        Fragment

| URL Component | Role and Syntax | Practical Explanation | | :--- | :--- | :--- | | Scheme (Protocol) | https:// or http:// | Defines the communication protocol used by client and server. | | Subdomain | www. | Designates a specific cluster or service host within the primary domain. | | Domain & TLD | learnquestly.com | Human-readable identity registered with ICANN (.com is the Top-Level Domain). | | Port | :443 (HTTPS) or :80 (HTTP) | Numerical network port directing traffic to a specific software service. Usually omitted in browsers. | | Path | /subjects/science/ | Hierarchical resource location or routing endpoint on the target server. | | Query Parameters| ?sort=alpha | Key-value pairs (key=value) passing dynamic query arguments to the server. | | Fragment Identifier| #photosynthesis | Client-side anchor pointing to an exact element ID within the rendered document (not sent to server). |

---

3. The Complete Journey of a Web Request#

When you enter https://learnquestly.com into your browser address bar and press Enter, a precise sequence of networking events unfolds in fractions of a second:

+------------+       1. DNS Query       +---------------------+
|            +------------------------->| DNS Recursive       |
|            |<-------------------------+ Resolver (8.8.8.8)  |
|            |    Returns IP: 172.67.x  +---------------------+
|            |
|            |    2. TCP 3-Way Handshake (SYN, SYN-ACK, ACK)
|            +================================================+
|  CLIENT    |
| (Browser)  |    3. TLS 1.3 Cryptographic Handshake (Key Exchange)
|            +================================================+
|            |
|            |    4. Encrypted HTTP GET / Request
|            +----------------------------------------------->+  WEB
|            |                                                |  SERVER
|            |    5. HTTP 200 OK + HTML Payload               |
|            |<-----------------------------------------------+
+------------+

Stage 1: Domain Name Resolution (DNS)

Computers communicate using numeric IP addresses, not English words:

1. The browser checks its local memory cache, then queries the operating system cache.
2. If unresolved, a recursive query is dispatched to the configured Recursive DNS Resolver (often provided by your ISP or a public provider like Cloudflare 1.1.1.1 or Google 8.8.8.8).
3. The resolver queries the hierarchical DNS tree:
   • Root Nameserver (.): Directs the resolver to the .com TLD servers.
   • TLD Nameserver (.com): Directs the resolver to the authoritative nameservers for learnquestly.com.
   • Authoritative Nameserver: Returns the authoritative IP address (e.g., 104.21.54.120).

Stage 2: Establishing the TCP Connection (3-Way Handshake)

Web communication requires reliable packet sequencing governed by the Transmission Control Protocol (TCP):

1. SYN (Synchronize): Client sends a packet with a random initial sequence number $A$ requesting a connection.
2. SYN-ACK (Synchronize-Acknowledge): Server acknowledges receipt by sending back $A + 1$ and provides its own sequence number $B$.
3. ACK (Acknowledge): Client returns $B + 1$. The reliable two-way connection channel is now established.

Stage 3: TLS 1.3 Encryption Handshake

For https:// connections, before any application data is sent, the client and server establish an encrypted tunnel using Transport Layer Security (TLS):

1. The server presents a digital certificate signed by a trusted Certificate Authority (CA) (e.g., Let's Encrypt).
2. The browser validates the cryptographic certificate signature against its built-in trust store.
3. Using asymmetric cryptography (Elliptic Curve Diffie-Hellman), client and server negotiate a shared symmetric session key. All subsequent traffic is encrypted with this ephemeral key.

Stage 4: HTTP Request and Response

1. The client transmits an HTTP request:

   GET / HTTP/2
   Host: learnquestly.com
   User-Agent: Mozilla/5.0
   Accept: text/html,application/xhtml+xml
   

2. The server processes the request and responds with a status code and content:

   HTTP/2 200 OK
   Content-Type: text/html; charset=UTF-8
   Cache-Control: public, max-age=3600
   
   <!DOCTYPE html><html>...</html>
   

Stage 5: Browser Parsing and Rendering

Upon receiving the HTML stream:

1. The browser engine parses HTML tokens to construct the Document Object Model (DOM) tree.
2. It parses CSS style rules to build the CSS Object Model (CSSOM) tree.
3. It combines DOM and CSSOM into a Render Tree, computes geometrical layout boxes (reflow), and paints colored pixels onto the display canvas.

---

4. Understanding IP Addresses: IPv4 versus IPv6#

Every device connected to the Internet must possess a unique numeric Internet Protocol (IP) address:

| Protocol | Address Format | Address Length | Total Theoretical Address Pool | Example Address | | :--- | :--- | :--- | :--- | :--- | | IPv4 | 4 decimal octets separated by dots | $32\text{ bits}$ | $2^{32} \approx 4.29\text{ billion}$ | 192.0.2.1 | | IPv6 | 8 hexadecimal groups separated by colons | $128\text{ bits}$ | $2^{128} \approx 3.4 \times 10^{38}$ | 2001:0db8:85a3::8a2e:0370:7334 |

Because the global expansion of smartphones, smart home appliances, and cloud servers exhausted the 4.3 billion IPv4 address pool, the global telecommunications infrastructure is transitioning to IPv6, ensuring every device on Earth can maintain a unique public address indefinitely.

---

5. Security Realities: What HTTPS Guarantees (and What It Doesn't)#

A pervasive misconception on the Internet is that a padlock icon in the browser address bar certifies that a website is trustworthy, reputable, or safe to buy from.

What HTTPS Actually Guarantees

• Confidentiality (Encryption): Intermediate eavesdroppers (such as someone on the same public Wi-Fi network or an ISP) cannot read your passwords, credit card numbers, or browsing contents.
• Data Integrity: Network routers cannot secretly tamper with or inject advertisements into packets while in transit.
• Server Authentication: The browser is communicating with the legitimate owner of that specific domain name, not an imposter.

What HTTPS Does NOT Guarantee

• Honesty of the Operator: Malicious actors and phishing criminals can obtain valid, free SSL/TLS certificates just as easily as legitimate businesses.
• Absence of Malware: An encrypted connection can deliver malicious software just as efficiently as an unencrypted one.
• Content Accuracy: HTTPS certifies the delivery pipe, not the truth of the information contained inside it.

---

6. Common Misconceptions to Avoid#

• Misconception 1: "The Web is the Internet." Correction: The Web is merely one hypermedia application running over the underlying Internet, just as email, SSH, and online gaming run over it.
• Misconception 2: "A green padlock means the website is legitimate and safe." Correction: The padlock only confirms the connection is encrypted. Phishing websites regularly use valid SSL certificates.
• Misconception 3: "DNS servers store the contents of web pages." Correction: DNS servers only act as phonebooks, mapping domain names to IP addresses. The actual web pages reside on web servers.
• Misconception 4: "Search engines search the live internet in real-time." Correction: Search engines like Google crawl and index copies of web pages into vast proprietary databases ahead of time, querying their own pre-built index when a user searches.