<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Ichraf Sassi</title>
    <description>The latest articles on DEV Community by Ichraf Sassi (@ichraf_sassi).</description>
    <link>https://dev.to/ichraf_sassi</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1977423%2F9beaec5b-03cd-435a-89f6-b19095e2200d.png</url>
      <title>DEV Community: Ichraf Sassi</title>
      <link>https://dev.to/ichraf_sassi</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ichraf_sassi"/>
    <language>en</language>
    <item>
      <title>AWS Cloud Security Roadmap, Phase 0 / Ch.1: How a Web Request Travels (DNS, TCP, TLS, HTTP, CIDR)</title>
      <dc:creator>Ichraf Sassi</dc:creator>
      <pubDate>Tue, 17 Nov 2026 20:55:28 +0000</pubDate>
      <link>https://dev.to/ichraf_sassi/aws-cloud-security-roadmap-phase-0-ch1-how-a-web-request-travels-dns-tcp-tls-http-cidr-20dp</link>
      <guid>https://dev.to/ichraf_sassi/aws-cloud-security-roadmap-phase-0-ch1-how-a-web-request-travels-dns-tcp-tls-http-cidr-20dp</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdgho6aq1gl9do08xmoqf.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdgho6aq1gl9do08xmoqf.png" alt=" " width="800" height="507"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;This is Chapter 1 of a full series.&lt;/strong&gt;&lt;br&gt;
The complete roadmap (networking → Linux → AWS → DevOps → DevSecOps → Cloud Security Engineering → Architecture) lives here:&lt;br&gt;
👉 &lt;a href="https://medium.com/@ichraf.sassi.456/aws-cloud-security-roadmap-the-full-learning-path-from-networking-to-security-engineering-1053df863c1e" rel="noopener noreferrer"&gt;AWS Cloud Security Roadmap: The Full Learning Path from Networking to Security Engineering&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Roadmap on Medium, hands-on chapters here on dev.to. Follow the series so you don't miss the next one.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Why start here?
&lt;/h2&gt;

&lt;p&gt;Cloud security sits on top of networking. If you can't explain what happens between typing a URL and seeing a page, you can't debug a security group, read a VPC Flow Log, or understand why a TLS certificate matters.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Goal of this chapter:&lt;/strong&gt; you can trace one request end to end, calculate a CIDR block by hand, and diagnose DNS, port and certificate problems from the command line.&lt;/p&gt;




&lt;h2&gt;
  
  
  The big picture
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3l88j6dbt1ur3zb70zap.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3l88j6dbt1ur3zb70zap.png" alt=" " width="800" height="507"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Every layer can fail on its own, with its own symptoms. That's the whole skill: &lt;strong&gt;know which layer is broken.&lt;/strong&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  1. DNS: names to IPs
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Resolution chain:&lt;/strong&gt; stub resolver (your OS) → recursive resolver (ISP / 1.1.1.1 / 8.8.8.8) → root servers → TLD servers (&lt;code&gt;.com&lt;/code&gt;) → authoritative server for the domain.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Record&lt;/th&gt;
&lt;th&gt;Purpose&lt;/th&gt;
&lt;th&gt;Example&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;A&lt;/td&gt;
&lt;td&gt;name → IPv4&lt;/td&gt;
&lt;td&gt;&lt;code&gt;example.com → 93.184.216.34&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;AAAA&lt;/td&gt;
&lt;td&gt;name → IPv6&lt;/td&gt;
&lt;td&gt;&lt;code&gt;example.com → 2606:2800:...&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;CNAME&lt;/td&gt;
&lt;td&gt;alias to another name&lt;/td&gt;
&lt;td&gt;&lt;code&gt;www → example.com&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;TXT&lt;/td&gt;
&lt;td&gt;free text (SPF, domain verification)&lt;/td&gt;
&lt;td&gt;&lt;code&gt;"v=spf1 ..."&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;MX&lt;/td&gt;
&lt;td&gt;mail servers&lt;/td&gt;
&lt;td&gt;&lt;code&gt;10 mail.example.com&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;TTL&lt;/strong&gt; = how many seconds resolvers may cache the answer. Low TTL = fast changes, more queries. High TTL = fewer queries, slow propagation. This is why "I changed the DNS but nothing happened" is usually just cache.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Rule:&lt;/strong&gt; a CNAME can't coexist with other records at the same name, and it can't sit at the zone apex. That's why Route 53 has &lt;em&gt;alias records&lt;/em&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. TCP: reliable delivery
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Three-way handshake:&lt;/strong&gt; SYN → SYN/ACK → ACK. Only then does data flow.&lt;/li&gt;
&lt;li&gt;A &lt;strong&gt;port&lt;/strong&gt; identifies the service: 22 SSH, 80 HTTP, 443 HTTPS, 53 DNS, 3306 MySQL, 5432 PostgreSQL.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;TCP vs UDP:&lt;/strong&gt; TCP = ordered, acknowledged, retransmitted. UDP = fire and forget (DNS queries, streaming, QUIC builds on it).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Symptoms to recognize:&lt;/strong&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;em&gt;Connection refused&lt;/em&gt; → host reachable, nothing listening on that port.&lt;/li&gt;
&lt;li&gt;
&lt;em&gt;Timeout&lt;/em&gt; → packets dropped silently (firewall / security group / wrong route).&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That distinction (refused vs timeout) will save you hours in AWS later.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. TLS: the encrypted channel
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Client sends &lt;strong&gt;ClientHello&lt;/strong&gt; with &lt;strong&gt;SNI&lt;/strong&gt; (the hostname it wants, so one IP can host many sites).&lt;/li&gt;
&lt;li&gt;Server returns its &lt;strong&gt;certificate chain&lt;/strong&gt; (leaf → intermediate → root CA).&lt;/li&gt;
&lt;li&gt;Client verifies: chain trusted? hostname matches? not expired?&lt;/li&gt;
&lt;li&gt;Both sides derive session keys; everything after is encrypted.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;strong&gt;What a certificate proves:&lt;/strong&gt; whoever answered controls that domain name, as validated by a CA.&lt;br&gt;
&lt;strong&gt;What it does NOT prove:&lt;/strong&gt; that the site is honest or safe. Phishing sites have valid certificates too.&lt;/p&gt;
&lt;h2&gt;
  
  
  4. HTTP: the conversation
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Code&lt;/th&gt;
&lt;th&gt;Meaning&lt;/th&gt;
&lt;th&gt;Think&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;200&lt;/td&gt;
&lt;td&gt;OK&lt;/td&gt;
&lt;td&gt;worked&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;301 / 302&lt;/td&gt;
&lt;td&gt;redirect&lt;/td&gt;
&lt;td&gt;follow &lt;code&gt;Location&lt;/code&gt; header&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;400&lt;/td&gt;
&lt;td&gt;bad request&lt;/td&gt;
&lt;td&gt;client sent garbage&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;401&lt;/td&gt;
&lt;td&gt;unauthenticated&lt;/td&gt;
&lt;td&gt;who are you?&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;403&lt;/td&gt;
&lt;td&gt;forbidden&lt;/td&gt;
&lt;td&gt;I know you, no access&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;404&lt;/td&gt;
&lt;td&gt;not found&lt;/td&gt;
&lt;td&gt;wrong path&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;429&lt;/td&gt;
&lt;td&gt;too many requests&lt;/td&gt;
&lt;td&gt;rate limited&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;500&lt;/td&gt;
&lt;td&gt;server error&lt;/td&gt;
&lt;td&gt;app crashed&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;502 / 503 / 504&lt;/td&gt;
&lt;td&gt;bad gateway / unavailable / gateway timeout&lt;/td&gt;
&lt;td&gt;typical load balancer symptoms&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Methods: &lt;code&gt;GET&lt;/code&gt; read, &lt;code&gt;POST&lt;/code&gt; create, &lt;code&gt;PUT&lt;/code&gt; replace, &lt;code&gt;PATCH&lt;/code&gt; modify, &lt;code&gt;DELETE&lt;/code&gt; remove.&lt;br&gt;
Headers worth knowing: &lt;code&gt;Host&lt;/code&gt;, &lt;code&gt;Cookie&lt;/code&gt;, &lt;code&gt;Set-Cookie&lt;/code&gt;, &lt;code&gt;Authorization&lt;/code&gt;, &lt;code&gt;Content-Type&lt;/code&gt;, &lt;code&gt;Location&lt;/code&gt;, &lt;code&gt;Strict-Transport-Security&lt;/code&gt;.&lt;/p&gt;
&lt;h2&gt;
  
  
  5. IPv4 and CIDR: do it by hand
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;/N&lt;/code&gt; means the first N bits are the network part. Addresses in the block = 2^(32−N).&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;CIDR&lt;/th&gt;
&lt;th&gt;Addresses&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;/16&lt;/td&gt;
&lt;td&gt;65,536&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;/24&lt;/td&gt;
&lt;td&gt;256&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;/26&lt;/td&gt;
&lt;td&gt;64&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;/28&lt;/td&gt;
&lt;td&gt;16&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;Private ranges (RFC 1918):&lt;/strong&gt; &lt;code&gt;10.0.0.0/8&lt;/code&gt;, &lt;code&gt;172.16.0.0/12&lt;/code&gt;, &lt;code&gt;192.168.0.0/16&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fndrb84revaaavrmg6kvz.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fndrb84revaaavrmg6kvz.png" alt=" " width="799" height="413"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;
  
  
  Worked example A: &lt;code&gt;192.168.10.77/26&lt;/code&gt;
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Block size = 64 (since /26 leaves 6 host bits, 2^6 = 64).&lt;/li&gt;
&lt;li&gt;77 falls in the block starting at 64 → &lt;strong&gt;network = 192.168.10.64&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Broadcast = 192.168.10.127&lt;/strong&gt; (64 + 64 − 1)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Usable hosts = .65 – .126&lt;/strong&gt; (62 hosts)&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;
  
  
  Worked example B: &lt;code&gt;10.0.5.200/22&lt;/code&gt;
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;/22 → block size 4 in the third octet.&lt;/li&gt;
&lt;li&gt;5 falls in the block starting at 4 → &lt;strong&gt;network = 10.0.4.0&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Broadcast = 10.0.7.255&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Usable hosts = 10.0.4.1 – 10.0.7.254&lt;/strong&gt; (1,022 hosts)&lt;/li&gt;
&lt;/ul&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;AWS preview:&lt;/strong&gt; AWS reserves 5 addresses in every subnet, so a /24 subnet gives &lt;strong&gt;251&lt;/strong&gt; usable IPs, not 254. We'll use this in the VPC chapter.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3&gt;
  
  
  Quick drill (answers at the bottom)
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;How many addresses in a /20?&lt;/li&gt;
&lt;li&gt;What's the broadcast of &lt;code&gt;172.16.33.9/21&lt;/code&gt;?&lt;/li&gt;
&lt;/ol&gt;
&lt;h2&gt;
  
  
  6. Routing, NAT, stateful vs stateless
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Default gateway:&lt;/strong&gt; where your host sends anything not on its local network.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;NAT:&lt;/strong&gt; many private hosts share one public IP; the NAT device rewrites addresses and tracks connections.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Stateful filter:&lt;/strong&gt; remembers connections; if outbound is allowed, the reply is automatically allowed. (AWS &lt;strong&gt;security groups&lt;/strong&gt;.)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Stateless filter:&lt;/strong&gt; judges every packet alone; you must allow return traffic explicitly. (AWS &lt;strong&gt;network ACLs&lt;/strong&gt;.)&lt;/li&gt;
&lt;/ul&gt;


&lt;h2&gt;
  
  
  Build: trace one request
&lt;/h2&gt;

&lt;p&gt;Run these against any site and label each output on your diagram:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;dig +trace example.com                 &lt;span class="c"&gt;# full DNS resolution chain&lt;/span&gt;
curl -v https://example.com            &lt;span class="c"&gt;# TCP + TLS + HTTP in one view&lt;/span&gt;
openssl s_client -connect example.com:443 -servername example.com   &lt;span class="c"&gt;# cert chain&lt;/span&gt;
ss -tulpn                              &lt;span class="c"&gt;# what's listening on YOUR machine&lt;/span&gt;
traceroute example.com                 &lt;span class="c"&gt;# path through routers&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Deliverable:&lt;/strong&gt; redraw the request diagram above from memory (draw.io / Excalidraw / paper) with the real output of each command next to its layer. Drawing it yourself is what makes it stick.&lt;/p&gt;

&lt;h2&gt;
  
  
  Break it (and diagnose from the CLI)
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Break&lt;/th&gt;
&lt;th&gt;How (in a lab / local machine)&lt;/th&gt;
&lt;th&gt;How to diagnose&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Wrong DNS&lt;/td&gt;
&lt;td&gt;add &lt;code&gt;127.0.0.1 mysite.test&lt;/code&gt; vs a wrong IP in &lt;code&gt;/etc/hosts&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;dig&lt;/code&gt;, &lt;code&gt;getent hosts&lt;/code&gt;, &lt;code&gt;curl -v&lt;/code&gt; shows the IP used&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Blocked port 443&lt;/td&gt;
&lt;td&gt;local firewall rule dropping 443&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;curl -v&lt;/code&gt; hangs (timeout), &lt;code&gt;nc -zv host 443&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Nothing listening&lt;/td&gt;
&lt;td&gt;stop your local web server&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;curl&lt;/code&gt; → &lt;em&gt;connection refused&lt;/em&gt;, &lt;code&gt;ss -tulpn&lt;/code&gt; shows no listener&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Expired / mismatched cert&lt;/td&gt;
&lt;td&gt;use &lt;code&gt;curl https://expired.badssl.com&lt;/code&gt; or &lt;code&gt;wrong.host.badssl.com&lt;/code&gt; (public test sites)&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;openssl s_client&lt;/code&gt; + &lt;code&gt;curl -v&lt;/code&gt; error text&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Write each fix as a 3-line runbook: &lt;strong&gt;symptom → check → fix.&lt;/strong&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  Cheat sheet
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcrqhe4bbfgpgjd2tusfv.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcrqhe4bbfgpgjd2tusfv.png" alt=" " width="799" height="493"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Symptom&lt;/th&gt;
&lt;th&gt;Likely layer&lt;/th&gt;
&lt;th&gt;First command&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;"Could not resolve host"&lt;/td&gt;
&lt;td&gt;DNS&lt;/td&gt;
&lt;td&gt;&lt;code&gt;dig example.com&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Hangs then times out&lt;/td&gt;
&lt;td&gt;Firewall / routing&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;nc -zv host port&lt;/code&gt;, &lt;code&gt;traceroute&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Connection refused&lt;/td&gt;
&lt;td&gt;Nothing listening&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;ss -tulpn&lt;/code&gt; on the server&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Certificate error&lt;/td&gt;
&lt;td&gt;TLS&lt;/td&gt;
&lt;td&gt;&lt;code&gt;openssl s_client -connect host:443 -servername host&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;403 / 404 / 5xx&lt;/td&gt;
&lt;td&gt;HTTP / app&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;curl -v&lt;/code&gt;, check app + LB logs&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  ✔ Checkpoint
&lt;/h2&gt;

&lt;p&gt;You're ready for the next chapter when you can, without notes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;explain DNS → TCP → TLS → HTTP in order,&lt;/li&gt;
&lt;li&gt;compute network/broadcast/host range for any CIDR,&lt;/li&gt;
&lt;li&gt;tell "refused" from "timeout" and know what each implies,&lt;/li&gt;
&lt;li&gt;diagnose a bad cert from the command line.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Drill answers:&lt;/strong&gt; 1) 4,096. 2) /21 → block size 8 in the third octet; 33 is in 32–39 → broadcast &lt;code&gt;172.16.39.255&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  📚 Docs
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://aws.amazon.com/route53/what-is-dns/" rel="noopener noreferrer"&gt;What is DNS? (Amazon Route 53)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP" rel="noopener noreferrer"&gt;MDN: HTTP&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://developer.mozilla.org/en-US/docs/Web/Security/Transport_Layer_Security" rel="noopener noreferrer"&gt;MDN: Transport Layer Security&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;strong&gt;Next up:&lt;/strong&gt; Chapter 2, Linux for cloud engineers (users, permissions, systemd, logs, SSH hardening).&lt;/p&gt;

&lt;p&gt;Full roadmap with every phase, certification path and job mapping:&lt;br&gt;
👉 &lt;a href="https://medium.com/@ichraf.sassi.456/aws-cloud-security-roadmap-the-full-learning-path-from-networking-to-security-engineering-1053df863c1e" rel="noopener noreferrer"&gt;Read the complete AWS Cloud Security Roadmap on Medium&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Lab note: commands tested conceptually against public test domains only. Only test systems you own or are authorized to test.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>network</category>
      <category>beginners</category>
      <category>aws</category>
      <category>devops</category>
    </item>
  </channel>
</rss>
