User targeted network secure applications are, realistically, hardly more than an inside joke. As if the common end user has any chance of knowing more about the construction of network traffic than the people that built the system. Most favorably such pursuits as security conscious browsing pits you in a thermometer race; your countermeasures vs. the various levels of people attempting to harvest and exploit network traffic and the information it contains.
For example. Consider PPPoE. A very old component of modern day kernels. PPPoE is one of those security conscious technologies because PPP is actually underneath ethernet, way underneath. The people working on implementing, using, and securing PPPoE are committing themselves to somewhat of a joke, or the most easily accessible route to a desired functionality. The ethernet layer runs on tcp/ip protocol stacks. TCP/IP protocol stacks work because the chipset on the cards is designed to interpret protocols underneath even IP. Underneath even IP, another three or four protocol stacks down, are indeed the same circuit logic gates which, at one time, performed PPP functionality. Those in the 90s which enabled a PPP stack that they could use client-server programs at the shell prompts were, again, adding another layer of PPP on top of circuit paths which already handled PPP. The circuit paths for PPP were used to provide for dialup and, later, shell. The software PPP was necessary to handle the client side of large applications; most commonly for windowing applications. The server side of the software could have produced the same result using hardware capabilities with a significant blow to network traffic.
So, really, if you think you are using a network security conscious application, recall that there is a host of individuals and technologies which could do everything of ethernet with, say, a standard dialup modem. Even today, if you fabricated a dongle to adjust the wire current voltages, you could go ahead and plug your ethernet into your standard dialup modem (with an connection adapter) and you could indeed use the open internet with a standard dialup modem. As your modem chipset is designed to expect PPP type transactions and timings it would be necessary for you to write your own code. Estimate taking the first three months to write PPP level loops and structures to perform so much as an HTTP GET request and another six months to sort out the returning bitstream and feed that to a modern web browser. After that you could probably check your e-mail sometime before the following Christmas.
The fact remains, though, what would take a new pursuit near a year to check e-mail has already been done, is well known, and is thoroughly documented by those engineers and techs that have worked on it. Postulating network security from the point of view of a web browser is cherishably naive because, a few layers below IP, it is all looks like swiss cheese and works only because the extra bits and paths have become deprecated and unused but not sealed off and removed. Factoring and securing a hardware breadboard is a ridiculously expensive and impossible task. Security by obscurity really is the business profit solution.