Custom domains

Miraheze can make wikis available on custom domains (like wiki.example.org) on request. The only things we need is you to follow the below steps, and have an SSL certificate for your wiki (no SSL certificate → no custom domain). You can either use your own SSL Certificate (see below) or we can create one for you using Let's Encrypt, which is a process we handle entirely without intervention/additional work from you other than pointing the domain to our server (so it is easier).

You can use a custom domain by setting a CNAME entry for the domain or subdomain that you intend to use for your wiki: Add a CNAME on the subdomain you want (e.g. "wiki."), and point it to "mw-lb.miraheze.org";

If you are using Cloudflare for DNS server, please visit Cloudflare>Special:MyLanguage/Custom domains/Cloudflare|Cloudflare page to see how to do it. Submit a phab>Special:MyLanguage/Phabricator|Phabricator request using phabreq>phab:maniphest/task/edit/form/14/|this form to request a certificate signing request (and attach your certificate)

You may wish to set the nameserver of your domain to Miraheze. Be aware that any services used with your domain will become unavailable and you will not be able to control the domain you are using.

Note: if you already host a website on this domain, it will become unreachable. Change the name servers to "ns1.miraheze.org" and "ns2.miraheze.org" (contact your domain registrar if you don't know how to do this); Submit a phab>Special:MyLanguage/Phabricator|Phabricator request using phabreq>phab:maniphest/task/edit/form/14/|this form to request a certificate signing request (and attach your certificate)

If you have chosen your own SSL certificate: A system administrator who handles your CSR request will shortly after generate a CSR & private key (for use at our own servers), and the requested CSR will be emailed to you. You use this CSR to request your SSL certificate vendor to generate an SSL certificate with the CSR we gave you. You will need to email us the generated SSL certificate when this is done. If all of these steps are done, we will add the custom domain to your wiki, and we will notify you when this all is done.

If you have chosen the option of us creating it (Let's Encrypt): There is nothing left for you to do! A system administrator will take care of all the remaining steps, including renewing them.

Need help with any of the steps or have a question? reception>User:Reception123|Reception123 or paladox>User:Paladox|Paladox can help you.

URL structure
Note that Miraheze is configured not to serve pages from the domain root. E.g. if your wiki is, and its main page is called "Welcome", then the URL will not be  , but instead   (note the   piece). Likewise, even if you use a custom domain, Miraheze will still serve pages with this URL structure. So if you control  and you request that your Miraheze wiki use a custom domain e.g. , then your "Welcome" page will have the URL.

Free subdomains
If you don't wish to pay for a domain of your own, there are services that offer free subdomains, which you can use instead. Note that Miraheze wikis automatically get a free subdomain of miraheze.org, so using a third-party service is only necessary if you prefer something different (e.g. a service that has a very short or easy to spell second-level domain).


 * Available sites :
 * [https://freedns.afraid.org FreeDNS]
 * [https://www.freenom.com/en/freeandpaiddomains.html</> Freenom]

SSL Certificate Authority
Miraheze accepts most SSL certificate authority that are accepted by browsers such as Mozilla Firefox. However, we do not accept WoSign certs anymore.

Current authority used by Miraheze custom domains
Below is a list of the current SSL certificate authority used by custom domains. This does not mean that others not in this list are not accepted.


 * Let's Encrypt - managed by Miraheze, all steps regarding Let's Encrypt (except setting nameservers) are done by Miraheze Sysadmins
 * Cloudflare (Note: additional restrictions apply. Click the link for details)
 * Comodo
 * Gandi
 * GeoTrust
 * GlobalSign
 * GoDaddy
 * RapidSSL