Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
It produced this output: Your connection is not private
Attackers might be trying to steal your information from www.techecons.org (for example, passwords, messages, or credit cards). Learn more
NET::ERR_CERT_COMMON_NAME_INVALID
It asked me to return to safety . But I being owner, I proceeded to the 'unsafe' and got to the website. An invited reader would not have proceeded.
My web server is (include version):
The operating system my web server runs on is (include version): I dont know (Linux?)
An ancient certificate from 2016 for a different hostname is configured at the server of your website. The same certificate is presented by the server when using random hostnames, so it's probably the default certificate and not specifically configured for your website.
Did you somehow enable HTTPS, SSL or TLS in the control panel of your website? Your hosting provider claims "Free Wildcard SSL Certificates" for "StackCP Linux Cloud Hosting". Check the site of your hosting provider to see how to enable it or open a ticket for help. There's not much we can do about it I'm afraid.