{"id":22581,"date":"2026-08-28T12:36:12","date_gmt":"2026-08-28T10:36:12","guid":{"rendered":"https:\/\/www.curiaweb.ch\/?post_type=docs&#038;p=22581"},"modified":"2026-08-28T12:36:12","modified_gmt":"2026-08-28T10:36:12","password":"","slug":"create-subdomain","status":"publish","type":"docs","link":"https:\/\/www.curiaweb.ch\/en\/hilfe\/webhosting-cpanel\/subdomain-erstellen\/","title":{"rendered":"Create subdomain in cPanel"},"content":{"rendered":"<p class=\"wp-block-paragraph\">A subdomain is an additional address beneath your existing domain. This allows you to run, for example, a shop, a customer area, a development environment, or a separate web application under its own address.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">From the domain:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>example.com<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">can, for example, the subdomain:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>shop.example.com<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">become.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In this guide, we will show you step by step how to create a subdomain in the CURIAWEB cPanel, a suitable <strong>Document Root<\/strong> you define and then check whether the subdomain is correctly set up and reachable.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Important:<\/strong> A subdomain is a separate hostname. It is not the same as a subdirectory of a website. <code>shop.example.com<\/code> and <code>example.com\/shop\/<\/code> are technically different addresses.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">What is a subdomain?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A subdomain extends an existing domain with an additional name in front of the actual domain.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Main domain:\nexample.com\n\nSubdomain:\nshop.example.com\n\nFurther possible subdomain:\nsupport.example.com<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The part <code>shop<\/code> or rather <code>support<\/code> is the respective subdomain.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What can a subdomain be used for?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A subdomain is particularly suitable for content or applications that are to be logically separated from the main website.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Typical examples are:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>shop.example.com<\/code> for a separate online shop<\/li>\n\n\n\n<li><code>support.example.com<\/code> for a support section<\/li>\n\n\n\n<li><code>portal.example.com<\/code> for a customer portal<\/li>\n\n\n\n<li><code>dev.example.com<\/code> for a development environment<\/li>\n\n\n\n<li><code>test.example.com<\/code> for a test website<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Which term makes sense depends on the respective application.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Distinguish between subdomain and subdirectory<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A subdomain:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>shop.example.com<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">is not the same as:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>example.com\/shop\/<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The second variant is a path or subdirectory within the main domain.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Simplified:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>shop.example.com\n\u2192 own hostname\n\nexample.com\/shop\/\n\u2192 path within example.com<\/code><\/pre>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Briefly explained:<\/strong> Although a subdomain can load website files from a subdirectory, this does not technically make it a normal URL subdirectory.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">Distinguish between subdomain and independent domain<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">An additional independent domain is also something different than a subdomain.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>example.com\n\u2192 Domain\n\nshop.example.com\n\u2192 Subdomain of example.com\n\nexample-shop.com\n\u2192 independent domain<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">We explain how to set up an additional independent domain at <a href=\"\/en\/help\/web-hosting-cpanel\/add-and-manage-domain\/\">Add and manage a domain in cPanel<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What is the document root of a subdomain?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The <strong>Document Root<\/strong> determines from which directory the web server delivers the content of the subdomain.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, a possible configuration could look like this:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>shop.example.com\n        \u2193\npublic_html\/shop\/\n        \u2193\nWebsite files of the shop<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">A visitor calls:<\/p>\n\n\n\n<figure class=\"wp-block-embed\"><div class=\"wp-block-embed__wrapper\">\nhttps:\/\/shop.example.com\n<\/div><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">in this example, the website files are from:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>public_html\/shop\/<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">used.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">1. Log in to cPanel<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Log in to your CURIAWEB cPanel.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Then open:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Domains \u2192 Domains<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You can manage the domains and subdomains designated for your hosting account via the central domain management.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">2. Check existing domains and subdomains<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">First, check if the desired subdomain already exists.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, if:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>shop.example.com<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">already been set up, you should not create another similar entry, but first check the existing configuration.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">3. Create new domain<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In domain management, select the function to create a new domain.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Even a subdomain is specified by its full hostname in the process.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">4. Enter the full name of the subdomain<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Enter the desired subdomain completely.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>shop.example.com<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Do not use:<\/p>\n\n\n\n<figure class=\"wp-block-embed\"><div class=\"wp-block-embed__wrapper\">\nhttps:\/\/shop.example.com\n<\/div><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">and not just:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>shop<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">provided the input mask expects the full domain name.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Important:<\/strong> In cPanel domain management, enter the hostname without <code>http:\/\/<\/code>, <code>https:\/\/<\/code> and without a trailing URL path.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">5. Check document root<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Specify the directory from which the subdomain should load its website files.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>shop.example.com<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">could, for example, use a dedicated directory:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>public_html\/shop\/<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">What matters is not the specific name of the directory, but that you know later which website files are located there.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Subdomain with its own website<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the subdomain is to contain an independent website or application, a separate document root makes sense.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>example.com\n\u2192 public_html\/\n\nshop.example.com\n\u2192 public_html\/shop\/<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This keeps the website files logically separated from each other.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Do not accidentally use a shared document root<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">cPanel can offer an option when creating a domain to share the document root of an existing domain.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the subdomain is to have an independent website, you should check this setting carefully.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A configuration like:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>example.com\n\u2192 public_html\/\n\nshop.example.com\n\u2192 public_html\/<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">would basically result in both hostnames using the same website file base.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Attention:<\/strong> If the subdomain is to have a separate website, it must not accidentally use the same document root as the main website.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">6. Create subdomain<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Check again before creating:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>full name of the subdomain<\/li>\n\n\n\n<li>associated main domain<\/li>\n\n\n\n<li>designated document root<\/li>\n\n\n\n<li>whether a separate or shared document root is used<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Then create the domain or subdomain.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">7. Check subdomain in the domain overview<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">After creation, the subdomain should be under:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Domains \u2192 Domains<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">displayed.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check the assigned document root there in particular.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">8. Open document root in file manager<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Then open:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Files \u2192 File Manager<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Navigate to the document root of the subdomain.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If this, for example,:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>public_html\/shop\/<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">is, the website files of the subdomain belong in this directory.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A detailed guide on file management can be found at <a href=\"\/en\/help\/web-hosting-cpanel\/use-cpanel-file-manager\/\">Use cPanel File Manager<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">9. Deploying website files<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If you want to run an existing website on the subdomain, upload the corresponding files to the document root.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For a simple website, this could be, for example:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>index.html<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">or:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>index.php<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">lie.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For a web application, its complete files and, if applicable, additional components must be present.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Subdomain shows the same website as the main domain<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If you expected a standalone website, but the subdomain displays the same content as the main domain, you should check the document root first.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Both may be using the same folder.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check under:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Domains \u2192 Domains<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">which directory was actually assigned to the subdomain.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Subdomain is not showing any website<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the subdomain has been set up in principle, but no website appears, check the document root in the file manager.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check in particular whether the expected website files and a suitable start file are present there.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Common mistake:<\/strong> The subdomain has been set up correctly, but the website files are still located in a different directory.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">10. Understanding subdomain DNS<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">For a subdomain to be publicly accessible, its DNS resolution must also lead to the correct hosting environment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The domain configuration in the web server and the public DNS resolution are two different components.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Simplified:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>shop.example.com\n        \u2193\nDNS\n        \u2193\nHosting server\n        \u2193\ncPanel domain configuration\n        \u2193\nDocument root\n        \u2193\nWebsite<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">DNS is managed within cPanel<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the DNS zone of the main domain is managed via your CURIAWEB cPanel, you can find the existing records under:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Domains \u2192 Zone Editor<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">check.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We explain the complete operation at <a href=\"\/en\/help\/web-hosting-cpanel\/dns-zoneneditor-verwenden\/\">Using the DNS Zone Editor in cPanel<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">DNS is managed externally<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the nameservers or DNS zone are managed by an external provider, creating the subdomain in cPanel alone might not be sufficient.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The required DNS record must then be set up in the actually authoritative DNS zone.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Important:<\/strong> What matters is where the domain's DNS zone is actually managed. An entry in the cPanel zone editor has no public effect if different authoritative nameservers are used for the domain.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">A-Record or CNAME?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Subdomains can be resolved via different DNS records depending on the desired configuration.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A <strong>A-Record<\/strong> resolves a hostname to an IPv4 address.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A <strong>CNAME<\/strong> points one hostname to another hostname.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Which variant makes sense for your subdomain depends on the specific hosting and DNS configuration.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Do not change DNS records on a hunch if you do not know which existing configuration will be replaced by it.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Subdomain unreachable: Check DNS<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the browser cannot resolve the subdomain at all, you should check the DNS configuration in particular.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If, on the other hand, a website or server message already appears, the request is fundamentally reaching a target system.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This distinction helps with troubleshooting.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">DNS changes can take time<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If a DNS record for the subdomain has just been created or modified, cached DNS information may temporarily still return the previous state.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">As a result, the subdomain might already work on one device while not yet working over a different internet connection.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">11. Test subdomain HTTPS<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">After the subdomain points to the correct hosting environment, you should also test it via HTTPS.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<figure class=\"wp-block-embed\"><div class=\"wp-block-embed__wrapper\">\nhttps:\/\/shop.example.com\n<\/div><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">When a certificate warning appears, you should check DNS, domain mapping, and certificate status separately.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The SSL certificate of the main domain does not automatically apply to every subdomain<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">An SSL certificate must cover the respective hostname.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>example.com<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">works via HTTPS, therefore does not automatically prove that also:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>shop.example.com<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">is already covered by a valid certificate.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Important:<\/strong> Explicitly test a newly set up subdomain with its own full hostname via HTTPS.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">Test website on subdomain<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Open the subdomain in your browser.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Then check not only the home page, but for a web application also important subpages and functions.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For a standalone WordPress installation, the following can be checked, for example:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Home<\/li>\n\n\n\n<li>Subpages<\/li>\n\n\n\n<li>WordPress Login<\/li>\n\n\n\n<li>Administration area<\/li>\n\n\n\n<li>Images and other media files<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Use subdomain for WordPress<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A subdomain can contain a completely independent WordPress installation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>www.example.com\n\u2192 Main website\n\nshop.example.com\n\u2192 separate WordPress or WooCommerce installation<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The separate installation can use its own files, its own database, and its own configuration.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">A subdomain is not automatically a separate WordPress installation<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The creation of:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>shop.example.com<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">does not install WordPress automatically.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Initially, the subdomain provides the hostname and its assignment to the hosting.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The desired web application must then be set up separately in the designated document root.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Subdomain for a test website<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A subdomain like:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>test.example.com<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">can technically be used for a test or development environment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, you should also take into account that a publicly accessible test website can in principle also be reached via the internet.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, use appropriate access restrictions for non-public development environments.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Protect test environment with a password<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If a development or test website should not be publicly accessible, you can additionally protect the folder in question.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We explain the procedure under <a href=\"\/en\/help\/web-hosting-cpanel\/password-protect-folder\/\">Password protect folders in cPanel<\/a>.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Practical Tip:<\/strong> A hard-to-guess subdomain like <code>test123.example.com<\/code> is not a substitute for real access restriction.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">Subdomain and search engines<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If you operate a test environment under a publicly accessible subdomain, you should not rely solely on search engines \u201enot finding it.\u201c.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A test website can be discovered via links, sitemaps, or other ways.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For confidential or non-public content, a technical access restriction is the more reliable solution.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">subdomain for a customer area<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">An address like:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>portal.example.com<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">can be used for a customer area.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, the subdomain itself does not provide access security.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Authentication and permissions must be handled by the deployed application or an additional protective function.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Use subdomain for email?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In principle, a subdomain can also be used for services other than websites.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Creating a website subdomain in cPanel does not automatically set up email accounts, mail routing, or other services for this hostname.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">DNS, website, and email should be considered as separate technical areas.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Redirect subdomain<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the subdomain should not contain its own website, but rather simply redirect visitors to another address, a redirection may make more sense.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>shop.example.com\n        \u2193\nRedirect\n        \u2193\nhttps:\/\/www.example.com\/shop\/<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">We explain how to set up redirects in cPanel at <a href=\"\/en\/help\/web-hosting-cpanel\/domain-umleitung-einrichten\/\">Set up domain redirection in cPanel<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Do not confuse redirection and document root<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">During a redirect, the browser is instructed to access a different address.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">With a document root, the requested hostname remains the same, and the webserver serves files from the assigned directory.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">These are two different mechanisms.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Subdomain shows incorrect content<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If a subdomain is reachable but shows the wrong content, check in this order:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Which document root does the subdomain use?<\/li>\n\n\n\n<li>Which files are actually in this directory?<\/li>\n\n\n\n<li>Are there any redirects?<\/li>\n\n\n\n<li>Does the application itself use another configured URL?<\/li>\n\n\n\n<li>Does DNS point to the correct hosting environment?<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Do not move files on suspicion before checking these points.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Subdomain unexpectedly redirects to main domain<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If a subdomain automatically redirects to the main domain even though you haven't set that up, the cause can also lie within the web application.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, a CMS can know its preferred website address and redirect requests to that address.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, check not only cPanel but also the application's configuration and any existing forwarding rules.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">.htaccess can cause redirects<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">For Apache-based websites, rules in a file like:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>.htaccess<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Include redirects and other URL rules.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We explain how to securely analyze this file at <a href=\"\/en\/help\/web-hosting-cpanel\/htaccess-explained-edited\/\">.htaccess explained and safely edited<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Subdomain shows 403 Forbidden<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the subdomain reaches the correct server and document root, but:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>403 Forbidden<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">displayed, for example access rights, security rules or the directory structure can play a role.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We cover systematic error analysis under <a href=\"\/en\/help\/web-hosting-cpanel\/fehler-403-forbidden-beheben\/\">Fix 403 Forbidden<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Subdomain shows 404 Not Found<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">An error <code>404 Not Found<\/code> can occur even though the subdomain itself is configured correctly.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check among other things:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Document Root<\/li>\n\n\n\n<li>existing website files<\/li>\n\n\n\n<li>requested URL<\/li>\n\n\n\n<li>Rewrite rules<\/li>\n\n\n\n<li>Web application configuration<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Subdomain shows 500 Internal Server Error<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the subdomain fundamentally reaches the correct website, but a:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>500 Internal Server Error<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">is displayed, the problem may lie within the application, PHP configuration, or server rules, for example.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We are treating the diagnosis under <a href=\"\/en\/help\/web-hosting-cpanel\/fehler-500-internal-server-error\/\">Fixing a 500 Internal Server Error<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Check document root of an existing subdomain<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If you no longer know later which directory belongs to a subdomain, open:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Domains \u2192 Domains<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">and check the assignment there.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Do not rely solely on a folder named <code>shop<\/code> automatically close <code>shop.example.com<\/code> must belong.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Do not change the document root on suspicion<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If a subdomain is in production use, you should not change its document root without a specific reason.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Changing the mapping does not automatically move the existing website files.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The web server would then merely use a different directory.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Attention:<\/strong> Changing the document root and moving files are two separate processes.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">Remove subdomain<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If a subdomain is no longer needed, you can delete it via:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Domains \u2192 Domains<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">manage or remove.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check beforehand which resources are still connected to it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This may include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Website files<\/li>\n\n\n\n<li>Databases<\/li>\n\n\n\n<li>Redirects<\/li>\n\n\n\n<li>DNS records<\/li>\n\n\n\n<li>SSL configuration<\/li>\n\n\n\n<li>further data used by the application<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Removing the subdomain does not automatically delete the website<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The domain configuration and the files stored in the hosting are different things.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, do not assume that removing the subdomain automatically deletes all associated files or databases.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Conversely, you should not delete the files first if you have not yet checked whether they are needed elsewhere.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Removing a subdomain and deleting a DNS record are separate processes<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If DNS is managed externally, an entry for the subdomain may still exist there even though you removed it from cPanel.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, when permanently decommissioning, check both the hosting configuration and the DNS zone actually in use.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Recommended procedure for creating a subdomain<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Define what the subdomain should be used for.<\/li>\n\n\n\n<li>Log in to cPanel.<\/li>\n\n\n\n<li>Open <strong>Domains \u2192 Domains<\/strong>.<\/li>\n\n\n\n<li>Select the function to create a new domain.<\/li>\n\n\n\n<li>Enter the full hostname like <code>shop.example.com<\/code> one.<\/li>\n\n\n\n<li>Define a suitable document root.<\/li>\n\n\n\n<li>Check if a custom document root should be used.<\/li>\n\n\n\n<li>Create the subdomain.<\/li>\n\n\n\n<li>Check the mapping in the domain overview.<\/li>\n\n\n\n<li>Open the document root in the file manager.<\/li>\n\n\n\n<li>Provide the required website files.<\/li>\n\n\n\n<li>Check the DNS resolution.<\/li>\n\n\n\n<li>Test the subdomain via HTTPS.<\/li>\n\n\n\n<li>Check the website or application.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">Recommended troubleshooting for a non-working subdomain<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Check if the subdomain under <strong>Domains \u2192 Domains<\/strong> is available.<\/li>\n\n\n\n<li>Check the complete hostname.<\/li>\n\n\n\n<li>Check the document root.<\/li>\n\n\n\n<li>Check the files in the document root.<\/li>\n\n\n\n<li>Check the DNS resolution.<\/li>\n\n\n\n<li>Check HTTPS or SSL.<\/li>\n\n\n\n<li>Check redirects and if necessary <code>.htaccess<\/code>.<\/li>\n\n\n\n<li>Then, investigate a specific HTTP error message.<\/li>\n<\/ol>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Basic rule:<\/strong> If you experience issues with a subdomain, you should check the DNS, cPanel domain mapping, document root, and web application separately. This makes it much faster to determine at which level the error is occurring.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">When should you contact support?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn eine Subdomain trotz korrekter Einrichtung nicht erreichbar ist oder unerwartete Inhalte anzeigt, solltest du den aktuellen Zustand m\u00f6glichst genau dokumentieren.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For an analysis, the following information is particularly helpful:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>vollst\u00e4ndiger Name der Subdomain<\/li>\n\n\n\n<li>associated main domain<\/li>\n\n\n\n<li>in cPanel angezeigter Document Root<\/li>\n\n\n\n<li>ob die Website-Dateien dort vorhanden sind<\/li>\n\n\n\n<li>ob DNS \u00fcber CURIAWEB oder extern verwaltet wird<\/li>\n\n\n\n<li>ob DNS k\u00fcrzlich ge\u00e4ndert wurde<\/li>\n\n\n\n<li>genaue Fehlermeldung beziehungsweise unerwartetes Verhalten<\/li>\n\n\n\n<li>ob HTTP und HTTPS unterschiedlich reagieren<\/li>\n\n\n\n<li>ob die Subdomain neu eingerichtet wurde oder zuvor funktioniert hat<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Do not transmit any passwords or other confidential access credentials.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Summary<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A subdomain like <code>shop.example.com<\/code> ist ein eigener Hostname unterhalb einer bestehenden Domain. Im CURIAWEB-cPanel richtest du sie \u00fcber <strong>Domains \u2192 Domains<\/strong> ein und weist ihr einen passenden <strong>Document Root<\/strong> zu.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn die Subdomain eine eigenst\u00e4ndige Website enthalten soll, solltest du einen eigenen Document Root verwenden und die zugeh\u00f6rigen Website-Dateien in diesem Verzeichnis bereitstellen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Das Erstellen der Subdomain im Hosting und ihre \u00f6ffentliche DNS-Aufl\u00f6sung sind unterschiedliche Bestandteile. Wenn DNS extern verwaltet wird, muss der ben\u00f6tigte Eintrag dort vorhanden sein.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Teste nach der Einrichtung sowohl die normale Erreichbarkeit als auch HTTPS. Wenn die Subdomain die falsche Website zeigt, unerwartet weiterleitet oder einen Fehler ausgibt, pr\u00fcfe zuerst Document Root, Dateien, DNS und Weiterleitungen, bevor du die Konfiguration ver\u00e4nderst.<\/p>","protected":false},"excerpt":{"rendered":"<p>Eine Subdomain ist eine zus\u00e4tzliche Adresse unterhalb deiner bestehenden Domain. Damit kannst du beispielsweise einen Shop, einen Kundenbereich, eine Entwicklungsumgebung oder eine separate Webanwendung unter einer eigenen Adresse betreiben. Aus der Domain: example.com kann beispielsweise die Subdomain: shop.example.com werden. In dieser Anleitung zeigen wir dir Schritt f\u00fcr Schritt, wie du eine Subdomain im CURIAWEB-cPanel erstellst, [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_joinchat":[],"footnotes":""},"doc_category":[78],"doc_tag":[],"class_list":["post-22581","docs","type-docs","status-publish","hentry","doc_category-webhosting-cpanel"],"year_month":"2026-09","word_count":2792,"total_views":"3","reactions":{"happy":"0","normal":"0","sad":"0"},"author_info":{"name":"Silvio Mazenauer","author_nicename":"admin-curia","author_url":"https:\/\/www.curiaweb.ch\/en\/author\/admin-curia\/"},"doc_category_info":[{"term_name":"Webhosting &amp; cPanel","term_url":"https:\/\/www.curiaweb.ch\/en\/hilfe-kategorie\/webhosting-cpanel\/"}],"doc_tag_info":[],"knowledge_base_info":[],"knowledge_base_slug":[],"_links":{"self":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/22581","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/comments?post=22581"}],"version-history":[{"count":1,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/22581\/revisions"}],"predecessor-version":[{"id":22583,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/22581\/revisions\/22583"}],"wp:attachment":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/media?parent=22581"}],"wp:term":[{"taxonomy":"doc_category","embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/doc_category?post=22581"},{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/doc_tag?post=22581"}],"curies":[{"name":"WP","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}