Step 1: Change Default Router Admin Password
Log in to your router at 192.168.0.1 or 192.168.1.1 (check the sticker on your router). Change the admin password β not the Wi-Fi password. Use our Password Generator to create a strong one.
Step 2: Use WPA3 Encryption (or WPA2-AES)
- Go to Wireless β Security in your router settings
- Select WPA3 if available, or WPA2-AES as minimum
- Never use WEP (cracked in minutes) or plain WPA (deprecated)
- Wi-Fi password: 12+ random characters β generate one β
Step 3: Change Your SSID (Network Name)
- Don't use your name, address, or router brand as the SSID
- These reveal information to attackers wardriving your neighbourhood
- Optionally disable SSID broadcast (adds friction, not full protection)
Step 4: Disable WPS
WPS (Wi-Fi Protected Setup) has a known brute-force vulnerability (Pixie Dust attack) that can recover your Wi-Fi PIN in minutes. Disable it in your router settings β Advanced Wireless β WPS.
Step 5: Update Router Firmware
# Check if your router's web interface is exposed
curl -I http://192.168.1.1 | grep -i "server"
# Most routers: Settings β Administration β Firmware Update
# Enable auto-update if availableStep 6: Detect Rogue Devices on Your Network
# Linux β scan your subnet for all connected devices
nmap -sn 192.168.1.0/24
# View ARP table (shows MAC addresses of connected devices)
arp -a # Linux / macOS / Windows
arp -an # Numeric output on Windows
# macOS
arp -a | grep -v incompleteStep 7: Enable Router Firewall
Most modern routers have a built-in firewall. Verify it's enabled under Security β Firewall. Enable SPI (Stateful Packet Inspection) if available.
Step 8: Disable Remote Management
Turn off "Remote Management", "WAN Admin Access", or "Remote Web Access" in your router settings. This prevents anyone on the internet from accessing your router's admin panel.
Step 9: Set Up a Guest Network for IoT Devices
Keep smart TVs, cameras, and IoT devices on a separate guest network, isolated from your computers. Most modern routers support this under Wireless β Guest Network.
Step 10: Check for DNS Hijacking
# Check what DNS your device is actually using
cat /etc/resolv.conf # Linux
scutil --dns | grep "nameserver" # macOS
ipconfig /all | findstr "DNS Servers" # Windows
# Verify DNS isn't hijacked β compare results across servers
dig A google.com @8.8.8.8 +short # Google DNS
dig A google.com @1.1.1.1 +short # Cloudflare DNS
# Results should match your router's DNS result
# Check your router's DNS settings haven't been changed
curl -s http://192.168.1.1 | grep -i "dns" # Very basic check