# Page Not Found

The URL `guides/setting-up-mail-domains-in-humanic` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Setting Up Mail Domains in Humanic](https://humanic.gitbook.io/humanic/getting-started-with-humanic/domain-setup/setting-up-mail-domains-in-humanic.md)
- [Sub-Domains](https://humanic.gitbook.io/humanic/getting-started-with-humanic/domain-setup/sub-domains.md)
- [Switching to Humanic](https://humanic.gitbook.io/humanic/switching-to-humanic.md)
- [Generating a campaign](https://humanic.gitbook.io/humanic/getting-started-with-humanic/generating-a-campaign.md)
- [Understanding Domain Status](https://humanic.gitbook.io/humanic/getting-started-with-humanic/domain-setup/understanding-domain-status.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://humanic.gitbook.io/humanic/getting-started-with-humanic/domain-setup/setting-up-mail-domains-in-humanic.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://humanic.gitbook.io/humanic/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://humanic.gitbook.io/humanic/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/humanic/getting-started-with-humanic/domain-setup/setting-up-mail-domains-in-humanic.md`).

You may also use `Accept: text/markdown` header for content negotiation.