With three addresses you remember them. At twenty it becomes «whose is this one?», and at forty you are paying for a proxy nobody has used in a month.
The minimum set of fields
Address and port, login and password, type and country, paid-on and expires-on, seller, which account it is bound to. Nine columns, none of them spare.
Plus status: working, spare, to be replaced. Without it spares get lost, and in an emergency you discover there is no reserve — which is exactly when you need one, as in a proxy dying mid-run.
Why the expiry date
Proxies end quietly. The account simply stops connecting and you spend half an hour looking for a fault that is not there. A date column and a reminder a few days out removes that scenario entirely.
Why the account binding
So that «one account, one address» is enforced rather than merely declared. The table shows immediately when two accounts share one proxy — consequences in how many accounts per proxy.
Why the seller
Because when an address turns out not to be what it was sold as, you will know who to go to and which other addresses from that batch to re-check. The tricks are collected in how sellers cheat.
Where to keep it
Anywhere, as long as it is one place with a backup. Proxy logins are keys: if the table leaks, access to the whole fleet leaks with it. On storage, see proxy logs and privacy.
In Neurogram the proxy binding is stored with the account itself, so part of the table maintains itself — how it works.
Buy proxiespromo code NEURO — 5% off