Study guide
16.4 How the Internet Works: Protocols, IP Addressing, DNS, URLs, and Reliability
Praxis Computer Science 5652
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Praxis 5652 Exam Overview and ETS Pseudocode
1.1 Praxis 5652 Test Facts, Scoring, and Registration 1.2 Official ETS Pseudocode Notation and Tracing Strategy
2 Chapter 2: Impacts of Computing: Innovation, Access, and Effects
2.1 Computing for Creativity, Problem Solving, Communication, and Innovation 2.2 Equal Access, the Digital Divide, and Accessibility 2.3 Beneficial and Harmful Effects of Computing Innovations
3 Chapter 3: Impacts of Computing: Intellectual Property, Ethics, Privacy, and Security
3.1 Intellectual Property: Copyright, Open Source, and Creative Commons 3.2 Ethical and Unethical Computing Practices and Their Implications 3.3 Privacy, Security, Data Collection, and Local vs. Cloud Storage
4 Chapter 4: Algorithms and Computational Thinking: Abstraction, Decomposition, Number Bases, and Representation
4.1 Abstraction and Abstraction Hierarchies 4.2 Decomposition, Pattern Recognition, and Developing Algorithms 4.3 Number Bases: Binary, Octal, Decimal, and Hexadecimal 4.4 Algorithm Formats: Natural Language, Flowcharts, Pseudocode, and Tracing
5 Chapter 5: Algorithms: Efficiency, Limits of Computing, and Randomization
5.1 Algorithm Efficiency: Linear, Quadratic, Exponential, and Logarithmic Growth 5.2 Limits of Computing: Unsolvable Problems, Intractability, and Heuristics 5.3 Randomization, Random vs. Pseudorandom Numbers, and Scaling to a Range
6 Chapter 6: Algorithms: Searching, Sorting, and Recursion
6.1 Searching Algorithms: Linear Search and Binary Search 6.2 Sorting Algorithms: Tracing, Comparisons, Correctness, and Efficiency 6.3 Recursion: Base Cases, Tracing, Errors, and Iterative Equivalents
7 Chapter 7: Programming: Variables, Data Types, Strings, and Expressions
7.1 Variables, Data Types, and Type Conversion 7.2 Strings and String Operations 7.3 Operators, Precedence, Expressions, and Formulas 7.4 Boolean Expressions, Truth Tables, and Boolean Algebra
8 Chapter 8: Programming: Selection, Iteration, and Writing Code
8.1 Sequence and Selection: if, else, Chained and Nested Conditions 8.2 Iteration: for, while, do … while, and repeat … until Loops 8.3 Reading, Completing, and Modifying Code
9 Chapter 9: Programming: Procedures, Arrays, and Data Structures
9.1 Procedures, Parameters, Return Values, Nested Calls, and Scope 9.2 Arrays, Lists, and Two-Dimensional Arrays 9.3 Stacks, Queues, and Dictionaries (Maps)
10 Chapter 10: Programming: Correctness, Errors, Testing, and Code Quality
10.1 Program Correctness: Preconditions, Postconditions, Invariants, and Testing vs. Proof 10.2 Error Types and Debugging Techniques 10.3 Choosing Useful Test Cases: Boundaries, Partitions, Coverage, and Regression 10.4 Extensibility, Modifiability, and Reusability: Constants and Parameterization 10.5 Documentation, Code Reviews, Peer Feedback, and End-User Feedback
11 Chapter 11: Programming: Events, Usability, Input Validation, and APIs
11.1 Event-Driven Programming, Asynchronous Events, and Concurrency 11.2 Usability, Meaningful Error Messages, and Input Validation vs. Verification 11.3 Libraries and APIs: Reading Definitions, Making Calls, and Weighing Trade-offs
12 Chapter 12: Programming: Languages, Tools, Paradigms, and Object-Oriented Design
12.1 Low- and High-Level Languages, Compilers and Interpreters, and IDEs 12.2 Programming Paradigms: Procedural, Object-Oriented, and Others 12.3 Classes, Objects, Instance Variables, Methods, and Encapsulation 12.4 Inheritance, Polymorphism, and Overloading vs. Overriding
13 Chapter 13: Data: Bits, Encoding, Compression, and Encryption
13.1 Bits and Bytes: Why Binary, Storage Calculations, and Signed Integers 13.2 Encoding Text, Images, and Sound 13.3 Lossless and Lossy Compression: Run-Length Encoding, Huffman Coding, and Media Formats 13.4 Encoding vs. Encryption, Symmetric and Public-Key Encryption, and Their Trade-offs
14 Chapter 14: Data: Analysis Tools, Simulation, Storage, and Collection
14.1 Analyzing Data with Spreadsheets: Cleaning, Transforming, and Visualizing 14.2 Simulation and Modeling 14.3 Files, Databases, and Storage Requirements: Scale, Redundancy, and Backup 14.4 Collecting, Aggregating, and Generating Data: Public Data Sets, Surveys, Sensors, and Crowdsourcing
15 Chapter 15: Computing Systems: Hardware, Operating Systems, and Computing Environments
15.1 Hardware Components and the Fetch–Decode–Execute Cycle 15.2 Operating Systems, Software Components, and Resource Issues 15.3 Embedded Systems, the Internet of Things, and Types of Computing Systems 15.4 Local, Network, and Cloud Computing and Storage; How Binary Data Are Stored
16 Chapter 16: Networks, the Internet, the Web, and Cybersecurity
16.1 Network Types and Wired and Wireless Communication 16.2 Network Hardware and Layered Network Models (OSI and TCP/IP) 16.3 Network Performance: Bandwidth, Latency, Load, and Estimating Needs 16.4 How the Internet Works: Protocols, IP Addressing, DNS, URLs, and Reliability 16.5 The Web: HTTP, HTML and Markup Languages, Browsers, Servers, and Clients 16.6 Cybersecurity: The Five Pillars, Strong Passwords, Security Strategies, and Trade-offs
16.4 How the Internet Works: Protocols, IP Addressing, DNS, URLs, and Reliability
Key Takeaways Explain This Topic AI
A protocol is an agreed set of rules for formatting and exchanging data, so devices from different makers can communicate; common Internet protocols include IP, TCP, UDP, DNS, DHCP, HTTP, HTTPS, and SMTP.
IPv4 addresses are 32 bits, written as four decimal numbers such as 192.0.2.10 (about 4.3 billion addresses); IPv6 addresses are 128 bits, written in hexadecimal groups separated by colons (about 3.4 × 10³⁸ addresses).
In https://www.example.edu:8443/classes/cs101?week=3 , https is the protocol (scheme), www is the subdomain, example.edu is the domain name (with the top-level domain .edu), 8443 is the port, and /classes/cs101 is the path.
DNS is a distributed hierarchy: root servers point to top-level-domain servers such as .com and .edu, which point to the authoritative servers for each domain, which return its IP addresses.
TCP provides reliability with sequence numbers, acknowledgments, retransmission, and checksums; the Internet gains redundancy from multiple routes, and packet switching lets traffic flow around failures.
Last updated: September 2026
What this competency asks
ETS asks you to be familiar with how Internet and Web protocols work :
Describe the purpose of protocols and identify common Internet and Web protocols.
Compare IPv4 and IPv6.
Identify and describe the basic parts of a URL (for example, protocol, subdomain, domain name, port, and path).
Describe the hierarchical structure of names in the Domain Name System (DNS).
Describe the purpose and function of IP addressing .
Identify how Internet protocols address reliability, redundancy, and error handling .
Why protocols?
A protocol is a set of rules for how data are formatted, sent, received, and acknowledged. Because the Internet's protocols are open standards , a phone from one company can load a web page from a server built by another over equipment made by a third. Protocols are organized in layers (Section 16.2).
- Protocol Purpose Layer Default port
- IP (Internet Protocol) Addresses and routes packets between networks Internet —
- TCP (Transmission Control Protocol) Reliable, ordered, connection-based delivery Transport —
- UDP (User Datagram Protocol) Fast, connectionless delivery with no guarantees Transport —
- HTTP / HTTPS Web requests and responses; HTTPS adds TLS encryption Application 80 / 443
- DNS (Domain Name System) Translates domain names to IP addresses Application 53
- DHCP Assigns IP addresses to devices automatically when they join a network Application 67 / 68
- SMTP Sends email between servers Application 25 (587 for submission)
- IMAP / POP3 Retrieve email to a client Application 143 / 110
- FTP , SFTP File transfer (SFTP runs over SSH and is secure) Application 21 / 22
- SSH Secure remote login Application 22
- TLS Encryption and authentication for other protocols, such as HTTPS Between application and transport —
Ports identify which program on a device should receive the data. The IP address gets data to the right computer, and the port gets it to the right application.
IP addressing
An IP address identifies a device's network interface and its location in the network , so routers can forward packets toward it, much as a street address does for mail.
DHCP usually assigns addresses automatically ( dynamic ). Servers often keep static addresses.
Private addresses, such as 192.168.x.x , 10.x.x.x , and 172.16.0.0 – 172.31.255.255 , are used inside local networks and are not routed on the public Internet. A router's NAT lets many private devices share one public address.
IPv4 vs. IPv6
- IPv4 IPv6
- Size 32 bits 128 bits
Notation Four decimal numbers (0–255) separated by dots: 192.0.2.10 Eight groups of four hex digits separated by colons: 2001:0db8:0000:0000:0000:0000:0000:0001
- Shortening — Drop leading zeros and replace one run of zero groups with :: , giving 2001:db8::1
- Address space 2³² ≈ 4.3 billion 2¹²⁸ ≈ 3.4 × 10³⁸
Status Free addresses ran out in the 2010s; extended by NAT Designed to replace IPv4; the two run side by side today
- Other Relies heavily on NAT Enough addresses for every device; built-in autoconfiguration
- (The addresses 192.0.2.x and 2001:db8:: are reserved for documentation examples.)
- Parts of a URL
A URL (uniform resource locator) identifies a resource on the Web.
https://www.example.edu:8443/classes/cs101/index.html?week=3#quiz
- Part Value Meaning
- Protocol (scheme) https How to communicate: secure HTTP
- Subdomain www A host or section within the domain
- Domain name example.edu The registered name: second-level domain example plus top-level domain .edu
- Top-level domain (TLD) .edu The highest level of the name hierarchy
- Port 8443 Optional; when omitted, HTTPS uses 443 and HTTP uses 80
- Path /classes/cs101/index.html Which resource on the server
- Query string ?week=3 Parameters sent to the server
- Fragment #quiz A location within the page, handled by the browser
Watch for look-alike domains in phishing links. In https://example.edu.login-check.com/ , the actual registered domain is login-check.com , and example.edu is only a subdomain of it.
The Domain Name System
People use names, and routers use numbers. DNS translates between them. Names are hierarchical , read from right to left: . (root)
- └── edu (top-level domain)
- └── example (second-level domain: example.edu)
- └── www (subdomain / host: www.example.edu)
Resolving www.example.edu :
The device checks its own cache, then asks its configured recursive resolver , typically run by the ISP, school, or a public DNS service.
If the answer is not cached, the resolver asks a root server , which refers it to the .edu TLD servers .
A .edu server refers it to the authoritative servers for example.edu.
The authoritative server returns the IP address (an A record for IPv4 or an AAAA record for IPv6).
The resolver caches the answer for its time-to-live (TTL) and returns it to the device.
DNS is distributed : no single server holds every name, and each zone is served by multiple servers, which gives both scale and redundancy .
Reliability, redundancy, and error handling
- Mechanism What it handles
- TCP sequence numbers Reassembles segments in the correct order
- TCP acknowledgments and retransmission Resends data that were lost or not acknowledged in time
Checksums (in TCP, UDP, and IPv4 headers; CRC in Ethernet frames) Detect corrupted data, which is then discarded and, with TCP, resent
- TCP flow and congestion control Slows the sender when the receiver or network is overloaded
- Packet switching and dynamic routing Routers find alternate paths when links fail
- Redundant links, servers, and DNS servers No single failure takes down the service
- Time-to-live (hop limit) Discards packets caught in routing loops
TCP or UDP? TCP establishes a connection with a three-way handshake (SYN, SYN-ACK, ACK) and guarantees ordered, complete delivery, so web pages, email, and file transfers use it. UDP skips the handshake and guarantees, trading reliability for speed, so live video, voice calls, games, and most DNS lookups use it. For them, a late packet is useless anyway.