There are two possibilities: (a) your company wants to use
SSL or (b) your company doesn't want to use SSL.
Without SSL, there are three basic aspects of delivering Web
pages: (1) the network, (2) the pages, and (3) the Web server.
1. You received an alert about an invalid certificiate. This
would seem to indicate that the network is up and running.
2. You can look at the Web pages in code view to see if code
from another source was accidentally copied into the files.
3. You can look at your Web server configuration to see what
influence it has on delivery of your pages.
When SSL is added to the above, things become a little more
complicated. Browser settings and a certifcate authority become
part of the equation.
It is common for browsers to provide alerts or dialog boxes
when certificates are invalid. However, alerts or dialog boxes are
rarely provided when a certificate is valid.
To receive a certificate, your company provides contact
information and a fee to a certificate authority. The certificate
might last for 1, 2, or 3 years. When it expires, it is invalid. If
the company moves and doesn't update its contact infromation with
the certificate authority, the certificate is invalid. If the
certificate is assigned to "ssl.yourcompany.com" and your company
wants to use it on "secure.yourcompany.com", the certificate is
invalid. There are other reasons that a certificate might be
invalid. To determine the reason that a certificate is invalid,
your company must contact the certificate authority.
If your company previously used a certificate, you might
start with the certificate authority. If your company never used a
certificate, you might start with the information at the top of
this message.