Plan 01
WP 1
A first WordPress blog or brochure site.
PKR2,699per year
Order now WP 1 →- Disk space1 GB
- Bandwidth usage25 GB
- Email accounts10
- Sub-domains5
- MySQL databases1
- SSL certificateFree
SSL for company websites
Every business website needs HTTPS, but not every business needs the same certificate. Free SSL comes with our entry shared and WordPress hosting, and our sales team arranges domain-validated, organisation-validated, extended-validation, wildcard and multi-domain certificates for companies with stricter requirements.

Certificate types we can arrange
Validation level and coverage are separate decisions. First decide how much identity checking you need, then decide how many names the certificate must protect.
Included on the two entry shared plans and every WordPress plan. Ideal for company brochure sites, blogs and small catalogues that need the padlock and nothing more.
Read moreConfirms control of the domain only. A paid DV certificate suits sites hosted outside our entry plans or companies that prefer a commercial issuer.
The certificate authority checks that your company legally exists, and the verified organisation name appears in the certificate details.
The most thorough identity checks, often requested by banks, payment partners and large corporate buyers who review supplier certificates.
Protects a domain and all its subdomains at one level, such as portal, shop and support, under a single certificate and renewal.
Covers several different names on one certificate, useful when a company runs related sites on .pk, .com and .biz versions.
Free SSL included
All three yearly WordPress plans, billed in rupees, include free SSL. The two entry shared hosting plans include it as well, listed on our shared hosting page.
Plan 01
A first WordPress blog or brochure site.
PKR2,699per year
Order now WP 1 →Plan 02Bestseller
Growing WordPress sites with more media and traffic.
PKR3,999per year
Order now WP 2 →Plan 03
High-traffic WordPress sites and stores that need unlimited room.
PKR6,199per year
Order now WP 3 →Running a non-WordPress site? See the shared hosting plans for small businesses, where the two entry plans also carry free SSL.
Section 1 of 5 · Validation levels
Every SSL certificate does two jobs. It encrypts the connection between the visitor and the server, and it tells the browser who the certificate was issued to. The encryption part is the same across certificate types. The difference between DV, OV and EV lies entirely in how much the certificate authority checked before putting its name behind that identity claim.
A domain-validated certificate proves only that whoever requested it controls the domain, usually by responding to an email or placing a record in DNS. It says nothing about the business behind the site. For most company websites, that is sufficient: visitors see the padlock and the connection is protected.
Organisation validation adds a check on the company itself. The certificate authority confirms the legal entity from official records and includes the verified organisation name in the certificate. Extended validation goes further, with stricter checks on the entity, its physical existence and the authority of the person placing the order.
The right level depends on who inspects your certificate. If customers simply browse and fill in forms, a free or DV certificate is enough. If a bank, payment processor, government buyer or multinational client reviews your security posture as part of onboarding, they may ask for OV or EV specifically, and it pays to know before the deadline.
Section 2 of 5 · Certificate governance
Certificates are tied to a private key, a small file that must stay secret on the server. In many companies that key was generated by a freelancer or an agency, stored on their own machine and never handed over. When the certificate needs renewing or moving to a new server, nobody inside the company knows where the key is.
Treat certificates as company assets, just like domains. Place orders in the company name, use a role-based email address for validation and expiry notices, and record each certificate in your IT documentation with the names it covers, where it is installed, who issued it and when it expires.
Keep the private key where your own IT team can reach it, protected by the same controls as other system credentials. Do not email keys around or paste them into chat. If an outside developer installs a certificate for you, ask for confirmation of where the key lives and how your team can access it later.
Review certificates when people leave. A departing employee or agency may have had access to keys, validation mailboxes or the account used to order certificates. Changing those credentials, and reissuing a certificate where there is any doubt, is far cheaper than dealing with a compromised key or an unexpected expiry months later.
Section 3 of 5 · Expiry planning
An expired certificate is one of the most visible failures a company website can suffer. Browsers display a full-page warning, many visitors leave immediately and online forms, logins and payment pages stop working for anyone who heeds the warning. Customers rarely understand the cause and simply assume something is wrong with the business.
Paid certificates have fixed validity periods, and the industry has been steadily shortening them, which means renewals come round more often than many IT teams expect. Record every expiry date in the same calendar or register you use for domain renewals, and set reminders well ahead rather than relying on notices from the issuer.
OV and EV renewals take longer than DV, because the certificate authority repeats or confirms its company checks. Start those renewals early, particularly if your company has changed its registered details, moved premises or changed directors since the last validation, as any mismatch can delay issue.
Assign one person to own the renewal of each certificate and give them a deputy. Many expired certificates are not the result of neglect but of a renewal email that went to someone on leave. Two names on the task, and a role-based address on the order, remove most of that risk at almost no cost.
Section 4 of 5 · Coverage choices
Coverage describes which hostnames the certificate protects. A single-name certificate typically covers the main domain and its www version. That is the simplest option and works perfectly for a company with one website on one domain, which is still the most common arrangement among small and medium businesses.
A wildcard certificate covers every subdomain at one level, so a single certificate protects portal, careers, support and any new subdomain you add later. It reduces administration for companies with many subdomains, but it also means one private key is shared by all of them, which affects how carefully that key must be guarded.
A multi-domain certificate lists several distinct names, which might be your .pk and .com addresses, a .biz version of the brand and a product site. It is convenient when those names are served from the same infrastructure, though every change to the list usually means reissuing the certificate.
There is no universally correct answer. Draw a quick map of your domains and subdomains, note which servers they run on and how sensitive each one is, then choose the coverage that keeps sensitive systems separate while minimising the number of renewals. Our sales team can review that map with you before you order.
Section 5 of 5 · Beyond the padlock
A certificate protects data while it travels between the visitor and the server. It does not protect the server itself, the application running on it or the passwords your staff choose. A site can show a perfect padlock while running an outdated plugin, a weak administrator password or a contact form that anyone can abuse.
On our shared hosting, server-side protections help cover some of that ground: servers are updated regularly, with firewalls, brute-force protection, malware scanning, account isolation and regular server-side backups. Your own team still needs to keep the website software current and remove administrator accounts that are no longer used.
Email is a separate concern. HTTPS on the website does not secure your mail, and customers judge your business by the email they receive as well as the site they visit. Make sure the records that authenticate your domain mail are correct, so messages from your staff are not treated as suspicious.
Finally, remember that the padlock appears on fraudulent sites too, because domain validation is easy to obtain. That is one reason brand protection matters: registering obvious lookalike domains makes it harder for anyone to put a convincing, certificate-protected copy of your company website in front of your customers.
Side-by-side overview
Use this table as a starting point for an internal discussion. Our sales team will confirm what is available for your specific domains and how validation will work.
| Option | What is checked | Names covered | Typical business use | How to get it |
|---|---|---|---|---|
| Free SSL with hosting | Domain control | The hosted site | Company sites on entry shared or WordPress plans | Included with the plan |
| Paid DV | Domain control | Usually one name | Sites on servers or larger plans | Arranged by sales |
| OV | Domain and legal entity | One or several names | Supplier onboarding, corporate portals | Arranged by sales |
| EV | Domain, entity and extra checks | One or several names | Finance, payments, large enterprise buyers | Arranged by sales |
| Wildcard | Depends on validation level | All subdomains at one level | Companies with many subdomains | Arranged by sales |
| Multi-domain | Depends on validation level | A list of different names | Brands across .pk, .com and .biz | Arranged by sales |
Ordering a paid certificate
Arranged by our team
Tell us which domains and subdomains need protecting, where they are hosted, and whether a client or partner has asked for a particular validation level. We will recommend a certificate, explain the documents the issuer is likely to request and confirm the current price before anything is ordered. No refunds apply once a certificate has been issued, so we check the details with you first.
Before you request a quote, it helps to sort your sites into two groups. The first group is public information pages: the company profile, product brochures, news and careers. These need encryption and a valid padlock, and for most organisations the free certificate on an entry shared or WordPress plan covers them completely. The second group is anything where a third party judges your company by its certificate: supplier portals, client login areas, payment pages and systems a bank or auditor will review. That second group is where an organisation or extended validation certificate earns its cost.
Write down who requested the higher validation level and why. When the renewal comes round in a year or two, nobody will remember that a particular corporate client insisted on EV, and the certificate may be downgraded by mistake, or renewed at a higher level long after the requirement disappeared. A one-line note in your IT register, next to the certificate expiry date, saves that debate.
Finally, think about where the certificate will be installed. Certificates for websites on our hosting can be handled together with your plan. For a VPS or dedicated server your own team manages, we can arrange the certificate, while installation follows your server administrator's process. Payment for any certificate can be made by bank transfer, mobile wallet, card, PayPal or international transfer, with an invoice in your company name.
A practical checklist
Validation goes faster when the details on your order match public records exactly. Before contacting sales, gather the information the certificate authority is likely to compare against official sources, and decide who in the company will answer verification calls or emails.
Delays almost always come from small mismatches: a trading name used instead of the registered name, an outdated phone number in a business directory or a validation email sent to an inbox nobody reads.

SSL FAQ
Free SSL is included on the two entry shared hosting plans and on every WordPress plan. If your company website runs on one of those, you do not need to buy a separate certificate for basic HTTPS. Larger shared plans, servers and sites hosted elsewhere can still use a paid certificate arranged through our sales team, or you can ask which option fits your setup.
No. The encryption strength a visitor receives depends on the server configuration and the browser, not on the validation level. What a paid organisation or extended validation certificate adds is verified information about your company inside the certificate. That matters to procurement teams, banks and partners who inspect certificates, but it does not make the connection itself any harder to break.
Requirements are set by the certificate authority that issues the certificate, not by us, and they vary by product. Expect to prove that the company legally exists, that the details on the order match official records and that the person requesting the certificate is authorised to do so. Our sales team will tell you what the chosen authority asks for before you pay.
A multi-domain certificate can protect several different names on a single certificate, which suits companies running the same site or related services across several extensions. Whether it is the best choice depends on how those domains are hosted and how often the list changes. Share the names and their hosting arrangements with our sales team for a recommendation.
Use a role-based address such as it@ or security@ on your own domain, monitored by more than one person. Certificate authorities send validation requests and expiry notices to the contacts on the order, and those messages are easy to miss when they go to an individual who is on leave or has left. The same rule applies to domain registrant contacts.
It can be, which is why it should be used thoughtfully. A wildcard certificate shares one private key across every subdomain it covers, so if that key leaks from one server, all those subdomains are affected. Companies with sensitive systems often keep separate certificates for payment or staff portals and use a wildcard only for lower-risk subdomains.
Discuss it with our support team first. Installation depends on where the website is hosted and what access is available. On our hosting, we can usually help as long as you have the certificate files and the matching private key. If you are unsure whether you still have the private key, ask before ordering anything new, as that determines what is possible.
No. Our policy is that there are no refunds once a service has been provisioned, and an issued certificate counts as provisioned. That is why we confirm the certificate type, the names it covers and the validation requirements with you before you pay. Taking a few minutes to check the domain list and the company details avoids costly mistakes.
PKDomain.biz · Business desk
Start with free SSL on our entry shared or WordPress hosting, or ask our sales team about OV, EV, wildcard and multi-domain certificates for stricter requirements.