HTTPS

How it works

• It is HTTP wrapped in TLS encryption, backed by a certificate.
• Visitors see the padlock and the address starts with https.
• Browsers warn on pages without it, and search engines favour sites that have it.
• A lapsed certificate triggers a full-page warning that sends visitors away.

What can go wrong (example scenario)

A four-person consulting firm's site loaded over HTTP. Chrome showed a “Not secure” label beside their name. A prospect mentioned it on a call and asked whether the firm took security seriously. The site had nothing wrong with it except the missing certificate.

How WILDCARD handles it

Managed Hosting runs the site with HTTPS on and HTTP redirected. Domain Security keeps the DNS behind it correct.

• A retailer's product pages must be HTTPS so shoppers trust the checkout and search engines rank them.
• A law firm's site has a mix of HTTP images on an HTTPS page, and browsers show a warning until every asset is fixed.
• A non-profit's donation form embedded from a third party must itself be HTTPS.

Example scenario: A small physiotherapy clinic noticed bookings dropping. Their site loaded over HTTPS on the www address but plain HTTP on the bare domain, which is what the Google listing used. Visitors saw a warning and left. A redirect from HTTP to HTTPS on both addresses brought the bookings back.

A question owners ask

My site is just a brochure. Does it still need HTTPS?

Yes. Browsers flag HTTP pages, search engines rank them lower, and HTTPS also stops anyone from altering your page in transit. It is free with most hosts.