Common network protocols divide networking into specialized jobs. IP addresses and routes datagrams, TCP and UDP move application data with different reliability trade-offs, DNS maps names to network addresses, HTTP and HTTPS deliver web resources, SMTP and IMAP handle different parts of email, FTP transfers files, and SSH provides secure remote services. A single web request commonly combines several of these protocols rather than relying on one protocol alone.
What a network protocol is
A network protocol is a shared set of message formats, procedures and expectations. It tells participating systems what a message means, how it is structured, what response is expected and how failures are handled. Protocols are not interchangeable product brands; they are agreements that let independently built devices and applications communicate.
![Computer Networking Bible: [3 in 1] The Complete Crash Course to Effectively Design, Implement and Manage Networks. Including Sections on Security, Performance and Scalability](https://m.media-amazon.com/images/I/41H4YJnxKgL._SL160_.jpg)
Each protocol has a scope. IP deals with addressing and routing. TCP and UDP provide transport behavior. DNS handles names. HTTP defines web requests and responses. TLS can protect an HTTP connection. SMTP and IMAP serve different email operations, while FTP and SSH address file transfer and secure remote services.
The protocol map
| Protocol | Main job | Important distinction |
|---|---|---|
| IP | Moves connectionless datagrams between network addresses | Addressing and routing, not delivery reliability |
| TCP | Reliable, connection-oriented end-to-end transport | Ordering, retransmission, flow control and connection overhead |
| UDP | Connectionless datagram transport | Low setup overhead; the application handles more responsibility |
| HTTP | Web request/response exchange | Stateless application semantics |
| HTTPS | HTTP protected with TLS | Confidentiality, integrity and endpoint authentication depend on TLS configuration |
| DNS | Host-name mapping and naming support | Human-readable names versus network addresses |
| SMTP | Electronic-mail delivery and relay | Sending role, not mailbox synchronization |
| IMAP4rev2 | Access to mailbox data | Server-side message access and synchronization |
| FTP | File transfer | Legacy workflow; encryption is not inherent |
| SSH | Secure remote login and related services | Encrypted services over an otherwise insecure network |
These roles reflect the foundational descriptions in RFC 1812, RFC 7230, RFC 4251, RFC 9051 and the Internet standards catalog RFC 2300. Implementations and protocol versions continue to evolve, so a standards document’s publication date is not a usage or performance statistic.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
IP: addressing and routing datagrams
Internet Protocol is the addressing and routing layer. RFC 1812 describes IP as a datagram, or connectionless, internetwork service. A datagram carries source and destination network addresses, and routers use those addresses to move it toward its destination.
IP does not by itself promise that a datagram arrives, arrives once, arrives in order or arrives within a deadline. Those guarantees, when needed, come from a transport protocol or from the application. This separation lets the same network layer carry traffic with very different requirements.
What IP does not tell you
- It does not identify the web page, email operation or remote command being requested; an application protocol supplies that meaning.
- It does not replace transport behavior. TCP or UDP may carry application data inside IP packets.
- A reachable IP address does not prove that the intended service is healthy. Name resolution, transport setup, security negotiation and application handling can still fail.
TCP versus UDP
TCP and UDP are the two primary transport protocols discussed by RFC 1812, but they solve different problems.
| Question | TCP | UDP |
|---|---|---|
| Connection model | Connection-oriented | Connectionless datagrams |
| Ordering | Provides resequencing | Application must handle ordering if it matters |
| Loss handling | Provides end-to-end reliability and retransmission behavior | No TCP-style delivery guarantee |
| Flow control | Provided by TCP | Application responsibility |
| Setup and overhead | Connection machinery adds state and overhead | Lower setup overhead |
| Best fit | Data that must arrive completely and in order | Applications that can tolerate loss or need to control timing themselves |
Calling UDP universally faster or TCP universally better is misleading. The correct choice depends on tolerance for delay, loss and reordering, plus how much reliability logic the application is prepared to implement. A protocol designer may choose TCP for dependable byte-stream delivery or UDP when connection setup and built-in retransmission would conflict with the application’s timing model.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →DNS: turning names into destinations
The Domain Name System lets people and applications use host names while network communication uses addresses. A client asks DNS for information associated with a name, receives an answer from the configured DNS service and can then attempt communication with the resulting destination.
DNS is a naming service, not a web server. A successful name lookup only establishes that a name was mapped; the destination may still reject a connection, fail TLS negotiation or return an application error. Conversely, a web service can be functioning while a local DNS problem prevents a user from finding it by name.
Useful diagnostic distinction
- Name failure: the host name cannot be resolved or returns an unexpected address. Investigate the DNS configuration and the name being requested.
- Transport failure: the name resolves, but no usable connection is established. Investigate routing, filtering or the service endpoint.
- Application failure: the connection works, but HTTP, email or another application protocol returns an error. Investigate that service’s configuration.
DHCP is also common in operational networks because it supplies host configuration, but detailed lease messages, ports and option behavior require the relevant DHCP specification. Treat it as a configuration companion to the protocols above rather than as a replacement for DNS or IP.
HTTP and HTTPS on the web
HTTP is a stateless application-level request/response protocol. A client sends a request describing a resource or operation, and a server returns a response. The uniform interface hides the server’s internal implementation from the client.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsHTTPS is HTTP carried with TLS protection. RFC 7230 describes the https URI scheme as depending on TLS and TCP. TLS can provide confidentiality, integrity and endpoint authentication when it is correctly negotiated and configured. HTTPS alone does not guarantee that a website’s content is accurate, that its code is free of vulnerabilities or that a user’s action is safe.
Why HTTP is called stateless
Each request contains the information needed for the server to interpret that request. Any continuity across requests is implemented separately, such as by application-managed identifiers or server-side state. Statelessness describes the protocol’s request/response semantics; it does not mean real web applications cannot maintain user sessions.
Protocol-version caution
RFC 7230 is an HTTP/1.1 architectural document, and later HTTP specifications supersede parts of it. Use it for the foundational request/response explanation, but check the version and deployment details when documenting a particular implementation, transport, header or security recommendation.
Email: SMTP and IMAP4rev2
SMTP sends and relays mail
SMTP, the Simple Mail Transfer Protocol, is used for electronic-mail delivery. In a typical flow, a sending system submits or relays a message toward a receiving system. SMTP’s role is moving mail between systems; it is not the protocol a user normally uses to browse and synchronize an existing mailbox.
IMAP accesses mailbox data
IMAP4rev2, specified in RFC 9051, lets a client work with messages stored in a mailbox and synchronize mailbox data. Its role complements SMTP: one protocol delivers mail, the other provides access to stored mail.
RFC 9051 warns that IMAP transactions, including email data, are sent in the clear unless protection is negotiated. Unprotected sessions can therefore be exposed to eavesdropping and manipulation. Providers differ in their available ports, authentication methods and required protection, so do not infer a provider’s exact connection settings from the protocol name alone.
FTP and SSH
FTP is a file-transfer protocol
FTP names a file-transfer service and its traditional workflow. The protocol itself does not imply encryption. A deployment needs a separately specified protection mechanism if credentials and file contents must be protected in transit.
SSH provides secure remote services
RFC 4251 describes SSH as a protocol for secure remote login and other secure network services over an insecure network. SSH normally runs over a TCP/IP connection. Its scope is broader than copying a file: it provides a secure protocol framework for remote administration and related services.
Do not automatically equate SFTP with FTP. SFTP is an SSH subsystem whose details are outside the FTP description here; verify the specific subsystem and server implementation before documenting commands, authentication or compatibility.
How a typical web request uses several protocols
- Resolve the name. The client uses DNS to map a host name to one or more network addresses.
- Address packets. IP places source and destination addresses on datagrams and routers forward them.
- Establish transport. A TCP-based deployment creates the reliable transport needed by the web exchange. Other protocol versions or deployments can use a different stack.
- Protect the channel. For HTTPS, TLS is negotiated over the underlying transport and verifies the endpoint according to its configuration.
- Exchange application messages. HTTP carries the request and response, while the server applies its own application logic.
- Interpret the result. The client separates a DNS problem, transport problem, TLS problem and HTTP response because each belongs to a different protocol layer.
The stack is the key idea: no single protocol performs naming, routing, reliable delivery, encryption and web semantics at once.
Choosing the right protocol: a developer’s checklist
- Define the function: Are you routing packets, mapping names, exchanging web resources, delivering mail, accessing a mailbox, transferring files or administering a remote system?
- Choose a connection model: Do you need TCP’s connection and reliability machinery, or can your application manage loss and ordering over UDP?
- Set reliability expectations: Identify whether ordering, retransmission and flow control are protocol requirements or application responsibilities.
- Specify protection: Decide where TLS, SSH or another protection layer is negotiated, and document how endpoint authentication is validated.
- Separate names from addresses: DNS configuration and IP routing are distinct failure domains.
- Check the version: Standards evolve. Record the protocol version and deployment assumptions instead of treating an older RFC as the complete modern specification.
Common failure patterns and fixes
| Symptom | Likely layer | What to check |
|---|---|---|
| A host name cannot be resolved | DNS | Requested name, local resolver configuration and the address returned |
| Name resolves, but the destination is unreachable | IP or transport | Routing path, filtering and whether the service endpoint is listening |
| Connection starts, then security negotiation fails | TLS or SSH | Protection settings, endpoint identity and compatible protocol configuration |
| Mail sends but does not appear in a mailbox | SMTP/IMAP division | Delivery path on the SMTP side and mailbox synchronization on the IMAP side |
| File transfer exposes credentials or contents | FTP deployment | Whether a separately specified secure mechanism is enabled; FTP alone is not encryption |
| Web connection works but content is wrong | HTTP/application | Request target, response status and server-side application behavior |
Diagnose from the bottom up without assuming that a successful lower layer proves higher layers are healthy. An IP route does not prove TCP can establish a session; a TCP session does not prove TLS succeeded; TLS success does not prove the HTTP application returned the intended resource.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup: ScreenshotNeo as an HTTP example
If your practical goal is to capture a page rather than study browser automation, ScreenshotNeo exposes a single GET endpoint: https://api.screenshotneo.com/v1/shot. The request uses HTTP, and the response is a PNG, JPEG, WebP or PDF depending on the options you send.
Best Value
- Used Book in Good Condition
ScreenshotNeo removes cookie and consent banners, newsletter popups and chat widgets before capture. More than 60 known consent platforms and similar interruptions are covered, and each cleanup step can be disabled. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads and cache hits are not billed; response headers identify the page verdict and whether the request was billed.
One-call examples
See the ScreenshotNeo API documentation for the complete parameter list. These runnable examples capture Stripe’s home page as a WebP file.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpimport requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);Options useful to developers
- Full-page capture loads lazy images; CSS selectors can target one element.
- Choose dark mode, any viewport, 12 device presets and retina scale.
- Create PDFs with paper size, margins, landscape mode and page ranges.
- Render HTML/CSS, run custom JavaScript, click an element, wait for a selector, delay or network idle.
- Block ads, trackers, requests or resource types; provide custom headers, cookies, user agent and Authorization.
- Set timezone and geolocation, use a transparent background or resize the image.
- Choose a cache TTL, create signed links for public
<img>tags, submit asynchronous jobs with signed webhooks and capture up to 100 URLs per bulk call. - Use the usage API, OpenAPI specification and familiar parameter names used by other screenshot APIs when switching.
ScreenshotNeo also provides an MCP server for Claude, Cursor and other MCP clients, with take_screenshot, get_page_info and capture_pdf tools. Every feature is available on every plan. The free plan includes 1,000 shots per month without a card; paid plans start at $5 for 3,000 shots, followed by $15 for 15,000, $39 for 60,000, $99 for 250,000 and $249 for 1,000,000. Yearly billing gives two months free.
Create a free ScreenshotNeo account to try 1,000 screenshots a month with no card.
Recommended Free Tools
FAQ
Do all networks use exactly the same protocol stack?
No. Protocol versions and deployments vary. The stable concept is the division of responsibilities: naming, addressing, transport, protection and application semantics may be supplied by different protocols.
Is SFTP simply a more secure mode of FTP?
Not automatically. SFTP is an SSH subsystem rather than a property that FTP gains by itself. Confirm the server’s supported subsystem and its documented behavior before assuming FTP commands or compatibility.
Frequently Asked Questions
Do all networks use exactly the same protocol stack?
No. Protocol versions and deployments vary. The stable concept is the division of responsibilities: naming, addressing, transport, protection and application semantics may be supplied by different protocols.
Is SFTP simply a more secure mode of FTP?
Not automatically. SFTP is an SSH subsystem rather than a property that FTP gains by itself. Confirm the server’s supported subsystem and its documented behavior before assuming FTP commands or compatibility.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
