Note: My Web pages are best viewed with style sheets enabled.
|
Unrated |
Why This Web Site Is NOT Secure
Copyright © 2017 by David E. Ross
NOTE: I use certain technical terms that appear as links to their definitions. If you select any of those links, my
Internet Glossary will appear in a separate browser window so that you will not have to keep going back and forth between pages.
There is a growing movement to have all Web sites secure. That means all Web addresses begin with https instead of http. It also means that all Web sites rely on Transport Layer Security (TLS), a protocol for secure Internet communication. TLS relies on site certificates that provide authenticated connections between servers and web browsers and secure communications between them.
My Web site, however, is not secure for several reasons.
- I do not want the bother or expense of having a site certificate. The bother arises from the fact that a site certificate has a relatively short lifetime, requiring periodic replacement with a new certificate. The expense arises from having to purchase a certificate (although there are free, very short-lived certificates available) and having my Web hosting service install it; these expenses are recurring with each expiration of a certificate.
- My Web pages contain links to other of my Web pages. I would have to edit some 450 HTML files to change those links from http to https.
- Visitors to my Web site do not encounter any need for secure communication. I do not accept inputs other than on my search page, and input to that page goes to an outside Web site that I do not control.
- This is my personal Web site, not a commercial site. The need for authentication is doubtful, especially since there is no login to access my site.
28 April 2017
David Ross home
