> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gridix.live/llms.txt
> Use this file to discover all available pages before exploring further.

# Custom Domain Setup

> Connect your custom domain to Gridix projects for branded URLs

Connect your own domain to Gridix projects so customers can access your floor plans at your branded URL (e.g., `floors.yourcompany.com`).

## Overview

Custom domains allow you to:

* **Brand Your URLs**: Use your own domain instead of Gridix subdomain
* **Professional Appearance**: More professional and trustworthy
* **SEO Benefits**: Better for search engine optimization
* **Easy Sharing**: Easy-to-remember URLs for customers

<Check>
  Benefits:

  * Custom domain (e.g., floors.yourcompany.com)
  * SSL certificate included
  * Automatic DNS management
  * Professional branding
</Check>

## Prerequisites

Before setting up a custom domain, ensure you have:

* A domain name registered
* DNS access to your domain
* A Gridix project ready
* Admin access to domain registrar

## Adding a Custom Domain

### Step 1: Access Domain Settings

<Steps>
  <Step title="Navigate to Project Settings">
    Go to your project editor.
  </Step>

  <Step title="Open Domains Section">
    Click on "Domains" or "Custom Domain" in settings.
  </Step>

  <Step title="Add Domain">
    Click "Add Domain" or "Connect Domain" button.
  </Step>
</Steps>

### Step 2: Enter Domain

<Steps>
  <Step title="Enter Domain Name">
    Type your domain (e.g., `floors.yourcompany.com`).

    <Note>
      You can use a subdomain (floors.yourcompany.com) or root domain (yourcompany.com).
    </Note>
  </Step>

  <Step title="Verify Domain Format">
    Ensure domain is correctly formatted:

    * No `http://` or `https://`
    * Include subdomain if using one
    * No trailing slashes
  </Step>

  <Step title="Submit Domain">
    Click "Add Domain" or "Save".
  </Step>
</Steps>

### Step 3: Configure DNS

<Steps>
  <Step title="View DNS Instructions">
    Gridix will display DNS configuration instructions.
  </Step>

  <Step title="Access DNS Settings">
    Log in to your domain registrar or DNS provider.
  </Step>

  <Step title="Add DNS Record">
    Add the DNS record provided by Gridix:

    * Record type (usually CNAME)
    * Host/Name (subdomain or @)
    * Value/Points to (Gridix target)
    * TTL (Time to Live)
  </Step>

  <Step title="Save DNS Changes">
    Save changes in your DNS provider.
  </Step>
</Steps>

## DNS Configuration

### CNAME Record

For subdomains (recommended):

```
Type: CNAME
Name: floors (or your subdomain)
Value: gridix.app (or provided target)
TTL: 3600 (or default)
```

### A Record

For root domains (if required):

```
Type: A
Name: @ (or blank for root)
Value: [IP address provided by Gridix]
TTL: 3600
```

<Warning>
  Root domain configuration may vary. Use CNAME for subdomains when possible.
</Warning>

## DNS Propagation

### Understanding Propagation

After adding DNS records:

* **Propagation Time**: 24-48 hours typically
* **Global Updates**: DNS changes propagate worldwide
* **Verification**: Gridix checks DNS automatically

<Info>
  DNS propagation can take up to 48 hours, though often completes faster.
</Info>

### Checking DNS Status

<Steps>
  <Step title="View Domain Status">
    Check domain status in Gridix dashboard.
  </Step>

  <Step title="DNS Check Tools">
    Use online DNS checkers:

    * whatsmydns.net
    * dnschecker.org
    * dig command
  </Step>

  <Step title="Wait for Propagation">
    Allow time for DNS to propagate globally.
  </Step>
</Steps>

## SSL Certificate

### Automatic SSL

<Check>
  Gridix automatically provisions SSL certificates:

  * Free SSL certificate
  * Automatic renewal
  * HTTPS enabled
  * Secure by default
</Check>

### SSL Activation

SSL is activated automatically once:

* DNS is properly configured
* Domain is verified
* Propagation is complete

This typically happens within hours of DNS setup.

## Domain Verification

### Verification Process

<Steps>
  <Step title="DNS Check">
    Gridix verifies DNS configuration.
  </Step>

  <Step title="Domain Ownership">
    Verify you own the domain.
  </Step>

  <Step title="SSL Provisioning">
    SSL certificate is automatically provisioned.
  </Step>

  <Step title="Active Status">
    Domain becomes active and ready to use.
  </Step>
</Steps>

### Verification Status

Check verification status:

* **Pending**: DNS not yet configured or propagating
* **Verifying**: DNS check in progress
* **Active**: Domain is live and working
* **Failed**: DNS configuration issue

## Using Your Custom Domain

### Accessing Projects

Once domain is active:

* Visit `https://your-domain.com`
* Or use direct project URLs
* All projects accessible via custom domain

### Project URLs

Projects are accessible at:

* `https://your-domain.com/project/project-slug`
* Or via widget embedding
* Custom domain applies automatically

## Managing Domains

### Viewing Domains

See all connected domains:

* Domain list in project settings
* Status of each domain
* SSL certificate status
* Last verification check

### Removing Domains

To disconnect a domain:

<Steps>
  <Step title="Select Domain">
    Choose domain to remove.
  </Step>

  <Step title="Remove Domain">
    Click "Remove" or "Disconnect".
  </Step>

  <Step title="Confirm Removal">
    Confirm domain removal.
  </Step>

  <Step title="Update DNS">
    Remove DNS records from your registrar (optional).
  </Step>
</Steps>

## Troubleshooting

### Common Issues

<AccordionGroup>
  <Accordion title="Domain not verifying">
    * Check DNS records are correct
    * Verify DNS propagation completed
    * Ensure no typos in domain name
    * Wait 24-48 hours for propagation
  </Accordion>

  <Accordion title="SSL certificate not activating">
    * Verify DNS is correct
    * Wait for SSL provisioning (can take hours)
    * Check domain verification status
    * Contact support if issue persists
  </Accordion>

  <Accordion title="Domain not accessible">
    * Verify DNS records
    * Check domain status in Gridix
    * Test DNS propagation
    * Clear browser cache
    * Try different DNS servers
  </Accordion>
</AccordionGroup>

## Best Practices

<Tip>
  **Use Subdomains**: Use subdomains (floors.yourcompany.com) rather than root domain for easier management.
</Tip>

<Tip>
  **DNS Provider**: Use reliable DNS providers for faster propagation.
</Tip>

<Tip>
  **Documentation**: Keep DNS records documented for future reference.
</Tip>

<Tip>
  **Testing**: Test domain access from different locations after setup.
</Tip>

## Next Steps

* **[Project Configuration](/en/projects/editing)** - Configure projects for custom domains
* **[Widget Embedding](/en/widgets/embedding)** - Embed widgets using custom domain
* **[Project Management](/en/projects/creation)** - Create projects accessible via custom domain