> For the complete documentation index, see [llms.txt](https://docs.guestway.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guestway.io/inbox-and-messaging/domains.md).

# Domains

Domains connects your own domains to Guestway, for guest emails, the guest portal and the short links in your messages and QR codes.

{% hint style="info" %}
**Requirements**

* To see **Domains**: a role with **Advanced configuration** at **View** or higher. Every role except **Cleaner** has it.
* To add, verify or delete domains: the **Admin** or **Super admin** role, or a role with **Advanced configuration** → **Domains** at **Edit**. See [Users and roles](https://docs.guestway.io/account-and-administration/users-and-roles.md).
* Access to the DNS settings of your domain provider.
  {% endhint %}

## Email domains

The **Email domains** tab of **Settings** → **Domains** lists the domains that send and receive guest emails, such as *guests.yourcompany.com*. **Add email domain** adds one: enter the **Domain** and click **Create**. The new domain then opens.

Each domain shows its status, **Verified** or **Not Verified**, and the state of each record. The check icon (**Check email domain verification**) checks the records again and shows the date of the last check.

| Record    | Type  | What it does                                       |
| --------- | ----- | -------------------------------------------------- |
| **DKIM**  | CNAME | Signs outgoing mail, so it is not flagged as spam. |
| **DMARC** | TXT   | Sets the authentication policy of your domain.     |
| **MX**    | MX    | Routes incoming mail to Guestway.                  |
| **SPF**   | TXT   | Allows Guestway to send email for your domain.     |

The detail page of a domain shows each record with its name, the expected value and the value that was found, and a copy icon. **Send Email with verification info** prepares an email with the records for your IT administrator.

A verified domain can be used for **Custom guest inbox emails** in **Settings** → **Inbox**. See [Inbox](https://docs.guestway.io/inbox-and-messaging/inbox.md).

**Delete email domain** removes the domain. Custom guest inbox emails on that domain then no longer appear in the inbox.

## Guest portal domains

The **Guest portal domains** tab lists the domains that open the guest portal on your own address, such as *guests.yourcompany.com*, instead of the Guestway address. **Add portal domain** adds one: enter the **Domain** and click **Create**. The new domain then opens.

| Step           | What it means                                                                                                                        |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| **Setup**      | Guestway prepared the domain: **Done** or **Not Done**. The check icon tries again.                                                  |
| **DNS record** | The CNAME record, with its **Name** and **Value**, is in place at your domain provider. Changes can take up to 24 hours.             |
| **HTTPS**      | Guestway added a security certificate, so guests get a secure connection. It is added automatically once the DNS record is in place. |

The check icon (**Check domain status**) checks the domain again. **Email these instructions** prepares an email with the DNS record.

A portal domain is used only when it is verified and chosen in **Guest portal domain** of a [branding](https://docs.guestway.io/guest-experience/branding.md). The default is **Guestway default**.

**Delete portal domain** removes the domain. Guests then open the guest portal on the default Guestway address again.

## Short link domains

The **Short link domains** tab lists the domain that your short links use instead of *gstw\.io*, for example *go.yourcompany.com*. Guests see these short links in your messages and in QR codes. **Add short link domain** adds one: enter the **Domain** and click **Create**. The new domain then opens.

A short link domain has the same steps as a guest portal domain: **Setup**, **DNS record** and **HTTPS**. The check icon (**Check domain status**) checks the domain again. **Email these instructions** prepares an email with the DNS record.

| Limit          | What it means                                                                                                                          |
| -------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| One domain     | Your organization can have one short link domain. **Add short link domain** does not show when you have one.                           |
| Subdomain only | The domain must be a subdomain, such as *go.yourcompany.com*. A domain such as *yourcompany.com* cannot point to Guestway.             |
| Other domains  | You cannot use a Guestway domain, such as *gstw\.io* or *guestway.io*, or a domain that is already your guest portal domain.           |
| Holding        | Another organization of your holding can add the same domain after it is verified. An organization outside your holding cannot add it. |
| Not verified   | A short link domain that is still not verified one month after you add it is deleted.                                                  |

A short link domain is used only when it is verified and chosen:

* In **Short link domain** of a [branding](https://docs.guestway.io/guest-experience/branding.md): the short links in the messages to guests of that branding use it. Without one, they use *gstw\.io*.
* In **Short link domain** of a new [QR code](https://docs.guestway.io/guest-experience/qr-codes.md): the printed link uses it. The domain of a QR code never changes.

Guestway changes the *gstw\.io* short links in a message when the message is created: in the messages that your team sends from the inbox and in the messages of your automations. This includes the links that you paste, for example the link of a guidebook. The inbox shows the links as the guest gets them. A short link that you copy in Guestway, for example with **Copy link**, shows *gstw\.io*.

The message uses the branding of the property of the reservation. A message without a reservation uses the default branding. A branding without a short link domain uses *gstw\.io*, also when the default branding has one.

**Delete short link domain** removes the domain. Short links then use *gstw\.io* again. You cannot delete the domain while a branding or a QR code uses it. Set the branding back to **gstw\.io (Guestway default)** first. When QR codes use the domain, **This domain is in use** lists them: delete them first if they are no longer printed anywhere.

## What uses a domain

Guestway does not switch to a verified domain on its own. It uses a domain only where a branding or a QR code chose it.

| Domain              | What uses it                                                                                       |
| ------------------- | -------------------------------------------------------------------------------------------------- |
| Email domain        | A branding whose **Receiving Email** is a guest inbox email on the domain.                         |
| Guest portal domain | A branding that chose the domain in **Guest portal domain**.                                       |
| Short link domain   | A branding that chose the domain in **Short link domain**, and the QR codes created on the domain. |

The card of each domain has an **In use** row:

| Value                                                     | What it means                                                                |
| --------------------------------------------------------- | ---------------------------------------------------------------------------- |
| What uses it, for example **2 Brandings · 3 QR Codes**    | Brandings or QR codes use the domain. Point at the value to see their names. |
| **Not Yet**                                               | Nothing uses the domain yet.                                                 |
| The number of inbox emails, for example **1 Inbox Email** | An email domain has guest inbox emails, but no branding uses them yet.       |

The value shows as a warning when nothing uses the domain yet, or when something uses it but the domain is not verified. **In use** does not show when your role cannot see the brandings.

The detail of each domain ends with the step **Use it**. It lists what uses the domain: the brandings, the QR codes of a short link domain and the guest inbox emails of an email domain. Click an item to open it. Under the list, the step says what is left to do. When the domain is verified and nothing uses it yet, the step has a button:

| Button                      | Domain                                   | What it does                                                                                                 |
| --------------------------- | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
| **Choose it in a branding** | Guest portal domain, short link domain   | With one branding, opens its editor at **Custom domains**. With more than one, opens the list of brandings.  |
| **Add a guest inbox email** | Email domain without a guest inbox email | Opens **Settings** → **Inbox** with the domain selected.                                                     |
| **Choose it in a branding** | Email domain with a guest inbox email    | With one branding, opens its editor at **Receiving Email**. With more than one, opens the list of brandings. |

You cannot use **Choose it in a branding** without the permission to edit brandings, or **Add a guest inbox email** without the permission to edit the guest inbox emails.

## Statuses

| Status           | Meaning                                                               |
| ---------------- | --------------------------------------------------------------------- |
| **Verified**     | All records are in place. The domain can be used.                     |
| **Not Verified** | At least one record is missing or wrong. The detail page shows which. |

## Related

* [How to add a custom email domain](https://docs.guestway.io/inbox-and-messaging/domains/how-to-add-a-custom-email-domain.md)
* [How to use your own domain for the guest portal](https://docs.guestway.io/inbox-and-messaging/domains/how-to-use-your-own-domain-for-the-guest-portal.md)
* [How to use your own domain for short links](https://docs.guestway.io/inbox-and-messaging/domains/how-to-use-your-own-domain-for-short-links.md)
* [Branding](https://docs.guestway.io/guest-experience/branding.md): where you choose a guest portal domain and a short link domain
* [QR codes](https://docs.guestway.io/guest-experience/qr-codes.md)
* [Inbox](https://docs.guestway.io/inbox-and-messaging/inbox.md)
* [About email forwarding](https://docs.guestway.io/inbox-and-messaging/inbox/about-email-forwarding.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.guestway.io/inbox-and-messaging/domains.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
