Using Wireshark on Your Own Network: What Your Traffic Really Shows
Running Wireshark on your own computer and home network shows which devices talk, which domain names they look up, which servers they connect to and how often. Most web content is encrypted with TLS, so you will not see passwords or page contents for HTTPS sites, but you can still see DNS queries (unless encrypted), the server name in many TLS handshakes, IP addresses and traffic volume.
Topic: Security Tools, Authorized Labs & CTFs in Cybersecurity & Ethical Hacking · Tutorial
Quick answer: Running Wireshark on your own computer and home network shows which devices talk, which domain names they look up, which servers they connect to and how often. Most web content is encrypted with TLS, so you will not see passwords or page contents for HTTPS sites, but you can still see DNS queries (unless encrypted), the server name in many TLS handshakes, IP addresses and traffic volume. Smart TVs and IoT devices often reveal steady background connections. Use what you learn to switch on encrypted DNS, update devices and remove apps that phone home too often. Only capture traffic you own or have permission to see.
Key takeaways
- Wireshark is a free, legal protocol analyser when used on your own traffic.
- HTTPS hides content, but metadata such as domains and timing remains visible.
- Plain DNS reveals every site your devices look up.
- IoT devices often generate constant background traffic.
- Capturing other people's traffic without consent can break the law.
Table of Contents
- What Is Wireshark and Is It Legal to Use?
- How Do You Start a Safe Capture on Your Own Device?
- What Can You Actually See in Your Traffic?
- What Does Encryption Hide From Wireshark?
- Which Display Filters Help Beginners?
- What Should You Change After Looking?
- How Can You Take Packet Analysis Further?
- References
What Is Wireshark and Is It Legal to Use?
Wireshark is an open source network protocol analyser. It records packets passing through a network interface and decodes hundreds of protocols, as described in the Wireshark User's Guide. Network engineers use it to troubleshoot and security teams use it to investigate incidents.
Using it on your own device or network is legal. Capturing traffic on networks you do not own, such as office, hostel or cafe Wi-Fi, without written permission can breach Sections 43 and 66 of India's IT Act 2000 and privacy rules under the DPDP Act 2023.
How Do You Start a Safe Capture on Your Own Device?
- Install Wireshark from wireshark.org only.
- Pick your active interface, usually Wi-Fi or Ethernet.
- Close unneeded apps so the capture is easier to read.
- Capture for a few minutes, then stop and save the file.
- Store capture files securely; they can contain personal data.
On a laptop you normally see only your own device's traffic plus broadcasts. Seeing traffic from other home devices needs a router or switch that supports port mirroring, which is a more advanced setup.
What Can You Actually See in Your Traffic?
| Visible item | What it tells you |
|---|---|
| DNS queries (port 53) | Domain names your apps look up, including trackers |
| TLS server name (SNI) | Which site a HTTPS connection is for, in many cases |
| IP addresses and ports | Which servers and services are contacted |
| Traffic timing and volume | When devices are active, even when idle |
| Plain HTTP | Full requests and responses, which should be rare today |
| ARP, mDNS, SSDP | Local devices announcing themselves on your network |
Many people are surprised by how many update, analytics and advertising domains appear in a short capture, even when nobody is using the device.
What Does Encryption Hide From Wireshark?
HTTPS uses TLS, and TLS 1.3 (RFC 8446) encrypts more of the handshake than older versions, including the server certificate. Page content, cookies and passwords stay hidden. Many browsers and apps use QUIC, defined in RFC 9000, which runs over UDP port 443 and is also encrypted.
DNS over HTTPS (RFC 8484) hides domain lookups inside HTTPS. If your browser uses it, you will see far fewer DNS packets. Metadata such as IP addresses and timing still remains visible to anyone on the path, including your internet provider.
Which Display Filters Help Beginners?
Display filters narrow a saved capture without changing it. Syntax is documented in the display filter reference.
dns
tls.handshake.extensions_server_name
http.request
quic
ip.addr == 192.168.1.20
!(arp || mdns || ssdp)
| Filter | Shows |
|---|---|
| dns | All plain DNS lookups |
| tls.handshake.extensions_server_name | TLS handshakes that carry a server name |
| http.request | Unencrypted web requests |
| ip.addr == 192.168.1.20 | Traffic to or from one local device |
For more patterns, see our Wireshark filters guide.
What Should You Change After Looking?
- Enable encrypted DNS in your browser or router.
- Remove apps and browser extensions that contact many tracking domains.
- Update router and IoT firmware, and put IoT devices on a guest network.
- Replace any service still using plain HTTP logins.
- Follow CISA home network security tips for router settings.
How Can You Take Packet Analysis Further?
Packet captures are one data source among many. NIST SP 800-92 explains how logs and network records support security monitoring. Learn how attackers abuse sniffing in our network sniffing explainer, and practise in lab networks you control. For structured practice, ask about our network security and SOC training.
References
Frequently Asked Questions
What's Your Reaction?
Like
0
Dislike
0
Love
0
Funny
0
Wow
0
Sad
0
Angry
0