<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Khansa Mahmood on Medium]]></title>
        <description><![CDATA[Stories by Khansa Mahmood on Medium]]></description>
        <link>https://medium.com/@khansa.mahmood.pro?source=rss-8981bdc96f46------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Yw2hjiFt57OeWapU5NgxGQ.jpeg</url>
            <title>Stories by Khansa Mahmood on Medium</title>
            <link>https://medium.com/@khansa.mahmood.pro?source=rss-8981bdc96f46------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 12:26:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@khansa.mahmood.pro/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[HTTP vs HTTPS: What That Padlock Really Means]]></title>
            <link>https://blog.stackademic.com/http-vs-https-what-that-padlock-really-means-1f7bbd6de31e?source=rss-8981bdc96f46------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f7bbd6de31e</guid>
            <category><![CDATA[students]]></category>
            <category><![CDATA[https]]></category>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Khansa Mahmood]]></dc:creator>
            <pubDate>Mon, 16 Nov 2026 10:07:49 GMT</pubDate>
            <atom:updated>2026-11-16T10:07:49.128Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WWUDAUL3o00V6C46" /><figcaption>Photo by <a href="https://unsplash.com/@tbonz?utm_source=medium&amp;utm_medium=referral">Emmanuel Edward</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Imagine sending two messages to a friend across the city. The first one you write on a postcard and drop in the mail. Every postal worker, sorting machine, and delivery driver who handles it can read what you wrote. One of them could even cross out a line and write something else, and your friend would never know.</p><p>The second message goes into a locked steel box. Only you and your friend have the key. Before the courier hands it over, your friend checks the courier’s official ID to make sure it’s really from you. Anyone along the way can see that a box is being delivered and where it’s going, but nobody can read what’s inside or change it without breaking the lock.</p><p>The postcard is HTTP. The locked box is HTTPS.</p><p>In the last article, What Happens When You Type a URL in Your Browser?, we briefly met TLS, certificates, and the padlock. This time we’ll open the box and look at what HTTPS actually protects, what it doesn’t, and what that little icon in your address bar is really telling you.</p><p><strong><em>Welcome to Part # 7 of my series:<br> “Peer-to-Peer: Networks Made Easy (By a Student, For Students)”</em></strong></p><h4>What Is HTTP?</h4><p>HTTP (HyperText Transfer Protocol) is the language your browser and a web server use to talk to each other. It’s a simple request-and-response conversation:</p><ul><li>Your browser sends a <strong>request</strong>: “Please send me /login.&quot;</li><li>The server sends a <strong>response</strong>: “200 OK, here’s the page.”</li></ul><p>HTTP was designed in the early 1990s for sharing documents between researchers. Security wasn’t part of the plan. By default, everything travels as <strong>plain text</strong>, so anyone who can see the traffic can read it word for word.</p><p>A plain HTTP login might look like this as it crosses the network:</p><pre>textPOST /login HTTP/1.1Host: www.example.com<br>Content-Type: application/x-www-form-urlencoded<br><br>username=khansa&amp;password=MySecret123</pre><p>There’s no scrambling and no hiding. If someone on the same café Wi-Fi is running a packet sniffer (as we covered in How Packet Sniffing Works), they see the password exactly as you typed it.</p><h4>HTTP Is Stateless</h4><p>One more important detail: HTTP is <strong>stateless</strong>. Every request is treated as brand new, and the server doesn’t remember you from one click to the next. To keep you logged in, websites use <strong>cookies</strong>, small pieces of data your browser sends back with every request.</p><p>On plain HTTP those cookies travel in the open too. An attacker who copies your session cookie can often become you on that site without ever knowing your password. This is called <strong>session hijacking</strong>.</p><h4>What Is HTTPS?</h4><p>HTTPS (HyperText Transfer Protocol Secure) is not a different language. It’s the same HTTP conversation, wrapped inside an encrypted tunnel created by <strong>TLS (Transport Layer Security)</strong>.</p><p>You may still hear people call it <strong>SSL</strong>. SSL was the older protocol that TLS replaced, and every version of SSL is now considered broken. The name stuck around (people still say “SSL certificate”), but modern HTTPS uses TLS, ideally TLS 1.3.</p><p>The same login over HTTPS looks something like this to an eavesdropper:</p><pre>text17 03 03 00 4a 8f 2c e1 9b 77 d4 0a 3e 5f c2 91 ...</pre><p>It’s unreadable without the session keys, which only your browser and the server have.</p><h3>The Three Promises of HTTPS</h3><p>HTTPS gives you three protections, and each one maps onto our locked box.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/603/1*i5laDZt8jVgJocRoRBC0uw.png" /><figcaption>Table 1: The three core protections HTTPS provides.</figcaption></figure><p>Most people only think about the first one, but the other two matter just as much. Without integrity, an attacker could inject ads or malware into a page you’re downloading. Without authentication, you could set up a perfectly encrypted connection straight to an attacker.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*J9R06f-3CC5JV1p2" /><figcaption>Photo by <a href="https://unsplash.com/@juzzepo?utm_source=medium&amp;utm_medium=referral">Juzzepo</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>How HTTPS Works: The TLS Handshake</h3><p>Before any HTTP data is sent, your browser and the server run a TLS handshake. In the URL article we covered the steps briefly. Here’s what’s going on underneath.</p><h4>Two Kinds of Encryption Working Together</h4><p>TLS uses two types of encryption, each for what it does best:</p><ul><li><strong>Asymmetric encryption (public-key cryptography):</strong> Uses a pair of keys, a public key anyone can see and a private key only the server holds. It’s great for proving identity and agreeing on secrets safely, but it’s slow.</li><li><strong>Symmetric encryption:</strong> Uses one shared key for both locking and unlocking. It’s very fast, which makes it ideal for encrypting the actual web traffic.</li></ul><p>The handshake uses the slow, clever method to safely agree on a key for the fast method.</p><h4>The Handshake in Plain Terms (TLS 1.3)</h4><ol><li><strong>Client Hello:</strong> Your browser says, “Here are the encryption methods I support, and here’s my half of a key exchange.”</li><li><strong>Server Hello:</strong> The server picks a method and sends its half of the key exchange.</li><li><strong>Certificate:</strong> The server presents its digital certificate and proves it holds the matching private key.</li><li><strong>Verification:</strong> Your browser checks the certificate (more on that below).</li><li><strong>Session keys:</strong> Both sides combine their halves to calculate the same secret session keys. The keys themselves never cross the network.</li><li><strong>Encrypted conversation:</strong> From here on, every HTTP request and response is encrypted with those keys.</li></ol><p>The key exchange works like mixing paint. You each start with a shared base colour, add your own secret colour, and swap the mixtures. Each of you then adds your secret colour again, and you both end up with the same final colour. Someone watching only ever sees the mixtures, and they can’t “un-mix” them to find your secret colours.</p><p>TLS 1.3 does all of this in a single round trip, so HTTPS is barely slower than HTTP. Thanks to newer protocols like HTTP/2 and HTTP/3, which browsers only use over encrypted connections, HTTPS sites are often faster in practice.</p><h4>Certificates: The Website’s ID Card</h4><p>Encryption alone isn’t enough. You also need to know who you’re encrypting to. That’s the job of the <strong>digital certificate</strong>.</p><p>A certificate contains:</p><ul><li>The <strong>domain name(s)</strong> it’s valid for, such as <a href="http://www.example.com/">www.example.com</a></li><li>The website’s <strong>public key</strong></li><li>The <strong>issuer</strong>, the Certificate Authority that vouches for it</li><li><strong>Validity dates</strong>: when it starts and when it expires</li><li>A <strong>digital signature</strong> from the issuer, proving the certificate hasn’t been forged</li></ul><h4>The Chain of Trust</h4><p>Why should your browser believe a certificate? Because of a <strong>chain of trust</strong>:</p><ol><li>Your operating system and browser come with a built-in list of trusted <strong>root Certificate Authorities (CAs)</strong>.</li><li>Root CAs sign <strong>intermediate certificates</strong>.</li><li>Intermediates sign the website’s own certificate (the <strong>leaf certificate</strong>).</li></ol><p>Your browser follows that chain from the website back up to a root it already trusts. If every signature checks out, the domain matches, and nothing has expired or been revoked, the connection goes ahead. If anything fails, you get the full-page “Your connection is not private” warning.</p><p>It’s like a passport. The border officer doesn’t know you personally, but they trust the government that issued your passport, and they can check that it’s genuine and not expired.</p><h4>Types of Certificates</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/648/1*FqsYWDDn5q2xcFX6zgiMFA.png" /><figcaption>Table 2: The three main types of TLS certificates.</figcaption></figure><p>All three provide the same strength of encryption. The difference is how much the CA checked about who is behind the site. Browsers used to show EV certificates with a green company name in the address bar, but they dropped that because most users didn’t notice or understand it.</p><h4>Certificates Are Getting Shorter Lives</h4><p>Certificates don’t last forever, and their lifetimes are shrinking quickly. Under rules adopted by the CA/Browser Forum, publicly trusted certificates issued since March 15, 2026 can be valid for at most 200 days. That limit drops to 100 days in March 2027 and 47 days in March 2029. The goal is to limit the damage if a key is stolen, and in practice it means websites need automated renewal.sans+1</p><p>Free, automated certificate authorities like Let’s Encrypt are a big reason HTTPS went from a luxury for banks to the default for almost every website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wz3Tbo1_sQzymlu4" /><figcaption>Photo by <a href="https://unsplash.com/@flyd2069?utm_source=medium&amp;utm_medium=referral">FlyD</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>So, What Does the Padlock Really Mean?</h3><p>Here’s the heart of the matter. The padlock means:</p><blockquote><em>Your connection to this domain is encrypted, and the server proved it controls this domain name.</em></blockquote><p>That’s it. It does <strong>not</strong> mean:</p><ul><li>The website is honest or legitimate</li><li>The company behind it is real</li><li>The site is free of malware</li><li>Your data is safe once it reaches the server</li><li>The site won’t misuse what you give it</li></ul><p>Back to our analogy: the locked box guarantees that nobody tampered with the package on the way. It says nothing about whether the person you’re sending it to is trustworthy. If you’ve been tricked into sending your box to a scammer, the lock just makes sure nobody else can read your bank details on the way to the scammer.</p><h4>Phishing Sites Have Padlocks Too</h4><p>Getting a free DV certificate only requires proving you control a domain. A criminal who registers paypa1-secure-login.com can get a valid certificate for it in minutes. Today a large share of phishing sites use HTTPS, so the padlock looks exactly the same as it does on the real site.</p><h4>Why Chrome Removed the Padlock</h4><p>This confusion was so common that Google changed the icon. A 2021 Google study found that only 11% of participants understood what the padlock actually meant. Starting with Chrome 117 in 2023, Chrome replaced the padlock with a neutral “tune” icon (two small sliders). Google said the change was meant to stop people linking the icon with trustworthiness and to stress that security should be the default. Clicking it still shows the connection status and certificate.</p><p>In other words, the browser now treats HTTPS as normal and saves its warnings for when something is wrong.</p><h4>What HTTPS Hides, and What It Doesn’t</h4><p>Even with HTTPS, some information is still visible to anyone watching the network, such as your Wi-Fi provider, your ISP, or a sniffer on the same network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/483/1*7_QgGITt4lDjF2yf1IOgvQ.png" /><figcaption>Table 3: What an observer can and cannot see on an HTTPS connection.</figcaption></figure><p>So on HTTPS, someone watching knows you visited www.example-bank.com, but not which pages you opened or what you typed. Encrypted DNS (DNS over HTTPS) and a newer TLS feature called Encrypted Client Hello (ECH) can hide the domain name too, though ECH isn&#39;t used everywhere yet. A VPN hides even more from your local network by tunnelling everything to the VPN provider, which then sees what your ISP would have seen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*N9OfnUlvhpIw3oZg" /><figcaption>Photo by <a href="https://unsplash.com/@markusspiske?utm_source=medium&amp;utm_medium=referral">Markus Spiske</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Common Weak Spots Even With HTTPS</h3><h4>Mixed Content</h4><p>A page loaded over HTTPS that pulls in some resources (images, scripts, stylesheets) over plain HTTP has <strong>mixed content</strong>. A script loaded over HTTP could be swapped out by an attacker and take over the whole “secure” page. Modern browsers block insecure scripts outright and upgrade or block insecure images.</p><h4>SSL Stripping</h4><p>If you type example.com without https://, the very first request might go over HTTP before the site redirects you to HTTPS. An attacker in the middle (for example on fake café Wi-Fi) can intercept that first request and keep you on HTTP, while talking HTTPS to the real site. You&#39;d see the page normally, just without the secure connection.</p><p>Two defences close this gap:</p><ul><li><strong>HSTS (HTTP Strict Transport Security):</strong> A site tells your browser, “Only ever contact me over HTTPS.” The browser remembers and refuses plain HTTP from then on. Some sites are on a built-in <strong>HSTS preload list</strong>, so they’re protected from the very first visit.</li><li><strong>HTTPS-first browsing:</strong> Browsers now try HTTPS automatically before anything else.</li></ul><p>On that second point, Chrome made a major change this year. With Chrome 154, rolling out in October 2026, the “Always Use Secure Connections” setting is on by default. Chrome tries HTTPS first for public sites and asks for permission before loading a site that only works over HTTP. Private addresses, such as your router’s admin page at 192.168.1.1, are excluded from the warning by default.blog+1</p><h4>Clicking Through Certificate Warnings</h4><p>A certificate warning means the browser could not confirm who it’s talking to. It might be a harmless expired certificate, or it might be an attacker intercepting your connection. If you click “Proceed anyway,” you throw away the authentication promise of HTTPS. On public Wi-Fi especially, don’t.</p><h4>Problems on the Server or Your Device</h4><p>HTTPS only protects data while it’s travelling. It doesn’t help if the website itself is hacked, if it stores passwords badly, or if your own computer has malware or a malicious browser extension. Those happen at either end of the locked box, not along the way.</p><h4>HTTP vs HTTPS Side by Side</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/647/1*HEi_0jEmECh1mSWQM65kkw.png" /><figcaption>Table 4: A side-by-side comparison of HTTP and HTTPS.</figcaption></figure><h4>Try It Yourself</h4><ul><li><strong>Inspect a certificate:</strong> On any HTTPS site, click the icon to the left of the address, choose the connection or security option, and open the certificate details. Check who issued it, which domains it covers, and when it expires.</li><li><strong>See the chain of trust:</strong> In the certificate viewer, look at the hierarchy tab to see the leaf, intermediate, and root certificates.</li><li><strong>Read the handshake:</strong> Run curl -v &lt;https://example.com&gt; in a terminal. You&#39;ll see the TLS version, the chosen cipher, and the certificate details before the HTTP response.</li><li><strong>Compare in Wireshark:</strong> Capture traffic while visiting a plain HTTP test site and then an HTTPS site. Use the filter http to see readable requests, then tls to see only encrypted &quot;Application Data.&quot; It&#39;s the clearest way to see the difference between a postcard and a locked box.</li><li><strong>Test a site’s configuration:</strong> Free tools like Qualys SSL Labs grade a website’s HTTPS setup and flag weak settings.</li></ul><p>Only capture traffic on networks and devices you own or have permission to monitor.</p><h4>Quick Safety Checklist</h4><ul><li>Make sure the domain is spelled exactly right before typing a password, rather than relying on the icon.</li><li>Never click past a certificate warning on public Wi-Fi.</li><li>Keep “Always use secure connections” turned on in your browser.</li><li>Be wary of links in emails and messages. Type important addresses yourself or use bookmarks.</li><li>Use a VPN on networks you don’t trust.</li><li>If you run a website, use HTTPS everywhere, turn on HSTS, fix mixed content, and automate certificate renewal.</li></ul><h4>Final Thoughts</h4><p>HTTP is a postcard: simple, fast, and readable by anyone who handles it. HTTPS puts that same message in a locked, tamper-evident box and checks the courier’s ID before delivery. It keeps your data private, keeps it intact, and makes sure you’re connected to the domain you asked for.</p><p>But the lock is about the journey, not the destination. The padlock, or Chrome’s tune icon, tells you the connection is secure. It can’t tell you whether the person at the other end deserves your trust. That judgement is still up to you, and it starts with reading the domain name carefully.</p><p>So the next time you see that little icon in the address bar, remember what it really means: nobody can read your mail on the way. Just make sure you’ve addressed it to the right person.</p><p><strong><em>Previously in the series:</em></strong></p><p><a href="https://meetcyber.net/what-happens-when-you-type-a-url-in-your-browser-24ca5ccfe484">What Happens When You Type a URL in Your Browser?</a></p><p><strong><em>Next in the series:</em></strong></p><blockquote><strong><em>“MAC Addresses and ARP: How Devices Find Each Other on a Network..”</em></strong></blockquote><p><em>— Khansa Mahmood.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f7bbd6de31e" width="1" height="1" alt=""><hr><p><a href="https://blog.stackademic.com/http-vs-https-what-that-padlock-really-means-1f7bbd6de31e">HTTP vs HTTPS: What That Padlock Really Means</a> was originally published in <a href="https://blog.stackademic.com/">Stackademic</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Happens When You Type a URL in Your Browser?]]></title>
            <link>https://meetcyber.net/what-happens-when-you-type-a-url-in-your-browser-24ca5ccfe484?source=rss-8981bdc96f46------2</link>
            <guid isPermaLink="false">https://medium.com/p/24ca5ccfe484</guid>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[students]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[beginners-guide]]></category>
            <dc:creator><![CDATA[Khansa Mahmood]]></dc:creator>
            <pubDate>Sun, 15 Nov 2026 21:33:03 GMT</pubDate>
            <atom:updated>2026-11-15T21:33:03.650Z</atom:updated>
            <content:encoded><![CDATA[<h4>(Simple guide for students)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*F8sKL5rrzEbPmrWH" /><figcaption>Photo by <a href="https://unsplash.com/@ilyapavlov?utm_source=medium&amp;utm_medium=referral">Ilya Pavlov</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Imagine you want to visit a friend you’ve never visited before. You know their name, but not where they live. So you check your own notebook first. When the address isn’t there, you ask a neighbour, who sends you to the local post office, who sends you to the city records office, who finally gives you the exact street address. You drive over and knock, and your friend checks who you are through the peephole before opening the door. Then you ask for what you came for, and they hand it to you piece by piece.</p><p>That whole trip, from knowing only a name to standing in the right living room, happens every time you type a URL and press Enter. It usually takes less than a second.</p><p>In our last article, How Data Travels on the Internet, we looked at packets, bits, and protocols. This time we’ll follow one URL from the keyboard to a finished webpage and look closely at each stop.</p><p><strong><em>Welcome to Part # 6 of my series:<br> “Peer-to-Peer: Networks Made Easy (By a Student, For Students)”</em></strong></p><h4>Step 0: Reading the URL</h4><p>Before anything goes over the network, the browser has to work out what you typed. A URL (Uniform Resource Locator) is an address with several parts:</p><pre>https://www.example.com:443/blog/article?id=42#comments*</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pwYunyDXn_OMMseuHyXyzA.png" /><figcaption>The parts of a URL, using <a href="https://www.example.com/blog/article?id=42#comments">https://www.example.com:443/blog/article?id=42#comments</a> as an example.</figcaption></figure><p>The browser also makes a few quick checks:</p><ul><li><strong>Is this a URL or a search?</strong> If you type cute cat videos, the browser sends it to your default search engine. If you type example.com, it treats it as an address.</li><li><strong>Which scheme should it use?</strong> If you leave out the scheme, modern browsers try HTTPS first. If a site is on the browser’s HSTS list (HTTP Strict Transport Security), the browser will only connect to it over HTTPS.</li><li><strong>Is the name safe?</strong> Browsers convert international characters to a standard form (called Punycode) and check the address against lists of known phishing and malware sites.</li></ul><h4>Step 1: Finding the Address (DNS Lookup)</h4><p>Computers don’t route traffic by names like www.example.com. They need an IP address. The Domain Name System (DNS) turns the name into a number, and it checks the nearest places first.</p><p><strong>Checking the Local Notebooks:</strong></p><ol><li><strong>Browser cache:</strong> Has the browser looked up this name recently?</li><li><strong>Operating system cache:</strong> Has any app on this device looked it up?</li><li><strong>Hosts file:</strong> A small local file that can map names to IPs by hand.</li><li><strong>Router cache:</strong> Your home router often keeps its own short-term cache.</li></ol><p>If any of these has a fresh answer, the lookup finishes in a few milliseconds.</p><p><strong>Asking the Directory Chain:</strong></p><p>If no cache has the answer, the request goes to a <strong>recursive resolver</strong>. This is usually run by your ISP, or by a public service such as Google (8.8.8.8) or Cloudflare (1.1.1.1). The resolver does the asking for you:</p><ol><li><strong>Root servers:</strong> “I don’t know www.example.com, but the .com servers will. Here&#39;s where they are.&quot;</li><li><strong>TLD (top-level domain) servers:</strong> “I don’t know the exact address, but example.com&#39;s authoritative name server does. Here it is.&quot;</li><li><strong>Authoritative name server:</strong> “www.example.com is at 203.0.113.10.&quot;</li></ol><p>The resolver passes the answer back to your computer, and every cache along the way saves it for a set time called the TTL (time to live). That’s why the second visit to a site feels quicker.</p><p>It’s the same as our friend’s address: check your own notebook, then the neighbour, then the post office, then city records.</p><h4>Step 2: Getting Out of the House (ARP and the Gateway)</h4><p>Your computer now has the server’s IP address, but the server is on a different network, so the packets have to go through your router (the default gateway) first.</p><p>On the local network, devices talk using hardware MAC addresses, not IP addresses. So your computer uses <strong>ARP</strong> (Address Resolution Protocol) to shout across the local network: “Who has the router’s IP? Tell me your MAC address.” The router answers, and your computer can now send packets out of the house.</p><p>(ARP is also the protocol attackers abuse in ARP spoofing, which we covered in How Packet Sniffing Works.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_gdwN0gVkEOXSc_o" /><figcaption>Photo by <a href="https://unsplash.com/@charlesdeluvio?utm_source=medium&amp;utm_medium=referral">charlesdeluvio</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Step 3: Knocking on the Door (TCP Handshake)</h4><p>Before sending a request, your computer and the server set up a reliable connection with TCP’s three-way handshake:</p><ol><li><strong>SYN:</strong> “Hi, I’d like to connect.”</li><li><strong>SYN-ACK:</strong> “Hi, I’m ready.”</li><li><strong>ACK:</strong> “Great, let’s begin.”</li></ol><p>The connection goes to the port from the URL, which is 443 for HTTPS or 80 for plain HTTP.</p><p><strong>A modern twist:</strong> many large sites now support <strong>HTTP/3</strong>, which runs over a protocol called <strong>QUIC</strong> on top of UDP instead of TCP. QUIC combines the connection setup and the encryption setup into fewer round trips, so pages start loading sooner, especially on mobile networks.</p><h4>Step 4: Checking Through the Peephole (TLS Handshake)</h4><p>For HTTPS sites, the next step is a <strong>TLS handshake</strong>. This is how your browser and the server agree to talk privately and how the browser confirms the server is who it says it is.</p><p>In simple terms:</p><ol><li><strong>Client Hello:</strong> Your browser lists the encryption methods it supports and sends some key material.</li><li><strong>Server Hello and certificate:</strong> The server picks a method, sends its own key material, and presents its <strong>digital certificate</strong>, a kind of ID card for the website.</li><li><strong>Certificate check:</strong> Your browser confirms that:<br>- the certificate was issued by a trusted <strong>Certificate Authority (CA)</strong>,<br>- it matches the domain you typed,<br>- it hasn’t expired or been revoked.</li></ol><p>4.<strong> Shared keys:</strong> Both sides use the exchanged material to create the same session keys. They never send those keys over the network.</p><p>From here on, everything is encrypted. With TLS 1.3, the current standard, this takes just one round trip.</p><p>If the certificate check fails, you’ll see a full-page warning such as “Your connection is not private.” Don’t click past it unless you know exactly why it’s showing. It can mean someone is pretending to be the site.</p><p>The padlock in the address bar means the connection is encrypted and the certificate matches the domain. It doesn’t mean the site itself is trustworthy, since phishing sites can have valid certificates too.</p><h4>Step 5: Asking for What You Came For (HTTP Request)</h4><p>With a secure connection open, the browser sends an <strong>HTTP request</strong>. A simplified version looks like this:</p><pre>textGET /blog/article?id=42 HTTP/1.1Host: www.example.com<br>User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) ...<br>Accept: text/html<br>Accept-Language: en-US<br>Cookie: session=abc123</pre><ul><li><strong>GET</strong> is the method. It means “please send me this.” Other methods include POST (send data, such as a form), PUT, and DELETE.</li><li><strong>Headers</strong> give extra context: which site you want, what browser you’re using, what formats and language you accept, and any cookies the site set earlier.</li></ul><h4>Step 6: Behind the Server’s Door</h4><p>The request often doesn’t go straight to a single machine. On a large site it may pass through:</p><ul><li><strong>A CDN (Content Delivery Network):</strong> A copy of the site stored on servers close to you. If the CDN already has the page, it answers right away.</li><li><strong>A load balancer:</strong> Spreads requests across many servers so none gets overloaded.</li><li><strong>A web application firewall (WAF):</strong> Filters out malicious requests.</li><li><strong>The web server and application:</strong> Runs the site’s code, maybe queries a database, and builds the response.</li></ul><h4>Step 7: The Server Responds (HTTP Response)</h4><p>The server sends back a response with a <strong>status code</strong>, headers, and the content:</p><pre>textHTTP/1.1 200 OKContent-Type: text/html; charset=UTF-8<br>Cache-Control: max-age=3600<br>Set-Cookie: session=abc123; Secure; HttpOnly<br><br>&lt;!DOCTYPE html&gt;<br>&lt;html&gt; ... &lt;/html&gt;</pre><p>Status codes are grouped by their first digit:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4hs6362H4uA5iRnK35AHPA.png" /><figcaption><em>HTTP status code categories and common examples.</em></figcaption></figure><p>If the server answers with a redirect (for example, from example.com to www.example.com), the browser follows it and repeats the steps above for the new address.</p><h4>Step 8: Building the Page (Rendering)</h4><p>The browser now has a file of HTML text, and it has to turn that text into the page you see. This is the rendering process:</p><ol><li><strong>Parse HTML into the DOM:</strong> The browser reads the HTML and builds the <strong>DOM (Document Object Model)</strong>, a tree of every element on the page.</li><li><strong>Find more resources:</strong> While parsing, it finds links to CSS files, JavaScript, images, and fonts, and requests each one. Many of these repeat the DNS, connection, and request steps for other servers.</li><li><strong>Parse CSS into the CSSOM:</strong> Style rules are built into their own tree.</li><li><strong>Run JavaScript:</strong> Scripts can change the DOM and CSSOM, load more data, and add interactivity. Scripts that aren’t marked async or defer can pause parsing until they finish.</li><li><strong>Build the render tree:</strong> The DOM and CSSOM are combined into a list of only the visible elements and their styles.</li><li><strong>Layout:</strong> The browser works out the exact size and position of every element.</li><li><strong>Paint and composite:</strong> It fills in the pixels (text, colours, images, borders) and stacks the layers in the right order on screen.</li></ol><p>Going back to our friend: this is them unpacking the boxes and setting up the room exactly as it’s meant to look.</p><h4>Step 9: After the Page Loads</h4><p>The work doesn’t stop when the page appears:</p><ul><li><strong>Connections stay open</strong> (keep-alive) so the next request is faster.</li><li><strong>Resources are cached</strong> according to the server’s Cache-Control headers, so the next visit loads from your device.</li><li><strong>JavaScript keeps running</strong> to handle clicks, load new content, and send analytics.</li><li><strong>Cookies are stored</strong> to keep you logged in or remember your preferences.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HS-6oV185IjJIdcL" /><figcaption>Photo by <a href="https://unsplash.com/@freestocks?utm_source=medium&amp;utm_medium=referral">freestocks</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>The Whole Journey at a Glance</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CkkrA9NwhvdUHP6P17d0KA.png" /><figcaption>Summary of each step from typing a URL to seeing the page, with the main protocol or tool involved.</figcaption></figure><h4>Where Security Comes In</h4><p>Almost every step can be targeted by an attacker, which is why this journey matters so much in cybersecurity:</p><ul><li><strong>Typosquatting and phishing:</strong> Look-alike URLs such as examp1e.com or paypa1.com trick people at Step 0.</li><li><strong>DNS spoofing and cache poisoning:</strong> An attacker sends a fake DNS answer, so you end up at the wrong server. DNSSEC and encrypted DNS (DNS over HTTPS or DNS over TLS) help defend against this.</li><li><strong>ARP spoofing:</strong> An attacker on the local network places themselves between you and the router.</li><li><strong>Man-in-the-middle attacks:</strong> Someone tries to intercept the connection. TLS certificate checks are the main defence.</li><li><strong>Downgrade attacks:</strong> An attacker forces a connection onto plain HTTP. HSTS prevents this.</li><li><strong>Malicious scripts:</strong> Cross-site scripting (XSS) injects harmful JavaScript into pages during rendering.</li></ul><p><strong>Simple habits that help:</strong></p><ul><li>Check the domain carefully before entering passwords.</li><li>Never ignore certificate warnings.</li><li>Use a browser that keeps itself updated.</li><li>Turn on encrypted DNS in your browser or operating system settings.</li><li>Use a VPN on public Wi-Fi.</li></ul><h4>Try It Yourself</h4><p>You can watch this whole process on your own computer:</p><ul><li><strong>Browser DevTools:</strong> Press F12, open the <strong>Network</strong> tab, and reload a page. Each request shows its timing broken into DNS lookup, initial connection, SSL/TLS, waiting for the server, and content download.</li><li><strong>nslookup example.com</strong> or <strong>dig example.com</strong> in a terminal shows the DNS answer.</li><li><strong>curl -v &lt;https://example.com&gt;</strong> prints the TLS handshake details and the raw HTTP request and response headers.</li><li><strong>Wireshark</strong> (from our packet sniffing guide) lets you capture the DNS query, the TCP handshake, and the TLS “Client Hello” packet by packet.</li></ul><h4>Final Thoughts</h4><p>Typing a URL feels like one action, but it starts a chain of work: the browser reads the address, DNS looks up the IP, ARP finds the way out of the local network, TCP opens a connection, TLS checks the server’s identity and encrypts the channel, HTTP asks for the page, and the browser turns code into pixels. All of this happens in about the time it takes to blink.</p><p>Back to our friend: you started with only a name. A chain of directories gave you an address, roads took you to the door, a quick ID check got you inside, and your friend handed over what you came for. The next time a page loads instantly, you’ll know how much happened in that second, and where along the way someone could try to interfere.</p><p><strong><em>Previously in the series:</em></strong></p><p><a href="https://blog.stackademic.com/how-packet-sniffing-works-38d8fa9e6c72?sharedUserId=khansa.mahmood.pro">How Packet Sniffing Works</a></p><p><strong><em>Next in the series:</em></strong></p><blockquote><strong>“<em>HTTP vs HTTPS: What That Padlock Really Means.</em>”</strong></blockquote><p><strong><em>— Khansa Mahmood</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24ca5ccfe484" width="1" height="1" alt=""><hr><p><a href="https://meetcyber.net/what-happens-when-you-type-a-url-in-your-browser-24ca5ccfe484">What Happens When You Type a URL in Your Browser?</a> was originally published in <a href="https://meetcyber.net/">MeetCyber</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Data Travels on the Internet]]></title>
            <link>https://meetcyber.net/how-data-travels-on-the-internet-8be88452eab4?source=rss-8981bdc96f46------2</link>
            <guid isPermaLink="false">https://medium.com/p/8be88452eab4</guid>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[network]]></category>
            <category><![CDATA[computer-security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[students]]></category>
            <dc:creator><![CDATA[Khansa Mahmood]]></dc:creator>
            <pubDate>Sun, 08 Nov 2026 15:10:23 GMT</pubDate>
            <atom:updated>2026-11-08T19:53:59.621Z</atom:updated>
            <content:encoded><![CDATA[<h4>(Packets, Bits &amp; Protocols)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kKUK5bEAXxxG5TP0" /><figcaption>Photo by <a href="https://unsplash.com/@markuswinkler?utm_source=medium&amp;utm_medium=referral">Markus Winkler</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Imagine you want to send a 500-page book to a friend on the other side of the world. Instead of shipping it in one heavy box, you tear out each page, put it in its own envelope, number it, write your friend’s address on the front, and drop all 500 envelopes into the postal system. Some go by plane, some by truck, some through different cities altogether. Some arrive early, some arrive late, and one or two might get lost and need to be sent again. Your friend collects them all, sorts them by number, and puts the book back together.</p><p>It sounds chaotic, but that’s roughly how every message, photo, video, and webpage moves across the internet, millions of times per second, usually in well under a second.</p><p>Let’s open the envelopes and see how it works.</p><p><strong><em>Welcome to Part # 4 of my series<br>“Peer-to-Peer: Networks Made Easy (By a Student, For Students)”</em></strong></p><h4>Starting Small: Bits and Bytes</h4><p>At the most basic level, computers understand only two states: on and off. These are represented as 1 and 0, and each one is called a bit (short for binary digit).</p><p>A single bit can’t say much, so bits are grouped together:</p><ul><li><strong>8 bits = 1 byte.</strong> One byte can represent a single character, such as the letter “A” (01000001).</li><li><strong>1,024 bytes ≈ 1 kilobyte (KB)</strong>, roughly a short paragraph of text.</li><li><strong>1,024 KB ≈ 1 megabyte (MB)</strong>, roughly a high-quality photo.</li><li><strong>1,024 MB ≈ 1 gigabyte (GB)</strong>, roughly an hour of HD video.</li></ul><p>Everything you send online, whether a text, an emoji, or a 4K movie, is ultimately converted into a long string of 1s and 0s.</p><p>But how do bits physically travel? It depends on the medium:</p><ul><li><strong>Copper cables (Ethernet)</strong> carry bits as electrical pulses.</li><li><strong>Fiber-optic cables</strong> carry bits as flashes of light, which is extremely fast and works over long distances.</li><li><strong>Wi-Fi and mobile networks</strong> carry bits as radio waves.</li></ul><p>A 1 might be a pulse of light and a 0 the absence of one. Strung together billions of times a second, these signals become your Netflix stream.</p><h4>Why Data Is Broken Into Packets</h4><p>Sending data as one giant, continuous stream would cause serious problems. If a single error occurred halfway through a large file, the entire thing would have to be resent. And while one person’s huge download occupied the line, nobody else could use it.</p><p>So data is split into small, manageable pieces called packets. This approach, called packet switching, is the foundation of the internet. It has three big advantages:</p><ul><li><strong>Efficiency:</strong> Many users can share the same network lines, with their packets interleaved like cars merging on a highway.</li><li><strong>Reliability:</strong> If a packet is lost or damaged, only that small piece needs to be resent.</li><li><strong>Flexibility:</strong> Packets can take different routes. If one path is congested or broken, traffic flows around it.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zThI-HPAHjIWzMg-" /><figcaption>Photo by <a href="https://unsplash.com/@markusspiske?utm_source=medium&amp;utm_medium=referral">Markus Spiske</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>The Anatomy of a Packet</h4><p>Just like the envelopes in our book example, every packet has a structure:</p><ul><li><strong>Header:</strong> The “outside of the envelope.” It contains the source address, the destination address, the protocol being used, a sequence number (so packets can be reassembled in order), and a time-to-live (TTL) value that stops lost packets from circulating forever.</li><li><strong>Payload:</strong> The actual piece of data, such as a fragment of a webpage, part of an image, or a few words of a chat message.</li><li><strong>Trailer (in some protocols):</strong> Error-checking information that lets the receiver confirm the data arrived intact.</li></ul><p>A typical packet on most networks carries up to about 1,500 bytes. That means a single 3 MB photo might be split into roughly 2,000 packets.</p><h4>Protocols: The Rules of the Road</h4><p>If everyone mailed letters in their own made-up format, the postal system would collapse. The internet works because every device follows agreed-upon rules called protocols. A protocol defines how data is formatted, addressed, sent, received, and acknowledged.</p><p>There are dozens of protocols, each handling a specific job. Here are the ones you’ll hear about most:</p><ul><li><strong>IP (Internet Protocol):</strong> Handles addressing and routing. Every device online has an IP address, such as 192.168.1.10 (IPv4) or 2001:db8::1 (IPv6). IP’s job is to get packets to the right destination.</li><li><strong>TCP (Transmission Control Protocol):</strong> Makes delivery reliable. It numbers packets, confirms they arrived, resends missing ones, and puts them back in order. It’s used for websites, email, and file downloads.</li><li><strong>UDP (User Datagram Protocol):</strong> A faster, lighter alternative to TCP. It sends packets without checking that they arrived. It’s used for video calls, online gaming, and live streaming, where speed matters more than perfection.</li><li><strong>HTTP/HTTPS:</strong> The language of the web. Your browser uses it to request pages from servers. HTTPS is the encrypted version.</li><li><strong>DNS (Domain Name System):</strong> The internet’s phone book. It translates names like <a href="http://google.com/">google.com</a> into IP addresses.</li><li><strong>Others:</strong> SMTP, IMAP, and POP3 handle email. FTP and SFTP handle file transfers. DHCP automatically gives your device an IP address when it joins a network.</li></ul><h4>TCP vs. UDP in Plain Terms</h4><p>A helpful way to picture the difference:</p><ul><li><strong>TCP is like a registered letter.</strong> You get confirmation it arrived, and if it didn’t, it’s sent again. It’s reliable but slightly slower.</li><li><strong>UDP is like shouting across a room.</strong> It’s fast and direct, but if someone misses a word, you just keep talking.</li></ul><p>That’s why a video call might briefly glitch or freeze (UDP drops a few packets and moves on), while a downloaded file is always complete and correct (TCP makes sure of it).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4XmUlRC69Gdm_mNO" /><figcaption>Photo by <a href="https://unsplash.com/@markusspiske?utm_source=medium&amp;utm_medium=referral">Markus Spiske</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>The Layered Model: How It All Fits Together</h4><p>Networking is organized into layers, with each layer handling one part of the job and passing its work to the next. The most practical model is the TCP/IP model, which has four layers:</p><p>Layer What It Does Examples Application Talks to the apps you use HTTP, HTTPS, DNS, SMTP Transport Splits data into segments and manages delivery TCP, UDP Internet Addresses and routes packets across networks IP, ICMP Network Access (Link) Moves bits across the physical medium Ethernet, Wi-Fi</p><p>You may also see the seven-layer OSI model, which splits these into finer pieces (Physical, Data Link, Network, Transport, Session, Presentation, Application). It’s mainly used for teaching and troubleshooting, but the idea is the same.</p><h4>Encapsulation: Envelopes Inside Envelopes</h4><p>As data moves down the layers on your device, each layer wraps it with its own header, a process called encapsulation:</p><ol><li>Your browser creates a request (Application layer).</li><li>TCP adds a header with port numbers and sequence numbers (Transport layer).</li><li>IP adds a header with source and destination IP addresses (Internet layer).</li><li>Ethernet or Wi-Fi adds a header with hardware (MAC) addresses, and the result is converted into electrical, light, or radio signals (Link layer).</li></ol><p>At the receiving end, the process runs in reverse. Each layer removes its own header and passes the contents up, a process called decapsulation, until the original data reaches the application.</p><p>It’s like putting a letter in an envelope, putting that envelope in a courier pouch, and loading the pouch onto a truck. At the other end, the truck is unloaded, the pouch opened, and the envelope handed to the recipient.</p><h4>The Journey: What Happens When You Visit a Website</h4><p>Let’s follow the data when you type <a href="http://www.example.com/">www.example.com</a> into your browser and press Enter.</p><p><strong>Step 1: Finding the Address (DNS)<br></strong>Your computer doesn’t know where <a href="http://www.example.com/">www.example.com</a> lives, so it asks a DNS server, “What’s the IP address for this name?” The DNS server replies with something like 93.184.215.14. Your browser now knows where to send its request.</p><p><strong>Step 2: Shaking Hands (TCP Connection)<br></strong>Before sending any real data, your computer and the web server set up a connection using a three-way handshake:</p><ol><li><strong>SYN:</strong> Your computer says, “I’d like to connect.”</li><li><strong>SYN-ACK:</strong> The server replies, “Sure, I’m ready.”</li><li><strong>ACK:</strong> Your computer confirms, “Great, let’s begin.”</li></ol><p>If the site uses HTTPS, an extra TLS handshake follows, where both sides agree on encryption keys so nobody in between can read the conversation.</p><p><strong>Step 3: Sending the Request<br></strong>Your browser sends an HTTP request, essentially “Please send me your homepage.” This request is encapsulated into packets and sent out through your Wi-Fi or cable.</p><p><strong>Step 4: Hopping Across the Internet (Routing)<br></strong>Your packets first reach your home router, which forwards them to your Internet Service Provider (ISP). From there, they pass through a series of routers, each one reading the destination IP address and deciding the best next hop.</p><p>A packet might make 10 to 20 hops, crossing cities, countries, and even undersea fiber-optic cables before reaching the server. Different packets from the same request may take different routes.</p><p>You can see this yourself. Open a terminal and type tracert google.com on Windows or traceroute google.com on macOS or Linux. You&#39;ll see each hop your packets take.</p><p><strong>Step 5: The Server Responds<br></strong>The web server receives the packets, reassembles your request, and sends back the webpage’s HTML, images, and scripts. These are split into packets of their own and routed back to you.</p><p><strong>Step 6: Reassembly and Display<br></strong>Your computer collects the incoming packets, uses the sequence numbers to put them in the right order, asks for any missing ones to be resent, and hands the complete data to your browser. The browser then renders the page.</p><p>All of this typically happens in a fraction of a second.</p><p><strong>Key Players Along the Way<br></strong>A few pieces of hardware keep this system running:</p><ul><li><strong>Network Interface Card (NIC):</strong> The part of your device that sends and receives signals.</li><li><strong>Switch:</strong> Connects devices within a local network and sends traffic to the correct device using MAC addresses.</li><li><strong>Router:</strong> Connects different networks and directs packets toward their destination using IP addresses.</li><li><strong>Modem:</strong> Converts signals between your home network and your ISP’s infrastructure.</li><li><strong>Servers:</strong> Powerful computers that store and deliver websites, apps, and files.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Z7sylncH5PDnBE0_" /><figcaption>Photo by <a href="https://unsplash.com/@elisa_ventur?utm_source=medium&amp;utm_medium=referral">Elisa Ventur</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>What Can Go Wrong?</h4><p>The internet is remarkably resilient, but problems do happen:</p><ul><li><strong>Packet loss:</strong> Some packets never arrive, which causes choppy calls or slow loading.</li><li><strong>Latency:</strong> The delay between sending and receiving. High latency is what gamers call “lag.”</li><li><strong>Jitter:</strong> Packets arriving at uneven intervals, which disrupts real-time audio and video.</li><li><strong>Congestion:</strong> Too much traffic on a link, like rush hour on a highway.</li></ul><p>Protocols like TCP are designed to detect and recover from many of these issues automatically.</p><h4>Where Security Comes In</h4><p>Because packets travel through many devices you don’t control, anyone positioned along the path could, in principle, capture them. That’s exactly what packet sniffing is (covered in our guide, How Packet Sniffing Works).</p><p>This is why encryption matters. With HTTPS, a VPN, or other encrypted protocols, the payload of every packet is scrambled. Someone intercepting it would see the envelope’s address, but the letter inside would be unreadable.</p><h4>Final Thoughts</h4><p>Every time you send a message or load a page, your data is converted into bits, packaged into packets, wrapped in layers of headers, guided by protocols, and passed from router to router across the world, then reassembled perfectly on the other side.</p><p>Going back to the book we mailed one page at a time: it seems inefficient at first, but it turns out to be the smartest way to move information across a vast, shared, constantly changing network. Understanding that journey is the foundation for everything else in networking and cybersecurity, from troubleshooting a slow connection to defending against attackers who try to read the envelopes along the way.</p><p><strong><em>Previously in the series:</em></strong></p><p><a href="https://blog.stackademic.com/what-are-ports-864b45f093cf">What Are Ports?</a></p><p><strong><em>Next in the series:</em></strong></p><blockquote><strong><em>“How Packet Sniffing Works (Beginner Guide)”</em></strong></blockquote><p><strong><em>— Khansa Mahmood</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8be88452eab4" width="1" height="1" alt=""><hr><p><a href="https://meetcyber.net/how-data-travels-on-the-internet-8be88452eab4">How Data Travels on the Internet</a> was originally published in <a href="https://meetcyber.net/">MeetCyber</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Packet Sniffing Works]]></title>
            <link>https://blog.stackademic.com/how-packet-sniffing-works-38d8fa9e6c72?source=rss-8981bdc96f46------2</link>
            <guid isPermaLink="false">https://medium.com/p/38d8fa9e6c72</guid>
            <category><![CDATA[beginners-guide]]></category>
            <category><![CDATA[computer-networking]]></category>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[students]]></category>
            <dc:creator><![CDATA[Khansa Mahmood]]></dc:creator>
            <pubDate>Fri, 06 Nov 2026 19:08:03 GMT</pubDate>
            <atom:updated>2026-11-08T19:49:20.457Z</atom:updated>
            <content:encoded><![CDATA[<h4>(Beginner Guide)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*saTj_MKrNgVStveo" /><figcaption>Photo by <a href="https://unsplash.com/@stikkx?utm_source=medium&amp;utm_medium=referral">Markus Stickling</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Imagine walking into a bustling, crowded coffee shop. Tables are packed close together, and everywhere you look, people are deep in conversation. Some are whispering secrets, others are shouting phone orders, and a few are just casually chatting about the weather. Normally, your brain tunes out this ambient noise, focusing only on the person sitting across from you. But what if you decided to actively listen in on every single table around you, capturing fragments of gossip, business plans, and phone numbers as they float through the air?</p><p>That is essentially what happens in the digital world when a network is in action.</p><p>The process of gathering, collecting, and recording some or all packets that go over a computer network, regardless of how they are addressed, is known as <strong>packet sniffing</strong>. This allows for the collection of all packets or a specific selection of packets for additional analysis. As network managers, you can monitor bandwidth and traffic, among many other uses for the gathered data.</p><p><strong><em>Welcome to Part # 5 of my series<br>“Peer-to-Peer: Networks Made Easy (By a Student, For Students)”</em></strong></p><h4>What Exactly Is a Packet?</h4><p>To understand packet sniffing, you first need to understand what is being sniffed.</p><p>When you send an email, stream a video, or load a webpage, the data doesn’t travel across the network as one big continuous stream. It gets broken into small chunks called packets. Think of it like mailing a long letter by tearing it into numbered pages and sending each page in its own envelope. Each envelope may take a different route, and the recipient puts the pages back in order when they arrive.</p><p>Every packet has two main parts:</p><ul><li><strong>The header:</strong> This is the outside of the envelope. It holds the source and destination addresses (IP addresses and MAC addresses), the protocol being used (such as TCP, UDP, or ICMP), port numbers, and sequencing information.</li><li><strong>The payload:</strong> This is the letter inside the envelope, the actual data being sent. It might be part of a webpage, a chunk of a file, or a line from a chat message.</li></ul><p>A packet sniffer can read both parts. Depending on whether the traffic is encrypted, that might mean only the envelope or the entire letter.</p><h4>How Packet Sniffing Actually Works</h4><p>Under normal conditions, your computer is a polite listener. Its network interface card (NIC) sees traffic passing by, but it only pays attention to packets addressed to it and quietly ignores the rest. That’s you at the coffee shop, focused on the person across the table.</p><p>Packet sniffing changes that behavior. The process generally works in three stages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FvhZjkT1Ke2LcvY2" /><figcaption>Photo by <a href="https://unsplash.com/@alexgallegos?utm_source=medium&amp;utm_medium=referral">Alex Gallegos</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Capturing the Traffic</h4><p>The sniffer puts the network card into a special state:</p><ul><li><strong>Promiscuous mode (wired and Wi-Fi networks):</strong> The NIC stops filtering and accepts every packet it can see, no matter who it’s addressed to.</li><li><strong>Monitor mode (wireless networks):</strong> The wireless card listens to all radio traffic on a channel, even from networks it isn’t connected to.</li></ul><p>This is the moment you stop tuning out the background noise and start listening to every table in the room.</p><h4>Decoding the Packets</h4><p>Raw packets are just streams of ones and zeros. The sniffer software decodes them layer by layer, following the structure of the network model. It works out the Ethernet frame, then the IP header, then the TCP or UDP segment, and finally the application data such as HTTP, DNS, or FTP. This turns the binary into something people can read, like “Device A requested <em>www.example.com</em> from DNS server B.”</p><h4>Analyzing the Results</h4><p>Once decoded, the captured data can be filtered, searched, and examined. An analyst might look for slow connections, unusual traffic spikes, failed login attempts, or devices talking to suspicious servers. Most of the real value of packet sniffing comes from this step.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*11SusSuXlArO7dWC" /><figcaption>Photo by <a href="https://unsplash.com/@scottrodgerson?utm_source=medium&amp;utm_medium=referral">Scott Rodgerson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Does the Network Setup Matter?</h4><p>Yes, quite a lot. What a sniffer can see depends on how the network is built.</p><p><strong>Hubs</strong> are old networking devices that broadcast every packet to every connected device. On a hub network, sniffing is easy, because every computer already receives everyone’s traffic. It’s like a coffee shop where everyone talks through one loudspeaker.</p><p><strong>Switches</strong> are what almost every modern network uses. A switch is smarter: it sends packets only to the port where the intended recipient is connected. A sniffer plugged into a switch will normally see only its own traffic plus broadcast messages. That’s more like a coffee shop with soundproof booths.</p><p>To see more on a switched network, there are a few options:</p><ul><li><strong>Port mirroring (SPAN):</strong> Administrators configure the switch to send a copy of traffic from one or more ports to a monitoring port. This is the legitimate, standard approach.</li><li><strong>Network TAPs:</strong> Hardware devices placed inline on a cable that copy all traffic passing through it.</li><li><strong>ARP spoofing:</strong> An attacker tricks devices into sending their traffic through the attacker’s machine, which creates a “man-in-the-middle” position. This is a malicious technique.</li></ul><p><strong>Wireless networks</strong> work like the open air of the coffee shop. Radio signals travel in every direction, so anyone within range with the right equipment can capture them. That’s why Wi-Fi encryption matters so much.</p><h4>Active vs. Passive Sniffing</h4><p>Packet sniffing generally falls into two categories:</p><ul><li><strong>Passive sniffing</strong> means quietly listening without interfering. It’s typical on hubs and wireless networks, and it’s very hard to detect because the sniffer sends nothing.</li><li><strong>Active sniffing</strong> means injecting traffic into the network to redirect packets, for example through ARP spoofing or MAC flooding (overloading a switch’s memory so it starts behaving like a hub). It’s needed on switched networks, and it’s easier to detect because it leaves traces.</li></ul><h4>The Good Side: Legitimate Uses</h4><p>Packet sniffing has a bad reputation, but it’s one of the most important tools in a network professional’s kit. Common legitimate uses include:</p><ul><li><strong>Troubleshooting:</strong> Finding out why a connection is slow, dropping, or failing.</li><li><strong>Bandwidth monitoring:</strong> Identifying which applications or devices are using the most traffic.</li><li><strong>Security monitoring:</strong> Intrusion detection systems (IDS) rely on packet inspection to spot attacks, malware communication, and data leaks.</li><li><strong>Forensics:</strong> Rebuilding what happened during a security incident.</li><li><strong>Learning and development:</strong> Students and developers use sniffers to see how protocols really behave, and to debug applications that talk over the network.</li></ul><h4>The Dark Side: Malicious Sniffing</h4><p>In the wrong hands, the same technique becomes a surveillance tool. Attackers use packet sniffing to:</p><ul><li>Steal usernames and passwords sent over unencrypted protocols such as HTTP, FTP, or Telnet.</li><li>Hijack sessions by capturing session cookies.</li><li>Collect sensitive information such as emails, messages, and financial data.</li><li>Map a network to plan further attacks.</li></ul><p>Public Wi-Fi, like our coffee shop, is a common hunting ground because many people connect to shared, often poorly secured networks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ahvl2v92EV7lUyGd" /><figcaption>Photo by <a href="https://unsplash.com/@ngeshlew?utm_source=medium&amp;utm_medium=referral">Lewis Kang&#39;ethe Ngugi</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Popular Packet Sniffing Tools</h4><p>If you want to explore packet sniffing yourself, on a network you own or have permission to monitor, these are the most common tools:</p><ul><li><strong>Wireshark:</strong> The best-known packet analyzer. It’s free, open source, and has a graphical interface with powerful filters. It’s the best starting point for beginners.</li><li><strong>tcpdump:</strong> A lightweight command-line sniffer for Linux and macOS, popular on servers.</li><li><strong>TShark:</strong> The command-line version of Wireshark.</li><li><strong>Kismet:</strong> A sniffer and detector focused on wireless networks.</li></ul><p>A simple first exercise: open Wireshark, start a capture on your own network adapter, visit a website, then type dns into the filter bar. You&#39;ll see your computer asking where to find the site, which is a small but eye-opening look at what&#39;s happening behind the scenes.</p><h4>How to Protect Yourself From Packet Sniffing</h4><p>You can’t stop people from listening, but you can make sure what they hear is gibberish. Encryption is the strongest defense.</p><ul><li><strong>Use HTTPS:</strong> Look for the padlock in your browser. HTTPS encrypts the payload, so a sniffer sees only scrambled data.</li><li><strong>Use a VPN on public Wi-Fi:</strong> A VPN wraps all your traffic in an encrypted tunnel.</li><li><strong>Prefer secure protocols:</strong> Use SSH instead of Telnet, and SFTP or FTPS instead of FTP.</li><li><strong>Secure your Wi-Fi:</strong> Use WPA3 (or at least WPA2) with a strong password.</li><li><strong>For organizations:</strong> Segment networks, enable switch protections such as Dynamic ARP Inspection and port security, and monitor for devices running in promiscuous mode.</li></ul><p>Going back to the coffee shop: encryption is like everyone switching to a language only they and their companion understand. The eavesdropper can still hear the voices, but the words mean nothing.</p><h4>A Quick Note on Legality and Ethics</h4><p>Packet sniffing is legal when you do it on your own network, or with explicit authorization as part of your job. Capturing other people’s traffic without permission can break wiretapping, privacy, and computer misuse laws in many countries. The rule is simple: only sniff networks you own or have written permission to monitor.</p><h4>Final Thoughts</h4><p>Packet sniffing is simply the act of listening to the conversations happening on a network. For network administrators and security professionals, it’s like a stethoscope that helps diagnose problems and catch threats early. For attackers, it’s a way to eavesdrop. Understanding how it works is the first step toward using it responsibly and protecting yourself from those who don’t.</p><p>The next time you’re in a crowded coffee shop, connected to the free Wi-Fi, remember that the room might be listening. Make sure your conversations are encrypted.</p><p><strong><em>Previously in the series:</em></strong></p><p><a href="https://meetcyber.net/how-data-travels-on-the-internet-8be88452eab4">How Data Travels on the Internet</a></p><p><strong><em>Next in the series:</em></strong></p><blockquote><strong><em>“What Happens When You Type a URL in Your Browser?)”</em></strong></blockquote><p><strong><em>— Khansa Mahmood</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38d8fa9e6c72" width="1" height="1" alt=""><hr><p><a href="https://blog.stackademic.com/how-packet-sniffing-works-38d8fa9e6c72">How Packet Sniffing Works</a> was originally published in <a href="https://blog.stackademic.com/">Stackademic</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Are Ports?]]></title>
            <link>https://blog.stackademic.com/what-are-ports-864b45f093cf?source=rss-8981bdc96f46------2</link>
            <guid isPermaLink="false">https://medium.com/p/864b45f093cf</guid>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[hacker]]></category>
            <category><![CDATA[university]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cyber-security-awareness]]></category>
            <dc:creator><![CDATA[Khansa Mahmood]]></dc:creator>
            <pubDate>Sun, 30 Aug 2026 10:23:28 GMT</pubDate>
            <atom:updated>2026-08-30T10:23:28.160Z</atom:updated>
            <content:encoded><![CDATA[<h4>(And Why Hackers Scan Them)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YXC0W2eWIVB7onKM" /><figcaption>Photo by <a href="https://unsplash.com/@roborobs?utm_source=medium&amp;utm_medium=referral">Robynne O</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Think of an IP address as the mailing address of an entire apartment building. It gets data to the right building, but how does the mail carrier know which specific apartment should receive the letter?</p><p>That is where <strong>ports</strong> come in.</p><p>In networking, a port is a virtual point where network connections start and end. They are software-based endpoints managed by your computer’s operating system. Without ports, your computer wouldn’t know if an incoming packet was a webpage, an email, or a file transfer. It would all just be noise.</p><p><strong><em>Welcome to Part # 3 of my series<br>“Peer-to-Peer: Networks Made Easy (By a Student, For Students)”</em></strong></p><h4><strong>What is a Port?</strong></h4><p>A port is a logical identifier that enables network traffic to reach the appropriate program by differentiating between various services or applications on a device.</p><p>At the Transport layer, ports provide data transmission and reception between devices via TCP and UDP.</p><p>They enable several apps to access the network simultaneously without disturbance. The operating system uses ports to direct incoming data to the right program.</p><h4><strong>How Ports Work</strong></h4><p>Every network port is assigned a 16-bit number ranging from <strong>0 to 65,535</strong>. When a service runs on a machine, like a web server or an SSH daemon, it “listens” on a specific port number for incoming traffic.</p><p>When you send data across the internet, your system packages it with both an IP address and a port number.</p><ul><li>The <strong>IP Address</strong> routes the packet to the correct target device.</li><li>The <strong>Port Number</strong> tells the receiving operating system which application should handle the payload.</li></ul><p>Ports fall into three main categories:</p><ul><li><strong>Well-Known Ports (0–1023):</strong> Reserved for core system services and widely used protocols (e.g., HTTP on 80, HTTPS on 443, SSH on 22).</li><li><strong>Registered Ports (1024–49151):</strong> Assigned by IANA for specific user processes or applications (e.g., MySQL on 3306, RDP on 3389).</li><li><strong>Dynamic / Private Ports (49152–65535):</strong> Used temporarily by client applications as origin ports when initiating outbound requests.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WP-Y70VbvufaZnke" /><figcaption>Photo by <a href="https://unsplash.com/@johnishappysometimes?utm_source=medium&amp;utm_medium=referral">John</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4><strong>Common Ports Every Security Professional Should Know</strong></h4><ul><li><strong>21:</strong> FTP (File Transfer Protocol)</li><li><strong>22:</strong> SSH (Secure Shell)</li><li><strong>23:</strong> Telnet (Unencrypted text communications)</li><li><strong>25:</strong> SMTP (Simple Mail Transfer Protocol)</li><li><strong>53:</strong> DNS (Domain Name System)</li><li><strong>80 / 443:</strong> HTTP / HTTPS (Web traffic)</li><li><strong>445:</strong> SMB (Server Message Block — often targeted in Windows environments)</li></ul><h4><strong>Why Hackers Scan Ports</strong></h4><p>Port scanning is one of the very first phases of cyber reconnaissance. Before an attacker can exploit a system, they need to map out its attack surface.</p><p>Here is what an attacker learns from a port scan:</p><ul><li><strong>Open Doors (Active Services):</strong> An open port means a service is actively accepting connections. Every open port is a potential entry point.</li><li><strong>Service &amp; Version Fingerprinting:</strong> Hackers don’t just look for open ports; they query them to discover the exact software and version running (e.g., <em>Apache 2.4.41</em> vs <em>OpenSSH 7.2</em>).</li><li><strong>Vulnerability Mapping:</strong> Once the service and version are identified, attackers cross-reference them against public vulnerability databases (like CVEs) to find unpatched exploits.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lHie2xnpM47sL0L0" /><figcaption>Photo by <a href="https://unsplash.com/@scottrodgerson?utm_source=medium&amp;utm_medium=referral">Scott Rodgerson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4><strong>How Port Scanning Works (The Mechanics)</strong></h4><p>Attacker tools like <strong>Nmap</strong> use various techniques to detect port states:</p><ol><li><strong>SYN Scan (Stealth Scan):</strong> Sends a TCP SYN packet. If the target responds withSYN-ACK, the port is open. The attacker resets the connection before completing the handshake to minimise logging.</li><li><strong>Connect Scan:</strong> Completes the full TCP 3-way handshake (SYN $\rightarrow$ SYN-ACK $\rightarrow$ ACK). Used when the scanner lacks raw socket privileges.</li><li><strong>UDP Scan:</strong> Sends UDP packets to target ports. If no response is received, it assumes open/filtered; if an ICMP Port Unreachable error comes back, the port is closed.</li></ol><h4><strong>How to Defend Against Unauthorised Port Scanning</strong></h4><p>Port scanning itself isn’t inherently malicious; administrators use it for inventory and auditing, but unauthorised scanning usually precedes an attack.</p><ul><li><strong>Apply Strict Firewall Rules:</strong> Block unused ports at the perimeter. Only expose essential services to the public internet.</li><li><strong>Implement Intrusion Detection Systems (IDS):</strong> Use tools like Snort or Suricata to detect rapid scanning patterns across port ranges.</li><li><strong>Disable Unnecessary Services:</strong> Close any port running services that aren’t strictly required for business operations.</li><li><strong>Use Port Knocking or VPNs:</strong> Keep management ports (like SSH 22 or RDP 3389) hidden behind a VPN or require sequence-based port knocking to open access.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IevqzpgZ3grWjyo3" /><figcaption>Photo by <a href="https://unsplash.com/@emilep?utm_source=medium&amp;utm_medium=referral">Emile Perron</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4><strong>Conclusion: Closing the Virtual Doors</strong></h4><p>At its core, network security comes down to visibility and control. Just as you wouldn’t leave every door and window in your house unlocked overnight, you shouldn’t leave unmonitored ports open to the internet.</p><p>Understanding how ports function and how malicious actors scan them allows you to take a proactive stance in hardening your systems. By auditing open ports regularly, closing unnecessary services, and enforcing strict firewall policies, you significantly reduce your attack surface and keep potential intruders locked outside.</p><h4><strong>Next Steps &amp; Key Takeaways</strong></h4><ul><li><strong>Audit your perimeter:</strong> Run a quick nmap -sV scan against your own public IP address (or stick to localhost if testing) to discover what services are currently exposed.</li><li><strong>Adopt the principle of least privilege:</strong> If a service doesn’t need external network access, bind it to 127.0.0.1 or block it at the host firewall level.</li><li><strong>Keep services updated:</strong> Since port scanners quickly reveal version information, patch management remains your strongest defence against automated exploit scripts</li></ul><p><strong><em>Previously in the series:</em></strong></p><p><a href="https://meetcyber.net/how-dns-works-186c17e924fb">How DNS Works</a></p><p><strong><em>Next in the series:</em></strong></p><blockquote><strong><em>“How Packet Sniffing Works (Beginner Guide)”</em></strong></blockquote><p><strong><em>— Khansa Mahmood</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=864b45f093cf" width="1" height="1" alt=""><hr><p><a href="https://blog.stackademic.com/what-are-ports-864b45f093cf">What Are Ports?</a> was originally published in <a href="https://blog.stackademic.com/">Stackademic</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How DNS Works]]></title>
            <link>https://meetcyber.net/how-dns-works-186c17e924fb?source=rss-8981bdc96f46------2</link>
            <guid isPermaLink="false">https://medium.com/p/186c17e924fb</guid>
            <category><![CDATA[students]]></category>
            <category><![CDATA[cyber-security-awareness]]></category>
            <category><![CDATA[explanation]]></category>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Khansa Mahmood]]></dc:creator>
            <pubDate>Mon, 04 May 2026 20:36:13 GMT</pubDate>
            <atom:updated>2026-05-04T20:36:13.044Z</atom:updated>
            <content:encoded><![CDATA[<h4>And How DNS Spoofing Attacks Happen</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/0*tZk6s2XT_v6LJ57M.jpg" /><figcaption>Image from Pinterest: <a href="https://www.pinterest.com/gridhostingltd/">Grid Hosting Limited</a>, used with permission from the author</figcaption></figure><p>Every time you open a website, something invisible happens in the background before the page even loads.</p><p>You type a name like <strong>google.com</strong>…<br>But computers don’t understand names.<br>They understand numbers. The IP Address, basically.</p><p>So how does your browser know where to go?</p><p>That’s where <strong>DNS</strong> comes in.</p><p>And if this DNS gets manipulated… You can be redirected without ever realising.</p><p>Welcome to Part #2 of my series</p><blockquote><strong>“Peer-to-Peer: Networks Made Simple (By a Student, For Students)”</strong></blockquote><p><em>(Please imagine a very fancy, very professional title)</em></p><h4><strong>What Is DNS?</strong></h4><p>DNS (Domain Name System) is like the Internet’s phonebook. It converts human-friendly website names into machine-readable IP addresses.</p><p>Simple Example:<br>- You type: “google.com&quot;<br>- DNS returns: “142.250.xxx.xxx”</p><p>👉 Without DNS, you would need to memorise IP addresses for every website.</p><p>Think of your phone contacts:<br>- You save a name: “Mom”<br>- Your phone stores the actual number behind it</p><p>When you tap &quot;Mom&quot;, your phone:<br>- Finds the number<br>- Makes the call</p><p>👉 DNS works the same way for websites.<br>You type a name, and it finds the real address behind it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*i0g9Qmc-qs4ghtuf" /><figcaption>Photo by <a href="https://unsplash.com/@matthieu_cabri?utm_source=medium&amp;utm_medium=referral">Matthieu Beaumont</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4><strong>How DNS Works (Step-by-Step) (Simple)</strong></h4><p>Here’s what happens when you visit a website:</p><p><strong>1. </strong>You type a website (example: google.com)<br><strong>2.</strong> Your device asks a DNS server: “What is the IP address?”<br><strong>3.</strong> DNS looks it up in its records<br><strong>4.</strong> DNS returns the correct IP address<br><strong>5. </strong>Your browser connects to that IP<br><strong>6.</strong> The website loads</p><p>👉 This entire process happens in milliseconds.</p><h4>Why DNS Is Important</h4><p>Without DNS:<br>- You couldn’t easily access websites<br>- You would need to remember long numbers<br>- The internet would be much harder to use</p><p>👉 DNS is what makes the internet user-friendly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-ReWfFicAhfU2Xvw" /><figcaption>Photo by <a href="https://unsplash.com/@flyd2069?utm_source=medium&amp;utm_medium=referral">FlyD</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>What Is DNS Spoofing?</h4><p>Now here’s where cybersecurity becomes important.</p><p><strong>DNS spoofing</strong> is an attack where hackers trick your system into using a fake DNS response. Instead of sending you to the real website… You are sent to a fake one.</p><p>Imagine you want to go to your bank:<br>- You type: <strong>yourbank.com</strong><br>- But instead of the real website…<br>- You are silently redirected to a fake copy</p><p>You log in thinking it’s real…</p><p>👉 But the attacker now has your credentials.</p><h4>How DNS Spoofing Works (Simple Breakdown)</h4><p>Attackers try to:<br>- Intercept DNS requests<br>- Send fake IP responses<br>- Trick your device into trusting them</p><p>So basically, your device sends a DNS request, and an attacker could intercept it (or poison the response). A fake IP address would be returned, and your browser would connect to the attacker’s server instead.</p><p>This can happen through:<br>- Unsafe public networks<br>- Malware on a device<br>- Vulnerable routers</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*y0fwkOr15tz4FFgG" /><figcaption>Photo by <a href="https://unsplash.com/@davidpupaza?utm_source=medium&amp;utm_medium=referral">David Pupăză</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Why DNS Spoofing Is Dangerous</h4><p>Because it<br>- Looks completely normal to the user<br>- Happens before the website even loads<br>- Can steal sensitive data like passwords</p><p>👉 The victim often has no idea that anything went wrong.</p><h4>How to Protect Yourself</h4><p>You don’t need advanced tools to stay safe. Basic steps help a lot:<br>- Use trusted networks (avoid unknown WiFi)<br>- Always check for HTTPS websites<br>- Keep your system and router updated<br>- Use secure DNS services when possible</p><p>Every click you make online depends on DNS.<br>You don’t see it. You don’t interact with it directly.<br>But it is always there, guiding where your request goes.<br>And when attackers exploit it… the deception is almost impossible to notice.</p><p>Understanding this all isn’t just for cybersecurity professionals; it’s for anyone who uses the internet. Because once you understand how the system works, you’re in a much better position to protect yourself.</p><p><strong>Previously in the series:</strong></p><p><a href="https://meetcyber.net/what-is-an-ip-address-d1810442c37a">What is an IP Address?</a></p><p><strong>Next in the series:</strong></p><blockquote><strong>“What Are Ports? And Why Hackers Constantly Scan Them.”</strong></blockquote><p><strong><em>-Khansa Mahmood</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=186c17e924fb" width="1" height="1" alt=""><hr><p><a href="https://meetcyber.net/how-dns-works-186c17e924fb">How DNS Works</a> was originally published in <a href="https://meetcyber.net/">MeetCyber</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is an IP Address?]]></title>
            <link>https://meetcyber.net/what-is-an-ip-address-d1810442c37a?source=rss-8981bdc96f46------2</link>
            <guid isPermaLink="false">https://medium.com/p/d1810442c37a</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cybersecurity-awareness]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[students]]></category>
            <category><![CDATA[hacker]]></category>
            <dc:creator><![CDATA[Khansa Mahmood]]></dc:creator>
            <pubDate>Mon, 27 Apr 2026 07:28:04 GMT</pubDate>
            <atom:updated>2026-04-27T07:28:04.240Z</atom:updated>
            <content:encoded><![CDATA[<h4>And How Hackers Track You</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/0*JuTCB-Csmk5ejCyD.jpg" /><figcaption>Image from Pinterest: <a href="https://www.pinterest.com/afnicregistry/">Afnic</a>, used with permission from the author</figcaption></figure><p>Every time you connect to the internet, you leave behind a digital address, a trace. This trace is a digital identifier that tells the online world where data should go and where it comes from.</p><p><strong>This is your IP Address.</strong></p><p>Most people don’t think about it. But in a field like cybersecurity, understanding IP Address on one of the first and basic steps towards understanding how the internet works and now how attackers take advantage of it.</p><p>So now let me welcome you to the first part of my series:</p><blockquote><strong>“Peer-to-Peer: Network Made Simple”</strong></blockquote><h4>What is an IP Address?</h4><p>An IP address (Internet Protocol address) is a unique number assigned to every device connected to a network.</p><p>Think of ordering food online:<br>- You place an order<br>- The delivery driver needs your address<br>- Without it, your food can’t arrive</p><p>👉 Your IP address works the same way; it tells the internet where to deliver information.</p><p>Example:<br>- IPv4: “192.168.1.1”<br>- IPv6: “2001:0db8:85a3:0000:0000:8a2e:0370:7334”</p><p>Without IP addresses, the internet simply wouldn’t function.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2EBknNfwqf4XDQkYDN6aIQ@2x.jpeg" /><figcaption>Photo by <a href="http://kvalifik.dk/">Kvalifik</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>How IP Addresses Work?</h4><p>Explaining it simply:<br>- You type a website, take for example, google.com<br>- DNS translates it into an IP<br>- Your request goes to that IP<br>- The server responds to your IP</p><p>👉 DNS is <strong>the Domain Name System</strong>, simply saying, it’s the human-readable form of an IP Address. <br>Small Example: “Google.com” → “142.250.xxx.xxx”</p><p><em>(I’ll cover DNS in detail in a separate article and will add a link here when it’s published.)</em></p><h4>What Information an IP Address Reveals</h4><p>An IP address doesn’t expose everything about you, but it does reveal more than you might expect.</p><p>It can show:<br>- Your approximate location (usually city or region)<br>- Your Internet Service Provider (ISP)<br>- Whether you’re using a home network, a company network, or mobile data</p><p><strong>Important:<br>Your IP address does not directly reveal:<br></strong>- Your exact home address<br>- Your name or identity<br>However, it can still be used as a starting point for tracking or targeting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w-AuWKVsD0zHf5UE2x_4aA@2x.jpeg" /><figcaption>Photo by <a href="https://markusspiske.com/">Markus Spiske</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>How Hackers Use IP Addresses</h4><p>On its own, an IP address is just a number. But in the hands of an attacker, it can become useful.</p><p><strong>1. Tracking Your Activity<br></strong>Websites log IP addresses automatically. While this is often used for analytics, it can also be used to monitor user behaviour.</p><p><strong>2. Packet Sniffing<br></strong>On unsecured networks (like public WiFi), attackers can intercept traffic and observe communication between devices.</p><p>If the data isn’t encrypted, sensitive information can be exposed.</p><p><strong>3. Scanning for Vulnerabilities<br></strong>Attackers can scan IP addresses to find:<br>- Open ports<br>- Running services<br>- Misconfigured systems<br>These can become entry points into a system.</p><p><strong>4. DDoS Attacks<br></strong>In a Distributed Denial-of-Service (DDoS) attack, a target IP address is flooded with massive traffic, overwhelming the system and causing it to crash.</p><p><strong>5. Profiling and Social Engineering<br></strong>An IP address can be combined with other data (location, browsing patterns, etc.) to build a profile of a user, which can then be used in targeted attacks.</p><h4>A Real-World Scenario</h4><p>Imagine you connect to free WiFi at a café.</p><p>An attacker on the same network is monitoring traffic. They can see devices connected to the network, including your IP address.</p><p>If you access websites that aren’t properly secured, they may attempt to intercept your data or analyse your activity.</p><p>This is why public networks are considered high-risk.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DKpWVxCdsBORxnORb-LRww@2x.jpeg" /><figcaption>Photo by Mikhail Fesenko on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>How to Protect Your IP Address</h4><p>-Use a VPN (Virtual Private Network) to mask your real IP address<br>-Avoid sensitive activity on public WiFi<br>-Make sure websites use HTTPS<br>-Keep your firewall enabled<br>-Avoid clicking suspicious links</p><h4>Common Misconceptions</h4><p>❌ “Someone can hack me instantly if they know my IP”<br>→ Not true. An IP address alone is not enough to gain access.</p><p>❌ “My IP reveals my exact location”<br>→ It only shows an approximate area, not your precise address.</p><p>✔️ Reality:<br>An IP address is a **starting point**, not a complete vulnerability.</p><p>Your IP address is like a digital footprint. Always present, often ignored. It quietly enables everything you do online, from browsing websites to sending messages. But it also plays a role in how you can be tracked, monitored, or targeted.</p><p>Understanding it isn’t just for cybersecurity professionals; it’s for anyone who uses the internet. Because once you understand how the system works, you’re in a much better position to protect yourself.</p><p><em>@Khansa Md.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d1810442c37a" width="1" height="1" alt=""><hr><p><a href="https://meetcyber.net/what-is-an-ip-address-d1810442c37a">What is an IP Address?</a> was originally published in <a href="https://meetcyber.net/">MeetCyber</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>