HTTP (Hypertext Transfer Protocol) is the set of rules for transferring files (text, graphic images, sound, video, and other multimedia files) on the World Wide Web. As soon as a web user opens their browser, the user is indirectly making use of HTTP.1
What’s the difference between HTTP and HTTPS?
When using HTTPS, the computers involved in transferring the files agree on a “code” between them, and then they use that “code” to scramble the message ensuring no other computer can read them. This “code” is used on a Secure Sockets Layer (SSL), sometimes called Transport Layer Security (TLS), to send the information back and forth. This keeps information safe from hackers.
What happens if your website domain doesn’t use an HTTPS with an SSL?
- Intruders may exploit your church website, its resources, and its visitors.
- Intruders can aggregate behaviors on your website to identify the people in your church.
- Your church website may not be able to use the latest features on the internet.
With Faithlife Sites, you’ll be protected with HTTPS via an SSL certificate so your church’s website, its visitors, and your members’ information is safe and secure.
- HTTPS protects your website’s integrity by preventing hackers from altering your church’s website communication with its visitor’s browsers.
- HTTPS protects the privacy and security of your church and its members.2 For example, if a church website has a member’s directory or lists their pastor’s contact information, HTTPS keeps them protected.
- HTTPS and an SSL allow you to securely and safely collect gifts from your congregation. Learn more about how Faithlife Sites integrates with Faithlife Giving.
***
No one wants their website to be the source of a virus. Keep your church website—and its visitors—safe and secure. Get started with Faithlife Sites.
