In the current work of information technology, computers are dumb devices if they cannot communicate over the network. A normal person would never know the details behind the way the data move from their computer to another computer somewhere on the network or internet. They would never know how their application on their browser or their computer talk to the server on the internet to grab the necessary data.

Fundamentally most of the network engineers use OSI model as the reference point of understanding how computer systems communicate over the network. The OSI model is a conceptual mode and not a physical implementation and it is a way of thinking how data travels across the network and also assists us in network troubleshooting.

Let us see an example of what happens when you open a web browser with the address https://www.google.com on a company network.

As soon as you enter https://www.google.com your computer would try to convert that web address to an ip address that would require it to know the DNS server ip address you are referring to. Your company network might have an internal DNS address which would be referred to find the public ip address of dns website. 

If it cannot find the ip address after using the internal dns it will most probably look at the  dns forwarder option on Windows server which will be public dns server like google (8.8.8.8 and 8.8.4.4) ,Cloudflare(1.1.1.1 and 1.0.0.1) etc. Sometimes your network settings itself might have a secondary public dns address that your computer might refer to. Once it finds the ip address of google.com for ex: 142.251.186.105, your computer will try to grab the webpage from google server

Once it grabs the ip address our computer will try to reach that server. The computer Ethernet or wireless connection is associated with a router or multilayer switch SVI and that enables it to talk to all other vlans. As the public ip address of the google website is not on our router it will forward that request to the default gateway. The devices sitting on the default gateway would be an edge device like a router or a firewall who would be responsible for forwarding the data to the google server public ip address 

Before the page is viewed on your web browser as we are using HTTPS protocol, the google server might try to prove that we are indeed the right person connecting to the server. Our computer. Our Browser does  a SSL/TLS handshake with the server and they verify that indeed we are talking to the right web server.

The certificate send by the server has the domain name or ip address of the web server as seen in the below image which can be used to identify the fact that we are connecting to the right web address domain