← Public decks·Computer Science

Networking: DNS, TCP Handshake, and TLS

Web networking path — DNS resolution, TCP three-way handshake, HTTP vs HTTPS/TLS basics.

12 cards· by GuruOwl

Make a deck like this from your own PDF — free.

Try it
  1. 01
    What does DNS do?
    Resolves human-readable domain names to IP addresses (and other records).
    dns
  2. 02
    Typical DNS lookup chain (recursive resolver view)?
    Stub → recursive resolver → root → TLD → authoritative name server.
    dns
  3. 03
    TCP three-way handshake sequence?
    SYN → SYN-ACK → ACK — establishes a reliable bidirectional connection.
    tcp
  4. 04
    TCP vs UDP in one line?
    TCP: reliable, ordered, connection-oriented. UDP: connectionless, low overhead, no delivery guarantees.
    tcp-udp
  5. 05
    What problem does TLS solve for HTTP?
    Encrypts and authenticates the channel (HTTPS) so eavesdroppers can’t read/modify traffic easily; server identity via certificates.
    tls
  6. 06
    What is a certificate authority (CA)?
    A trusted issuer of digital certificates binding public keys to identities (domains).
    tls
  7. 07
    HTTP is which OSI/Internet layer model “application” protocol over what transport?
    Application-layer protocol typically over TCP (or QUIC/UDP for HTTP/3).
    http
  8. 08
    What is a CDN primarily for?
    Cache and serve content from edge locations closer to users — lower latency and origin load.
    web
  9. 09
    What does NAT do?
    Network Address Translation maps private IPs to public IPs, sharing scarce public addresses.
    ip
  10. 10
    IPv4 address size vs IPv6?
    IPv4: 32-bit. IPv6: 128-bit.
    ip
  11. 11
    What is a SYN flood (high level)?
    Attacker sends many TCP SYNs without completing handshakes, exhausting server half-open connection resources.
    security
  12. 12
    Idempotent HTTP methods useful for safe retries?
    GET, PUT, DELETE are idempotent by spec; POST is not generally.
    http