Skip to main content
.com domains from $2.99 — WHOIS privacy at no extra charge

Hosting Terms

What is Wildcard SSL?

What Wildcard SSL really means, with the jargon taken out — plus the example that makes it obvious.

Straight answer first

A wildcard SSL certificate covers a domain and every one of its first-level subdomains — *.example.com secured by a single credential.

Below: the fuller explanation, a picture that makes it stick, why it matters in practice, and where you will actually run into it.

Written by the Hosting Seller staff · Checked 1 August 2026

100+

Terms on the shelf

2 min

Typical read

Plain

English, we promise

24/7

People if you're stuck

One certificate handles app., shop., portal. and whatever gets created next week, including subdomains that did not exist when the certificate was issued. That last part is what sets it apart from issuing a certificate per name.

The asterisk stretches exactly one level. Something like sub.sub.example.com needs its own arrangement, and the certificate is normally issued to cover the bare domain alongside the wildcard so both work.

The everyday comparison

A master key cut for every office on one floor, including the offices that have not been partitioned off yet. The floor above still needs a key of its own.

Keep that picture in mind and most of the documentation you will ever read on the subject stops being mysterious.

Why it matters if you run a site

If your architecture gives every client or tenant their own subdomain, a wildcard takes certificate paperwork out of the growth path entirely. New subdomains arrive already secured, with nothing to request.

That is the test for any technical term, incidentally — not 'do I understand it fully' but 'do I know when it is the answer to my problem'. For this one, you now do.

Wildcard SSL out in the open

A reseller's portal creates client123.theirbrand.com on demand. Each instance is ready for HTTPS the moment it exists, because the wildcard already covers it and provisioning has no certificate step at all.

Perfectly ordinary once you have seen it, which is rather the point: most hosting concepts are simple machinery wearing an intimidating name.

How this turns up in your own account

You will meet it in the control panel and occasionally in a support conversation, usually already set the right way. If this term made sense, the natural next reads are SSL Certificate, Let's Encrypt, Subdomain and HTTPS.

Backups run every day on every plan, and putting a file or a database back takes one click from the panel.

A padlock on a laptop screen standing in for a free SSL certificate

A glossary written by the people on the counter

We treat unexplained jargon as a service failure. This glossary is the support desk's accumulated translations, published where a search engine can hand them out for us.

What you pay on day one is what you pay at renewal, so the year-two invoice holds no surprises worth opening early.

  • 100+ terms, all in plain English
  • Everyday comparisons and real examples
  • Related concepts linked together
  • Written by the people on the desk

Why Hosting Seller

On every plan, as standard

The stakes spelled out

Not only what it is, but when it turns out to be the answer to a problem you are having.

Plain English first

Every term defined for people who run sites, not for other sysadmins — jargon translated rather than restated.

Linked, never siloed

Related terms cross-reference each other, so one lookup grows into a working understanding.

One term, fully landed

Wildcard SSL defined, pictured by comparison and placed in your own control panel — recognise-level in a single read.

Pictures that stick

Each concept gets a comparison you will still remember at the moment you actually need it.

The next reads, mapped

Read on into SSL Certificate and Let's Encrypt — terms rarely stand alone, so the neighbours are linked.

First Steps

From choosing to live

  1. 1

    Find it in your own account

    The quickest way to learn a hosting term is to find it in your own panel; five minutes of looking beats an hour of reading about it.

  2. 2

    Check what the defaults are

    Confirm how your account has this set. It is usually right by default here, and now you will know rather than guess.

  3. 3

    Follow the terms next door

    Concepts travel in packs — SSL Certificate, Let's Encrypt and Subdomain finish this one's picture, and each is a two-minute read away.

In the Box

Packed with every plan

  • Staging copies so changes get tested before they go live
  • SSH, Git and Composer on the plans built for developers
  • A 99.9% uptime commitment, watched by monitoring day and night
  • cPanel, the panel the rest of the trade already knows
  • Upgrades apply to the account in place, with no move between plans
  • A domain free for year one when you order annually
  • A backup taken daily, with restores you run yourself
  • One-click installs for WordPress and 400+ other applications
  • Real people on the counter, every hour of every day
  • A 30-day money-back guarantee on every hosting plan

Across the Counter

The questions we get asked most

Do I need a wildcard when free SSL already covers each subdomain?

For a handful of fixed subdomains, no — automated per-name certificates handle those perfectly well. A wildcard earns its fee when subdomains appear on demand or in bulk, at the point where issuing one at a time becomes another moving part that can jam.

Does a wildcard cover the bare domain as well?

As we issue them, yes: the certificate names example.com and *.example.com together. It is worth confirming with any issuer, though, because the asterisk on its own technically would not include the bare domain.

Can one plan hold more than a single website?

From the Pro tier upward, yes — several sites, each with its own domain, mailboxes and certificate, all under one account. If those extra sites belong to clients rather than to you, reseller hosting is the better fit: it gives each one proper separation.

Does hosting come with mailboxes?

It does — mailboxes on your own domain ship with every hosting plan, with webmail, IMAP, POP and SMTP access and spam filtering fitted as standard. There is also standalone email hosting for domains whose website lives somewhere else entirely.

Can I test changes somewhere safe first?

Yes — plans with staging let you clone the live site, work on the copy, then push it across when you are satisfied. It is the difference between hoping an update behaves and knowing that it does before any customer meets it.

Is there a refund if it does not suit?

Yes — thirty days. Put the hosting through real work, and if it is not right, ask for the money back and you get it; there is no retention script to survive first. Domain registrations are the one carve-out, because registries take that fee the moment the name is placed.

Can I bring a domain I already own?

Yes, and transfers in are routine. Unlock the name at your present registrar, collect the auth code, then start the transfer from your client area. Whatever registration time is left comes across with it, and DNS keeps answering the whole way through.

Packing up and moving host? Take our checklist.

A plain running order for a move nobody notices: what to copy first, how to carry email across without dropping a single message, when to point DNS, and the two slips behind nearly every hour of downtime we get called about.

One email carrying the checklist, then the odd note on running a site well. Step off the list whenever you like — our privacy policy spells out the rest.

Start on a plan with a plain price tag.

Free SSL, a free move in, renewals charged at the order price, and human support around the clock. That is the whole offer.

See the plans