TD Cyber Labs

TrainersTool Trainers / curl Trainer 0 / 50 pts

curl

curl

Web · Easy · 5 lessons

curl makes HTTP requests without a browser, so you see exactly what a server sends — status codes, headers, and body. It is the fastest way to fingerprint a web stack and poke at endpoints during web recon. Practise against the site on 10.10.10.10.

1
Fetch a page
'curl URL' performs a GET and dumps the response body to your terminal — no rendering, just the raw bytes the server sent. This is your baseline look at any endpoint.
curl http://10.10.10.10
2
Read only the headers with -I
-I sends a HEAD request and prints just the response headers. Look for Server and X-Powered-By to fingerprint the stack, and for missing security headers like X-Frame-Options.
curl -I http://10.10.10.10
3
See the full exchange with -v
-v prints the request line and headers you send (>) alongside what comes back (<). It is how you confirm exactly what curl put on the wire when a request behaves unexpectedly.
curl -v http://10.10.10.10
4
Request a specific path
Append a path to hit a specific endpoint. /robots.txt is a classic first stop: it often names directories the site would rather you not visit.
curl http://10.10.10.10/robots.txt
5
Spot and follow a redirect
A 301/302 status means the page moved. By default curl shows the redirect response; -L tells it to follow the Location header to the real page. /admin here answers with a 301.
curl http://10.10.10.10/admin

Applications

practice 10.10.10.10--:--

learner@kali: ~ — Terminal