# 10. Subdomain Manage

<figure><img src="https://1888569782-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fj6f1XtdOtNUZVCRH9J44%2Fuploads%2FagCSz3g7Q92eQX3Vq45w%2Fimage.png?alt=media&#x26;token=9a25e87a-45c3-45e7-a703-ac478f975b23" alt=""><figcaption></figcaption></figure>

#### 📖 Overview

The **Subdomain Manage** module allows you to create, configure, and monitor your subdomains with the same level of control and protection as your main domain.

You can manage DNS integration, toggle HTTPS redirection, and apply ShieldsGuard’s proxy security — all from a single dashboard.

> 🛡️ Subdomains often serve as entry points for attackers. Managing them effectively ensures that your entire domain hierarchy is secured, not just your root domain.

***

#### ⚙️ Key Functions

**✅ Subdomain Listing**

Each row in the interface shows:

* **Subdomain Name** (e.g., `login.yourdomain.com`)
* **DNS Label** (e.g., `login`)
* **Proxy Status** (ACTIVE / INACTIVE)
* **HTTPS Redirection** (toggle)
* **Resolved IP Address**
* **Action Buttons** (Create / Manage / Delete)

***

#### 🛠️ How to Create a Subdomain

1. Ensure your DNS records include an **A record** pointing the subdomain to the correct IP.
2. Open the **Subdomain Manage** module.
3. Locate or define the subdomain you wish to configure.
4. Click **Create** to activate ShieldsGuard’s edge protection and monitoring for that subdomain.

> ⚠️ If a subdomain does not appear, it may be missing from your DNS configuration.

***

#### 🔄 HTTPS Redirection

You can enable HTTPS enforcement for any subdomain individually. This ensures:

* All `http://` traffic is redirected to `https://`
* SSL certificates (ShieldsGuard-managed or custom) are applied
* Secure, encrypted connections are enforced site-wide

***

#### 🧱 Proxy Status

Toggle ShieldsGuard protection per subdomain:

* **ACTIVE** → All traffic passes through ShieldsGuard's protection engine (WAF, DDoS, IP filtering)
* **INACTIVE** → Traffic bypasses ShieldsGuard and goes directly to the origin server

> ✅ Keeping the proxy enabled is recommended to ensure security policies are applied consistently.

***

#### 🧨 Manage vs Delete

* **Manage** – Open detailed configuration and analytics for that subdomain
* **Delete** – Remove ShieldsGuard management and protection (does not delete DNS record)

***

#### 📋 Use Cases

| Scenario                 | Subdomain Example     | Outcome                                 |
| ------------------------ | --------------------- | --------------------------------------- |
| Isolated login system    | `auth.example.com`    | Separate WAF rules for authentication   |
| Client portal            | `client1.example.com` | Customized security & reporting         |
| Dev/staging environments | `staging.example.com` | Hidden from public, managed securely    |
| Public APIs              | `api.example.com`     | Rate limited, filtered by IP or headers |

***

#### 🔐 Best Practices

| Best Practice                   | Why It Matters                            |
| ------------------------------- | ----------------------------------------- |
| Enable HTTPS on every subdomain | Prevent downgrade attacks and build trust |
| Keep proxy active               | Apply full ShieldsGuard protection stack  |
| Disable unused subdomains       | Reduce unnecessary surface area           |
| Regularly review subdomain list | Detect orphaned or forgotten assets       |

***

> 🎯 Subdomain Manage ensures that **every endpoint under your domain** is actively protected, encrypted, and visible to your security team.