Ravindra BagaleCourses & study guides मराठी Track your progress

13. Multiple Websites on One Server and HTTPS with Certbot

13.1 How Name-Based Virtual Hosting Works

By Last updated:

Ekach IP, ekach port 80 – mag server la kasa kalte konti site dakhvaychi? Browser pratyek request madhe Host: header pathavto. Web server to header server_name / ServerName shi julavto.

 Browser: GET / HTTP/1.1  Host: site1.yourdomain.com  ─┐
 Browser: GET / HTTP/1.1  Host: site2.yourdomain.com  ─┼─► 203.0.113.10:80 ─► match Host
 Scanner: GET / HTTP/1.1  Host: 203.0.113.10          ─┘        │
                                                               ├─ site1 → /var/www/site1
                                                               ├─ site2 → /var/www/site2
                                                               └─ no match → default site

Why this matters for security

Scanners and bots usually connect by IP, not by name. If your default site is a real application, every internet scanner sees it. A catch-all default that returns nothing (Nginx return 444) hides your real sites from IP-based scanning and blocks Host-header tricks.

Ravindra Bagale's Tip

You created two sites and the same site shows on both – a common problem for students. The reason is that server_name doesn't match and the default site wins. Use sudo nginx -T | grep server_name or sudo apachectl -S to see which file answers for which name.

Practice task

Use curl -v http://example.com -o /dev/null and find the Host header your client sends.

Extended teaching notes

Why this lesson matters

Use this lesson to strengthen systems you own: understand the risk, practise safely in a lab, then write and apply the fix.

Apply the fix across stacks

Same class of bug, same idea in every language.

Java / Spring Boot

Parameterise queries, encode output, CSRF tokens, limited Actuator, dependency scanning.

ASP.NET Core

EF Core / parameterised SQL, Razor encoding, HTTPS, Data Protection.

Node.js / Express

helmet, parameterised SQL, npm audit, avoid eval and shell concat.

Python / Django / Flask / FastAPI

ORM, autoescape, pip-audit, Bandit; never shell=True with user input.

PHP / Laravel

PDO/Eloquent, Blade escaping, composer audit.

Go / Ruby

database/sql placeholders / ActiveRecord; html/template / ERB escaping; govulncheck / Brakeman.

nginx / Apache / Tomcat

Hide versions, TLS, security headers, least-open ports.

MySQL / PostgreSQL / MongoDB / Redis

Private networks, auth on, least-privilege users, no 0.0.0.0/0.

AWS / Azure / GCP

Roles not long-lived keys, private data stores, cloud audit logs on.

Mini case study

Suppose we are on a purple-team exercise for an Indian mid-size company (sample data). Red notes a technique from this lesson against a lab clone. Blue must show the control that stops it, the log that would have fired, and the ticket that hardens production. That is the standard this course trains you for.

Defender's worksheet (do this today)

  1. Write the lesson title, date and the exact lab target you are allowed to use.
  2. List three owned systems (VMs, apps, or cloud accounts) where this lesson applies.
  3. Run one safe check from the lesson on a lab system only. Paste the command and output.
  4. Write a two-sentence fix you would give a teammate.
  5. Name one related public advisory (CERT-In, CISA, NVD, or a vendor bulletin) with its date.

Indian workplace (sample data)

Suppose we are a junior analyst at Infosys, TCS, Wipro or a fintech SOC in Bengaluru/Pune. Turn this lesson into one checklist item with an owner, a due date and a place to store evidence (ticket + screenshot).

Global practice

Compare your notes with OWASP, CIS Benchmarks, NIST CSF/IR guidance or a cloud Well-Architected security question. Write five lines on what overlaps.

Everyday analogy

Explain the risk and the fix to a family member without jargon. If they can repeat the warning, you understand it well enough to teach juniors.

Key terms

  • Control: a safeguard (patch, config, process, detection).
  • Finding: a weakness backed by evidence.
  • Remediation: the fix plus how you verified it.
  • Scope: systems you have written permission to touch.
  • Least privilege: only the access the task needs.
  • Defence in depth: several layers so one failure does not end the story.

Common mistakes

  • Skipping written permission "just for a quick scan".
  • Practising on hostel, office or public targets without authorisation.
  • Collecting tool output without writing the fix.
  • Copying attack steps onto production to "verify". Defenders verify with versions, configs and patches.
  • Publishing screenshots that contain secrets, cookies or internal hostnames.

Recap

  • Evidence, fix, owner, date.
  • Own lab only.
  • Fix > spectacle.