| |

Internet Beginner 11 ๐ŸŒ Cheatsheet

โฑ๏ธ Estimated read: 4 min | |

Key point: A web request travels through DNS (name to IP), TCP (connection), TLS (encryption), and HTTP (request/response), and the browser is the environment that orchestrates all four. Every concept in this cheatsheet maps to one stage of that journey.


The Internet vs the Web

TermMeaning
InternetThe global network of interconnected networks
WebA service built on the internet (HTTP + browsers)
ProtocolAn agreed format for communication
PacketA small unit of data sent over the network
RouterA device that forwards packets between networks

The internet is the infrastructure; the web is one application running on it. Email, SSH, DNS, and streaming also use the internet.


IP Addresses vs MAC Addresses

AspectIP AddressMAC Address
LayerNetwork (L3)Data link (L2)
FormatIPv4: 192.168.1.10 / IPv6: 2001:db8::100:1A:2B:3C:4D:5E
ScopeRoutable across networksLocal to a network segment
Assigned byISP, DHCP, or manuallyManufacturer
ChangesCan changeFixed to hardware
IP TypeMeaning
PublicGlobally routable
PrivateLocal only (10.x, 172.16โ€“31.x, 192.168.x)
Loopback127.0.0.1 (self)
StaticManually assigned
DynamicAssigned by DHCP

Domain Names

TermMeaning
Domain nameHuman-readable name for an IP (example.com)
TLDTop-level domain (.com, .org, .uk)
SLDSecond-level domain (example in example.com)
SubdomainPrefix (www, api, blog)
FQDNFully qualified name (api.example.com.)
RegistrarCompany that sells domain registration
WHOISPublic record of domain ownership

URL vs URI Anatomy

PartExampleMeaning
Schemehttps://Protocol
Authorityuser@api.example.com:443Userinfo + host + port
Hostapi.example.comDomain or IP
Port:443Optional; default by scheme
Path/v1/users/42Resource location
Query?page=2&sort=ascParameters
Fragment#sectionClient-side anchor (not sent to server)

A URI is the general identifier; a URL is a URI that also locates the resource. All URLs are URIs; not all URIs are URLs (mailto: is a URI, not a URL).


Web Hosting

TypeDescription
SharedMany sites on one server
VPSVirtual private server slice
DedicatedEntire physical server
CloudVirtual instances, scaling
StaticHTML/CSS/JS only, no server code
ServerlessFunctions triggered on demand
ConceptMeaning
Web serverSoftware serving HTTP (Nginx, Apache, Caddy)
Document rootDirectory served as /
Virtual hostMultiple sites on one server
CDNDistributed caching edge network

DNS Resolution

RecordPurpose
ADomain โ†’ IPv4
AAAADomain โ†’ IPv6
CNAMEAlias to another name
MXMail server
TXTVerification, SPF
NSAuthoritative nameservers
Resolver StepServer
1Stub resolver (OS)
2Recursive resolver (ISP/8.8.8.8)
3Root server
4TLD server (.com)
5Authoritative nameserver
6Answer cached

DNS uses UDP port 53. Caching occurs at browser, OS, resolver, and authoritative levels, governed by TTL.


HTTP Fundamentals

MethodPurposeBody
GETRetrieveNo
POSTCreateYes
PUTReplaceYes
PATCHPartial updateYes
DELETERemoveOptional
HEADHeaders onlyNo
Status RangeMeaning
1xxInformational
2xxSuccess (200, 201, 204)
3xxRedirect (301, 302, 304)
4xxClient error (400, 401, 403, 404, 429)
5xxServer error (500, 502, 503)

HTTP is stateless; cookies and tokens carry state.


HTTP Request and Response

Request:                          Response:
GET /api/users HTTP/1.1           HTTP/1.1 200 OK
Host: api.example.com             Content-Type: application/json
User-Agent: curl/8.0              Cache-Control: max-age=60
Accept: application/json          Content-Length: 42
                                  ETag: "abc123"
                                  {"id": 1, "name": "Rohan"}
HeaderDirectionPurpose
HostRequestTarget domain
User-AgentRequestClient identity
AcceptRequestAccepted formats
AuthorizationRequestCredentials
Content-TypeBothBody format
Cache-ControlBothCaching policy
ETagResponseValidator
Set-CookieResponseClient state

Browser Architecture

ComponentFunction
UIAddress bar, tabs, bookmarks
NetworkHTTP/HTTPS, DNS, TLS
RendererHTML parsing, CSS layout, paint
JavaScript engineExecutes JS (V8, SpiderMonkey)
StorageCookies, localStorage, IndexedDB
Rendering StepMeaning
ParseHTML โ†’ DOM
StyleCSS โ†’ CSSOM
LayoutCompute geometry
PaintRasterize pixels
CompositeCombine layers

DevTools Panels

PanelUse
NetworkRequests, headers, timing, status
ElementsDOM and CSS inspection
ConsoleJS execution and logs
SourcesBreakpoints and debugging
ApplicationCookies, storage, service workers
PerformanceRender and JS profiling
SecurityTLS certificate details
Network Tab DetailMeaning
StatusHTTP code
TimingDNS, connect, TLS, TTFB, download
HeadersRequest and response
PreviewParsed response
ResponseRaw body
WaterfallChronological chart

The Full Request Journey

Type URL
   โ”‚
   โ–ผ
DNS lookup (cache โ†’ resolver โ†’ root โ†’ TLD โ†’ authoritative)
   โ”‚
   โ–ผ
TCP connection (SYN โ†’ SYN-ACK โ†’ ACK)
   โ”‚
   โ–ผ
TLS handshake (client hello โ†’ server hello โ†’ keys โ†’ cert)
   โ”‚
   โ–ผ
HTTP request sent
   โ”‚
   โ–ผ
Server processes โ†’ response
   โ”‚
   โ–ผ
Browser parses HTML โ†’ fetches subresources
   โ”‚
   โ–ผ
Render: parse โ†’ style โ†’ layout โ†’ paint โ†’ composite
   โ”‚
   โ–ผ
Page interactive

Port Numbers

PortService
20/21FTP
22SSH
53DNS
80HTTP
443HTTPS
3306MySQL
5432PostgreSQL
6379Redis

Common Pitfalls

PitfallFix
Confusing internet and webWeb is one service on the internet
Confusing IP and MACIP routes across networks; MAC is local
Fragment sent to serverFragments stay client-side
Assuming DNS is instantTTL and caching control propagation
Treating HTTP as statefulState lives in cookies/tokens

Summary

AreaKey Takeaway
Internet vs WebInfrastructure vs HTTP-based service
IP vs MACNetwork routing vs local delivery
DomainHuman name; DNS maps to IP
URL/URIURI identifies; URL locates
HostingShared โ†’ VPS โ†’ dedicated โ†’ cloud
DNSRecursive resolution with caching
HTTPStateless request/response protocol
Request/ResponseHeaders carry metadata; body carries data
BrowserOrchestrates network, rendering, and JS
DevToolsNetwork panel exposes the full lifecycle

This cheatsheet is a map, not a textbook. Each row can expand into a chapter of its own. Use it to keep the layers in order: physical network โ†’ addressing โ†’ naming โ†’ protocol โ†’ client โ†’ tools. The request lifecycle is the thread that connects all ten topics, and the DevTools Network panel is where that thread becomes visible.

Was this helpful?


Stop using slow, ad-bloated tool sites! ๐Ÿคฎ

๐Ÿ”Ž Search “KandZ Tools” on Google to use many professional utilities for free.

KandZ.me is the ultimate minimalist hub for:
โœ… Finance (Mortgage, Interest, Inflation)
โœ… Tech (Base64, JSON, Dev Suite, IP)
โœ… Health (BMI, BMR, TDEE)
โœ… Productivity (Timer, Workspace, QR)

โšก๏ธ Fast & Private
๐Ÿ”’ No data leaves your device
๐Ÿ’Ž 100% Free

๐Ÿ”— Use it now: https://tools.kandz.me
๐Ÿ”– Bookmark itโ€”youโ€™ll need it later!