Tools and labs
Browser Developer Tools for Security Beginners: See What a Website Really Does
Every modern browser has a powerful set of developer tools built in. For security beginners, they are a free microscope for understanding how websites work, before you ever install a specialised tool.
Opening developer tools
In Chrome, Edge and Firefox, press F12 or Ctrl+Shift+I (Cmd+Option+I on Mac), or right click a page and choose Inspect. A panel opens with tabs such as Elements, Console, Network, Sources and Application (called Storage in Firefox).
Looking at what your own browser receives is normal and harmless. Using what you learn to tamper with someone else's website is not. The rule stays the same: only test systems you own or have permission for.
The Network tab
This is the most useful tab for security learning.
- Open the Network tab, then reload the page.
- You will see every file the page loads: HTML, scripts, images, API calls.
- Click any request to see Headers (request and response), Payload (data sent), Response and Timing.
Look for: status codes (200, 301, 404, 500), which domains the page talks to (third party trackers, analytics, ads), and security headers in responses such as Content-Security-Policy and Strict-Transport-Security. This connects to the request and response flow in our How the Internet Works post.
Cookies and storage
Open Application (Chrome) or Storage (Firefox). Under Cookies, you will see what the site stores in your browser. Important cookie attributes:
- HttpOnly: JavaScript cannot read the cookie, which helps against some attacks.
- Secure: the cookie is only sent over HTTPS.
- SameSite: limits when the cookie is sent with requests from other sites.
Session cookies often keep you logged in. This is why stealing a session cookie can be as bad as stealing a password, and why you should never paste cookie values anywhere when someone asks. Some scams ask victims to copy and paste code into the console. Never paste code into DevTools that someone sent you. Browsers even show warnings about this.
The Console
The Console shows JavaScript errors and warnings, and lets developers run code. For beginners, it is useful to notice errors, mixed content warnings (HTTP resources on an HTTPS page) and Content Security Policy violations. Run only code you wrote yourself, on your own pages or practice labs.
Certificates and the security view
Click the padlock or site information icon in the address bar to view certificate details: who issued it, for which domain, and validity dates. Chrome's DevTools also has a Security panel in some versions. Remember from our phishing SMS guide: a valid certificate means the connection is encrypted for that domain, not that the site is honest. Check the domain itself.
Safe exercises to try
- Open any news website and count how many third party domains load in the Network tab. It is an eye opener about tracking.
- On your own simple HTML page or a local practice app, look at the response headers and research each one.
- In your lab's OWASP Juice Shop, watch the API calls the app makes when you log in and add items. This prepares you for the Burp Suite intro.
- Use Elements to see that hidden fields and disabled buttons are just HTML, which is why servers must never trust the browser.
Why this matters
DevTools teach you the core truth of web security: everything in the browser is under the user's control. Secure applications check everything on the server. Once this clicks, web vulnerabilities make much more sense. It is a free skill that helps in AppSec, SOC investigations of phishing pages and even everyday troubleshooting.
Frequently asked questions
Can a website detect that I opened DevTools? Some sites try, but viewing what your own browser received is normal. Just do not use what you see to attack sites you do not own.
Is it safe to clear cookies in DevTools? Yes. You will be logged out of sites, which is sometimes a useful troubleshooting step.
Which browser is best for learning? Chrome, Edge and Firefox all have excellent developer tools. Use the one you are comfortable with.
Educational content, not legal advice. Check official sources before you rely on it. If you have lost money, call 1930 now. Terms