Innomerc Choose your depth. Learn at your own pace.
Understand it
Your browser is a client: it asks another program for information. A server receives requests and sends responses. The internet connects many networks so those messages can travel between devices.
A website can involve several systems. A web service handles the request, application logic decides what to do, and a database stores records. They may share a computer or run on separate machines.
Under the hood
Packets carry data between network interfaces; IP addressing and routing help them reach the destination network. DNS helps resolve names, while protocols such as HTTP define application messages. A successful DNS lookup does not prove that a later service is reachable.
Ports help distinguish transport endpoints. They are not user identities, and a familiar port does not prove traffic is benign. Modern HTTPS can use different transports; diagrams here omit intermediaries such as proxies and CDNs.
Practitioner perspective
During investigation, distinguish name resolution, connection establishment, encrypted transport and application authorization. Each layer has different evidence and failure modes. A browser error alone rarely identifies the failing layer.
Draw the actual trust boundaries and owners before adding controls. A reverse proxy can change the apparent source seen by an application; forwarded identity information needs a trusted configuration.
Watch it work
A fictional, simplified model. Select a component to inspect it, or follow the steps in order.
Explore the system
Browser
The client requests a page.
Read every step without animation
Read a page
- Browser. The client requests a page.
- Application. The service processes the request.
- Response. The browser receives a result.
The request and response cross several layers.
Missing service
- Name found. DNS returns an address.
- Connection fails. The requested service is unavailable.
- No page. A name result did not guarantee an application response.
Test the layer that actually failed.
Attack view
A response failure may be caused by connectivity, name lookup, service state or application policy; it is not automatically an attack.
Defender view
- Learn the normal request path before diagnosing an abnormal one.
- Check each boundary with appropriate evidence rather than guessing from a single symptom.
Common mistakes
- The web is one use of the internet, not the whole internet.
- An IP address alone is not a stable person identifier.
Check your understanding
Active recall: explain this idea in 30 seconds
Your browser is a client: it asks another program for information. A server receives requests and sends responses. The internet connects many networks so those messages can travel between devices.
Now give an example and name one limitation. Revisit the explanation if you get stuck.
Primary sources
Original explanations informed by these specifications and official resources. Source versions and lesson review are separate from product updates.
Content reviewed 2026-09-10. Read the editorial policy.