To use a Titan mailbox at your custom domain, first find out where that domain’s DNS is managed. If Squarespace manages the domain or it uses Nameserver Connect, you can add Titan records in Squarespace. If the domain uses DNS Connect, the registrar or other third-party DNS provider remains the place for every mail record. Buying Essential Email by Titan through Squarespace is the simplest route: Squarespace adds the Titan MX records when the account is created, while Titan hosts the mailbox and its interface.
The critical safety rule is to preserve working MX records. MX records decide where incoming mail goes, so connecting the website must not involve deleting them. Use the setup path that matches your DNS arrangement and whether you already have a Titan account.
As an Amazon Associate I earn from qualifying purchases.
Understand which service does what
A custom-domain mailbox involves several separate services. Squarespace can host your website and, in some cases, sell and bill an integrated Titan plan, but the mailbox itself is hosted by Titan. The domain may be registered with Squarespace or with another registrar, and DNS may be managed in a different place again.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →| Role | What it controls | Where it may be managed |
|---|---|---|
| Website hosting | Your Squarespace site and its web content | Squarespace |
| Domain registration | Renewal and ownership of the domain name | Squarespace or a third-party registrar |
| DNS hosting | Records that direct web traffic and email | Squarespace, a registrar, or another DNS provider |
| Email billing | The commercial account and invoices for an integrated plan | Squarespace when Titan is purchased there; otherwise the provider selling Titan |
| Mailbox hosting | Messages, folders, authentication and the mail interface | Titan |
Squarespace’s Help Center describes this separation directly: your email is hosted externally even when your site is hosted by Squarespace. Buying through Squarespace changes billing and some automatic DNS behavior; it does not turn Squarespace into the mailbox host.
#1 Best Overall
Choose the correct DNS setup path
Before creating records, identify the domain connection type. The location of the DNS controls determines where you must make the change.
Squarespace-managed domain
A domain registered with Squarespace normally exposes its records in the Squarespace domain settings. The Squarespace DNS editor is the right place for a Titan preset or custom records.
Nameserver Connect
Nameserver Connect points the domain’s nameservers to Squarespace while the domain may remain registered elsewhere. Because Squarespace is authoritative for DNS in this arrangement, use the domain’s DNS panel in Squarespace.
DNS Connect
DNS Connect links a third-party domain to a Squarespace site without moving DNS authority to Squarespace. In this arrangement, Squarespace can show the connection, but the registrar or DNS provider still owns the records. Add or change Titan MX, TXT or CNAME records in that provider’s DNS manager, not in Squarespace.
If the Squarespace interface does not offer the DNS controls or the Titan preset, treat that as a sign to check the connection method before editing anything. A website can be connected successfully while DNS remains elsewhere.
Prepare without interrupting existing mail
Make a short inventory before changing records. This prevents a website connection from accidentally taking down an established mailbox.
- Write down the domain and the exact address or addresses you plan to create.
- Record the current MX entries and their priorities. They show which service currently receives mail.
- Identify the provider that currently handles outbound authentication, including any SPF, DKIM or DMARC records.
- Confirm whether the domain is Squarespace-managed, uses Nameserver Connect, or uses DNS Connect.
- Have administrator access to the Squarespace account and, when applicable, the external registrar or DNS host.
- Keep the current email provider’s support contact available if this is a provider migration rather than a new mailbox.
Connecting a third-party domain to a Squarespace website normally does not require an MX change when the domain and email provider already match. Squarespace specifically warns that deleting MX records can interfere with email routing.
Option 1: buy Titan through Squarespace
Use this path when you want Essential Email by Titan purchased and billed through Squarespace for the domain. Squarespace’s integrated setup adds Titan’s MX records automatically when the account is created, so you do not have to copy a guessed record set.
- Open the Squarespace custom email setup for the domain.
- Choose Essential Email by Titan and select the domain for the mailbox.
- Complete the account and mailbox details requested by Squarespace.
- Finish checkout and any account verification or reauthentication prompts.
- Allow the setup to complete. Squarespace adds the Titan MX records for the integrated account.
- Sign in through Titan’s email interface using the mailbox credentials supplied during setup.
In this arrangement, Squarespace handles the integrated-plan billing path, but Titan remains the service hosting the messages. The same setup also adds SPF and DMARC automatically according to Squarespace’s current email-DNS instructions. Squarespace points customers to Titan’s current guidance for DKIM details.
Option 2: connect a Titan account you bought elsewhere
Use the Titan preset when you already have a Titan account and the domain’s DNS is managed by Squarespace or by Nameserver Connect.
- In Squarespace, open Domains.
- Select the domain you want to use for Titan.
- Open DNS.
- Select Add preset.
- Choose Titan Email.
- Complete any reauthentication request shown by Squarespace.
- Add or apply the preset, then confirm that the resulting records are present in the DNS list.
The preset is a convenience for supported Squarespace DNS configurations. It does not move a DNS Connect domain into Squarespace. If your domain is connected through DNS Connect, perform the equivalent change at the third-party registrar or DNS provider instead.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Option 3: enter Titan records manually
Manual entry is appropriate when the preset is unavailable, when Titan gives account-specific values, or when DNS is controlled outside Squarespace. Do not copy a record set from an unrelated tutorial: Titan can change the hosts and priorities, and the values can depend on the account or service edition.
Get the live values from Titan
Open Titan’s current setup instructions or the administrator area for your account and obtain each required MX host and priority. Also obtain any TXT or CNAME records Titan requests for SPF, DKIM or other verification. Use the values displayed for your account at the time of setup.
Add records in Squarespace DNS
- Open Domains in Squarespace and select the relevant domain.
- Open DNS.
- Choose the control for adding a custom record, shown in Squarespace’s instructions as Custom Records.
- For every MX entry, select the MX record type, enter the host or name exactly as Titan specifies, enter the priority, and enter the mail server host.
- Add Titan’s TXT or CNAME records for authentication or verification exactly as supplied.
- Save each record and check the final list for spelling, trailing dots where the interface requires them, and priority numbers.
Add records at an external DNS provider
For DNS Connect, repeat the same record-entry process in the registrar or DNS provider’s manager. The labels may differ, but you still need the record type, host or name, priority for MX records, and destination value. Squarespace’s DNS editor cannot change records that remain authoritative elsewhere.
Keep an existing mailbox working during a changeover
There are two different scenarios: adding a new Titan address while another service remains active, or moving the domain’s mail reception from an existing provider to Titan.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsAdding Titan without replacing the current provider
Do not remove the current MX records merely because the website is now on Squarespace. If the existing provider should continue receiving mail, leave its MX configuration intact and follow that provider’s instructions for adding an address or alias. A Squarespace site connection and an email-provider change are separate operations.
Migrating mail reception to Titan
Coordinate the cutover with the current email provider. Establish the Titan account and any required users first, preserve access to the old mailbox, and schedule the MX change according to the providers’ migration instructions. The decisive action is replacing the receiving MX configuration with Titan’s current values; deleting records without a coordinated replacement can stop delivery.
Keep copies of the old records and note the time of the change. If delivery problems appear, those details let the current provider help you restore the previous routing while the migration is diagnosed.
Rank #4
Configure SPF, DKIM and DMARC correctly
Authentication records tell receiving servers which systems may send mail for your domain and how to handle messages that fail those checks.
SPF and DMARC in the Squarespace Titan integration
Squarespace says its Titan setup adds SPF and DMARC automatically. Do not add a second, competing SPF policy for the same domain; SPF is evaluated as a single policy, and combining providers requires a correctly merged value supplied by the relevant administrator.
DKIM
Squarespace directs Titan customers to Titan’s DKIM guidance. Retrieve the current selector, host and public-key value from Titan and publish them in the DNS manager that is authoritative for the domain. A DKIM record copied from another domain or an old account will not authenticate the new mailbox.
When another sender already uses the domain
If your website platform, newsletter service or another business system also sends mail, do not overwrite its approved SPF or DKIM records while adding Titan. Ask each provider for the current, compatible authentication instructions and keep one authoritative SPF policy. If you cannot reconcile the requirements, use the provider support channels before changing production DNS.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Verify the mailbox after setup
Verification should test both the mailbox and the domain’s routing, not just whether the Titan interface opens.
- Sign in to the Titan mailbox and send a message to an address outside your domain.
- Reply to that message and confirm that the reply arrives in Titan.
- Send a message from an external account to the new custom-domain address.
- Check the received message’s authentication details in the recipient’s mail client or headers when available.
- Send a message containing a normal attachment and confirm that it is delivered and readable.
- Repeat the inbound test for every mailbox or alias created during the setup.
If a message is rejected or lands in spam, compare the live MX, SPF, DKIM and DMARC records with Titan’s current instructions. Check the DNS provider that is actually authoritative; looking at Squarespace while the domain uses DNS Connect will show the wrong record set.
Troubleshoot by symptom
There is no DNS menu or Titan preset
Confirm the domain connection type. The preset is intended for a Squarespace-managed or Nameserver Connect domain. With DNS Connect, edit records at the third-party provider. If the domain should be managed by Squarespace but the controls are still missing, recheck which domain is selected and complete any requested reauthentication.
Mail stopped after connecting the website
Inspect MX records first. Squarespace warns that removing them can disrupt delivery. Restore the previous working MX configuration if the old provider should still receive mail, or apply the complete Titan set supplied for a planned migration. Do not attempt to fix a mail outage by changing unrelated website records.
Outgoing mail fails authentication
Retrieve fresh SPF, DKIM and DMARC instructions from Titan and compare them with the live DNS zone. Look for a misspelled host, an incomplete TXT value, a DKIM selector published at the wrong name, or multiple SPF policies. If the integrated Squarespace setup was used, verify that its automatically added SPF and DMARC records are still present.
Recommended Free Tools
Incoming mail does not reach Titan
Check that the MX records were added in the authoritative DNS manager and that every host and priority matches Titan’s instructions. A record entered in Squarespace has no effect when DNS Connect leaves authority with the registrar. Also check for an older MX record that still points to the previous provider when the intention was to migrate.
The website works but email does not
That combination is possible because web records and mail records are independent. Leave the functioning Squarespace website records alone and troubleshoot only the mail records and authentication policies. Squarespace limits its DNS support to showing where records can be entered; the email provider is the appropriate source for record values and mail-service behavior.
Quick Recap
Decide who should support each problem
| Problem | Best first contact |
|---|---|
| Where the DNS controls are located or how a Squarespace domain connection works | Squarespace support |
| Exact Titan MX, SPF, DKIM or DMARC values | Titan support or Titan’s current setup documentation |
| Mailbox sign-in, folders, sending limits or message behavior in the Titan service | Titan |
| Registrar-side DNS editing for a DNS Connect domain | The registrar or DNS provider |
| A planned migration from an existing email provider | The current provider and Titan together |
What to remember
- Titan hosts the mailbox even when Squarespace sells the integrated plan.
- Squarespace adds Titan MX records automatically when a Titan account is created through its integrated setup.
- The Titan Email preset is available for supported Squarespace DNS configurations.
- DNS Connect leaves DNS editing with the third-party domain provider.
- Working MX records should never be deleted simply to connect a website.
- Use Titan’s current account-specific values for manual records and DKIM, while checking the automatic SPF and DMARC behavior of the Squarespace integration.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
