plan_011/4
Web Hosting Gate
A first website, portfolio or brochure site with room to grow.
PKR2,199/ year
- Disk space2000 MB
- Bandwidth usage25 GB
- Email accounts10
- Sub-domainsUnlimited
- SSL certificateFree, 1 year
- Server typeLinux / Windows
TLS for websites, panels and servers
Every hosting plan we sell can run over HTTPS. The two entry shared plans and every WordPress plan come with a free certificate, while organisation-validated, extended validation, wildcard and multi-domain certificates are arranged by our sales team after we confirm exactly which names and checks you need.

Where HTTPS comes from
Which route fits depends on where your site runs and how much identity checking your visitors, partners or payment gateway expect.
The two entry shared plans and all three WordPress plans include a free domain-validated certificate on your domain. Nothing extra appears on the invoice for it.
Open guideWith root access on a VPS or dedicated server you can issue free certificates yourself using an ACME client, or let a control panel do it for you.
Open guideDV, OV, EV, wildcard and multi-domain products are ordered for you by our team. Tell us the names and the organisation details, and we handle the rest.
Hosting with a certificate included
Four yearly plans billed in rupees, Linux with cPanel or Windows with Plesk at the same price. The first two plans include a free certificate; on the larger plans our team can arrange a suitable certificate for you.
plan_011/4
A first website, portfolio or brochure site with room to grow.
PKR2,199/ year
plan_02Bestseller2/4
Company sites with corporate email and real daily traffic.
PKR2,999/ year
plan_033/4
Growing sites that need more room and more mailboxes.
PKR4,399/ year
plan_044/4
Resource-heavy sites and stores that need unlimited room.
PKR6,999/ year
Building on WordPress? Every WordPress hosting plan includes free SSL as well.
1/5 What it proves
When a browser opens https://yourdomain.pk, the server answers with its certificate before a single byte of your page is sent. The certificate contains a public key, the hostnames it is valid for, a validity window and a signature from a certificate authority. The browser checks every one of those details, and refuses or warns if anything fails.
The signature matters most. Browsers and operating systems ship with a short list of trusted root authorities. Your certificate is normally signed by an intermediate, which in turn is signed by a root. If the server forgets to send the intermediate, some phones and older systems cannot build the chain, so a correctly installed bundle is essential.
Once the chain checks out, browser and server agree on session keys using the public key in the certificate, and from then on everything is encrypted: page content, cookies, form fields and login details. The private key never leaves the server. Anyone who obtains it could impersonate the site, which is why it should stay protected.
What a certificate does not prove is that a website is honest. A phishing page can have a valid DV certificate for its own lookalike domain. The padlock only says the connection is private and the hostname matches. That is why domain names, brand protection and validation levels each play their own separate part in trust.
2/5 Validation levels
Domain-validated certificates confirm one thing: whoever requested the certificate controls the domain at that moment. The check is automated, usually through a token placed on the website or in DNS, so issuance takes minutes. For personal sites, developer portfolios, blogs, documentation and many online shops, DV is the sensible default and the type our hosting includes for free.
Organisation-validated certificates add a manual check that your company or organisation legally exists and that the person ordering is entitled to act for it. Expect to provide registration details and answer a verification call or email. The verified organisation name is written into the certificate, which procurement teams, banks and enterprise clients sometimes ask to see.
Extended validation runs a stricter and more standardised version of the same checks, with additional documents and confirmation of the requester's role. Modern browsers no longer display a green address bar for EV, so its value today lies in the verified legal details inside the certificate and in meeting contract or regulatory requirements that name EV specifically.
A practical rule: start with DV unless someone has asked you in writing for more. If a tender, payment partner or corporate customer requires organisation details, move to OV. Reserve EV for cases where it is explicitly demanded. Our team will tell you which documents each level needs before anything is ordered, so nothing is wasted.
3/5 Many hostnames
A standard certificate covers one hostname, normally with the www version included. As soon as you add shop.yourdomain.pk, api.yourdomain.pk and portal.yourdomain.pk, managing a separate certificate for each one becomes tedious, and every renewal is another chance to forget something. This is where wildcard and multi-domain products start to save real time.
A wildcard certificate is issued for *.yourdomain.pk and covers any single-level subdomain under it, including ones you create next month. It does not cover deeper levels such as a.b.yourdomain.pk, and the bare domain is typically added as an extra name. Wildcards suit SaaS dashboards, staging environments and agencies that spin up client subdomains often.
Multi-domain products, known in the trade as SAN or UCC certificates, carry a list of unrelated names, so acme.pk, acme.com.pk and acme.com can all sit on one file. It is handy when one server answers for a brand registered under several extensions, or when a mail server and web server share a single IP address and certificate.
The trade-off is shared fate. If the private key of a wildcard or multi-domain certificate leaks, every name on it is exposed and all of them must be reissued together. For setups spread across several servers or teams, separate certificates per service can be safer. Tell us how your infrastructure is laid out and we will suggest a sensible split.
4/5 Check it yourself
You do not need to trust the padlock icon alone. From any Linux or macOS terminal, or from Windows with OpenSSL installed, run: openssl s_client -connect yourdomain.pk:443 -servername yourdomain.pk. The output shows the full chain the server sends, the hostnames on the certificate and whether verification succeeded. Look for the line Verify return code: 0 (ok).
To see just the validity dates, pipe the output onward: openssl s_client -connect yourdomain.pk:443 -servername yourdomain.pk < /dev/null | openssl x509 -noout -dates -subject -issuer. The notAfter value tells you when the certificate expires, and the issuer tells you which authority signed it. It is a quick way to confirm a renewal actually reached the server.
For a broader view of how the site behaves over HTTPS, curl -vI https://yourdomain.pk prints the negotiated TLS version, the certificate subject and the response headers, including any redirect or Strict-Transport-Security header. Running curl -I http://yourdomain.pk shows whether plain HTTP requests are redirected to HTTPS with a 301 response, which they should be.
If something looks wrong, such as an incomplete chain, an unexpected hostname or an expiry date that has already passed, copy the command and its output into a support ticket. Exact output lets our engineers see what your visitors' browsers see, and it usually shortens a long back-and-forth into a single reply with the fix.
5/5 Going HTTPS-only
Installing a certificate is only half the job; the site also has to use it everywhere. Begin by confirming HTTPS works on every hostname you serve, with and without www. Then update your application's base URL, for example the WordPress Address and Site Address settings, so that new links are generated with https:// from the start.
Next, add a permanent 301 redirect from HTTP to HTTPS. On Apache hosting this is a few lines in .htaccess, on Nginx a server block that returns 301, and on Plesk a single checkbox. Use 301 rather than 302 so search engines transfer existing rankings to the new addresses instead of treating them as a temporary detour.
Then tidy up the signals around the site. Submit the HTTPS version in Google Search Console, regenerate your sitemap so every URL starts with https://, update canonical tags, and change links in social profiles, email signatures and ads where you can. Old links will still work thanks to the redirect, but direct links save a hop.
Only after everything has been stable for a while should you consider HSTS, the header that tells browsers to refuse plain HTTP for your domain. It is a good protection, but once a long max-age is cached, a broken certificate makes the site unreachable for returning visitors. Start with a short max-age and increase it gradually.
Certificate types compared
Encryption strength is the same in every column. What changes is the identity checking and the number of names covered.
| Certificate | What is checked | Names covered | Typical fit | How to get it |
|---|---|---|---|---|
| Free DV (bundled) | Domain control only | Domain and www | Blogs, portfolios, small shops | Included on entry shared and all WordPress plans |
| Paid DV | Domain control only | Domain and www | Sites wanting a vendor-backed product | Arranged by our sales team |
| OV | Domain plus registered organisation | One or more names | Company portals, B2B services | Arranged by our sales team |
| EV | Stricter, standardised organisation checks | One or more names | Contracts or regulators that require EV | Arranged by our sales team |
| Wildcard | DV or OV level | All single-level subdomains | SaaS, staging, client subdomains | Arranged by our sales team |
| Multi-domain | DV, OV or EV level | A list of different domains | One brand on .pk, .com.pk and .com | Arranged by our sales team |
After installation
Certificate lifetimes keep getting shorter across the industry, which is good for security and bad for anyone relying on a calendar reminder. Free certificates are short-lived by design and are meant to renew automatically, while paid ones have a fixed end date. Either way, the safest assumption is that a renewal will one day fail quietly, so watch for it.
A simple monitor helps. A cron job on a VPS that runs the openssl date check shown above once a day and emails you when fewer than fourteen days remain costs nothing and catches most surprises. External uptime checkers can do the same from outside your network, which also covers the case where the server itself is down.
Renewals usually break for predictable reasons: DNS was moved and the validation record vanished, a redirect rule blocks the challenge path under /.well-known/, or a firewall drops traffic from the authority. If your padlock turns into a warning, check those three first, then send us the output so we can look at the server side with you.
Paid certificates
Paid certificates are not sold through an online price list here, because the right product depends on your names, your server and the checks your organisation can complete.
Arranged by our team
Send us the hostnames you want covered, where the site runs (our shared hosting, a VPS, a dedicated server or elsewhere), and whether you need organisation or extended validation. We reply with the suitable product, the documents the authority will ask for and a quote, and nothing is ordered until you confirm.
Write down every name visitors and applications actually use, including www, mail and API subdomains, so the certificate covers all of them from the start.
On shared hosting the panel creates both for you. On a VPS, openssl req -new -newkey rsa:2048 -nodes produces a key and request; keep the key file private.
DV finishes once a DNS record or file is in place. OV and EV need organisation details and a verification contact who answers promptly.
Add the certificate with its intermediate bundle, reload the web server and confirm the chain with openssl s_client before announcing the change.
Certificate help
NAME
support — ask us in plain words, in English or Urdu, and we explain what to prepare and what happens next.
SYNOPSIS
PHONE
Usually, yes. On shared hosting you paste the certificate, its private key and the intermediate bundle into the SSL section of cPanel or Plesk, and the panel matches them together. On a VPS you place the files wherever your web server expects them. The one thing you cannot do without is the private key created with the original CSR; if it is lost, the certificate has to be reissued against a new key.
Almost always the culprit is mixed content: the document itself arrives encrypted, yet some asset on it, perhaps a logo, a font or a tracking script, is still fetched from an http:// address. The browser downgrades the padlock because part of the page travelled unencrypted. Open developer tools, check the console for blocked or insecure requests, then update those links in your theme, database or page builder to https:// or to relative paths.
Yes. The cipher suites and key sizes are negotiated by the browser and your server, not by the price of the certificate, so a free domain-validated certificate protects traffic just as well as an expensive one. What a paid product adds is identity checking on the organisation, broader name coverage such as wildcards, and in some cases a warranty offered by the certificate authority.
It does. Without encryption, anyone on the network path can inject adverts or scripts into your pages or swap a download link, and visitors would never know. Browsers also mark every plain HTTP page as not secure, which costs trust even on a simple brochure site. Features such as HTTP/2, geolocation and service workers only work over HTTPS, so leaving it off quietly limits what your site can do.
On a VPS or dedicated server you have root access, so you can issue a free certificate yourself with an ACME client such as certbot, or through cPanel, DirectAdmin or Plesk if you run one. For a paid certificate, our team handles the order and validation, and you install the issued files on your web server. If you get stuck, open a ticket with the server name and the error you see.
A website certificate secures connections to the hostname it names. Mail clients should connect over encrypted IMAP, POP3 and SMTP, which uses the certificate of the mail server they talk to, so your password and messages are protected on the way there. If you prefer to use mail.yourdomain.pk as the server name, ask us to confirm that the name is covered so the mail client does not show a warning.
Free certificates are renewed by proving control of the domain, usually through a file on the website or a DNS record. If your DNS moves elsewhere but the A record still points to our server, the file check keeps working. If the domain points somewhere else entirely, the certificate on our server can no longer renew, and the new host has to issue its own certificate.
Yes. A certificate only depends on the domain name and, for business-validated products, your organisation details, not on what the site contains. Many customers start validation early because OV and EV checks can take a few working days. Keep in mind that the validity period starts when the certificate is issued, and that once it has been issued the order counts as provisioned and cannot be refunded.
PKDomain.net · help in English & Urdu
Tell us which names you want secured and where they are hosted. Our team replies in English or Urdu with a recommendation, and we can review an existing setup if browsers are already showing warnings.