Author profile for DoVPN

Steve Price

Independent VPN researcher and privacy writer

Computer science background, 20+ years in IT and networking, and a practical focus on VPN leak testing, kill switch reliability, safer public Wi-Fi, online banking safety, and privacy-focused troubleshooting.

Illustrated avatar for Steve Price
20+ years in IT and networking
Computer science background
VPN leak and kill switch testing
Public Wi-Fi and banking safety

Technical privacy writing built from real network work.

Steve Price is an independent VPN researcher and privacy writer with a computer science background and more than 20 years of experience in IT and networking. He has spent much of that time debugging systems, reverse engineering behavior, and tracing how applications and network traffic work in real-world conditions.

His work focuses on VPN security, leak testing, kill switch reliability, and the privacy limits of consumer VPNs. He writes about IP, DNS, IPv6, and WebRTC leaks; safer use of public Wi-Fi; online banking over untrusted networks; and how browsers, operating systems, and VPN clients interact under failure conditions.

His approach is practical and test-driven: verify claims, reproduce issues, inspect network behavior, and document what users can check for themselves.

What Steve researches.

VPN leak testing

Checking IP, DNS, IPv6, and WebRTC behavior so readers can tell whether a VPN is actually protecting traffic.

Kill switch reliability

Looking at what happens when VPN tunnels fail, networks change, or apps restart under imperfect conditions.

Practical privacy guidance

Translating technical behavior into clear, realistic advice for public Wi-Fi, online banking, and everyday browsing.

Provider claim verification

Separating marketing language from reproducible checks, documented trade-offs, and user-visible evidence.

Clear guidance, testable claims.

For DoVPN, Steve focuses on the parts of VPN use where trust can be inspected: leak behavior, failure modes, privacy trade-offs, and realistic user safety.

  • Verify claims with repeatable checks whenever possible.
  • Explain limitations clearly instead of overstating privacy guarantees.
  • Prioritize safety, reliability, and user trust over provider marketing.
  • Keep guidance practical enough for readers to test on their own devices.

Recent DoVPN writing.