Skip to main content
Browse documentation

Fronty documentation

Connect a custom domain, HTTPS, and business email

Point a domain at Fronty without deleting mail records, verify the public result, and understand the DNS records that protect business email.

Last verified

Availability

Available on eligible plans

Custom domains, certificate handling and business-email DNS checks are implemented. Your registrar and mail provider remain separate services.

Plans
Plans that include a custom domain; mailbox costs belong to the mail provider.
Roles
Owner or administrator with website settings and DNS access.
Before you start
A registered domain, access to its DNS manager, and a published website.
On this page
  1. Choose the hostname before editing DNS
  2. Add and verify the web records
  3. Preserve and verify business email
  4. Verify outside the dashboard

Choose the hostname before editing DNS #

Decide whether the site should use the apex domain, www, or a subdomain such as shop. Keep one canonical public hostname and redirect other accepted variants to it.

Inventory existing DNS records first. In particular, copy the current MX, TXT, SPF, DKIM and DMARC records. Connecting web hosting should not require deleting the records that deliver or authenticate email.

Add and verify the web records #

  1. Open the website's domain settings and enter the intended hostname.
  2. Copy the exact records Fronty displays into the registrar or DNS provider. Do not copy values from a different website or an old support screenshot.
  3. Remove only a conflicting web record that prevents the new value from being published. Preserve unrelated mail and verification records.
  4. Recheck the domain from Fronty. DNS propagation has no guaranteed completion time; caches and providers differ.
  5. After verification, open the HTTPS URL and confirm that the certificate is valid for the exact hostname.

The current managed-domain path uses CNAME records; nameserver delegation is disabled. Canonical-host redirects are currently temporary HTTP 302 responses, so verify the exact behavior before treating them as permanent search migrations.

Preserve and verify business email #

Fronty does not host or read your mailbox. Your provider supplies the mailbox; Fronty reads public DNS and helps identify missing records.

MX
Where incoming mail is delivered.
SPF
Which systems may send mail for the domain.
DKIM
A provider-specific signature that recipients can verify.
DMARC
How receivers should handle unauthenticated mail and where reports go.

Add the values supplied by your mail provider, then re-run the public check. Do not invent or combine SPF records without understanding the provider's guidance.

Verify outside the dashboard #

You will know it worked when public DNS returns the intended web and mail records, the HTTPS URL opens without a certificate warning, canonical redirects use one hostname, and a test message can be sent and received through the existing mail provider.
Fronty still says pending
Compare the exact host, type and value. Check for a conflicting record and allow for DNS caching.
The website works but email stopped
Restore the provider's MX and authentication records from your inventory, then test mail independently.
Only one hostname works
Configure the intended canonical and redirect variant rather than duplicating the site.

Capability overviews

For the shorter product explanation, see:

Readiness and publishing Understand drafts and releases, resolve the complete readiness checklist, publish safely, and know the current rollback boundary. SEO, social, and AI visibility Control page identity and previews, verify what Fronty renders automatically, and understand what still requires manual work or external discovery. Plans and billing Read the live plan catalog, understand website-level entitlements, and verify checkout, portal, coupon, refund, and usage-limit behavior.