There's a Secure Sockets Layer (SSL) certificate in place, effective for about another 6 months.
A utility website,
http://whynopadlock.com (enter net54baseball.com and click the "I'm not a robot" checkbox) shows that all the pieces of the puzzle are in place except one:
"Protocols: You currently have TLSv1 enabled. This version of TLS is being phased out. This warning won't break your padlock, however if you run an eCommerce site, PCI requirements state that TLSv1 must be disabled by June 30, 2018."
This doesn't sound like something we can fix ourselves, and the web hosting system administrators should probably do something about it.
What we found on the OBC site was that if there are any references to "http://" in any script producing a web page in the net54baseball.com domain, they should be changed to "https://" in the program script files. OBC had several dozen of those protocols that needed to be changed. I don't think users can easily change the vBulletin script files, and any changes would be overwritten when a newer version of vBulletin is installed.
In the meantime, as Leon said, even though the browser warns "Not secure," it'll behave like a regular secure website.
Best,
WMD
Wayne Delia, Webmaster, OBC (Old Baseball Cards),
https://oldbaseball.com