Enom

A Webflow site publishes to a webflow.io subdomain until you connect a custom domain, and Webflow does not sell domains. A domain bought elsewhere keeps its DNS records at the registrar that issued it, so nothing resolves to the Webflow site until someone edits those records by hand.

Enom is that registrar for a large share of agency and reseller portfolios. Pointing its host records at Webflow's hosting connects the domain without changing nameservers or writing code, and teams running many domains can script registration and DNS setup instead, using the Enom Reseller API alongside the Webflow Data API. The same connection path covers one client site and a bulk provisioning pipeline.

This integration fits Enom resellers and web agencies that manage client domain portfolios. Hosting and SaaS companies provisioning customer domains through the API follow the same path at higher volume, and a freelancer connecting a single client domain runs the same DNS steps by hand.

How to integrate Enom with Webflow

What is Enom? Enom is a reseller platform for domains, email, and SSL certificates, owned by Tucows and separately ICANN-accredited as a domain registrar. Enom reports more than 6.5 million domains registered, 22,000 or more resellers in 150 or more countries, and support for 550 or more TLDs. Resellers manage domains through a control panel or the Enom Reseller API.

Agencies and resellers pair the two platforms to keep domain management and site hosting inside one workflow. Client domains registered through Enom's reseller program point at Webflow-hosted sites, and DNS stays editable in Enom's control panel. Every setup runs through DNS records or the two APIs, since the Webflow Marketplace has no Enom app.

Two approaches cover the work. Manual DNS configuration points an Enom-registered domain at a Webflow site through host records in Enom's control panel, with no code involved. The Webflow and Enom APIs give you control over registration, DNS records, and publishing, at the cost of server-side development and middleware you own. Most setups start with manual DNS configuration, and teams managing dozens of client domains add the API layer for bulk work.

Point your Enom domain at Webflow with host records

Manual DNS configuration is the no-code path, and the work splits between Webflow and Enom. You need a paid Site plan to connect a custom domain, because Starter sites publish to a webflow.io subdomain only. The domain also has to use Enom's default nameservers, since host records in Enom's panel only take effect on those nameservers. That constraint costs you nothing here, because Webflow hosting does not need custom nameservers.

Add the custom domain in Webflow

Start in Webflow so the site-specific verification value is already on your clipboard before you open Enom.

To add the domain:

1. Open Site settings > Publishing > Production.
2. Click Add a custom domain, then choose Manually add domain.
3. Enter your domain and click Add domain.

This connects the root domain and the www subdomain together, and the DNS values you need appear on the same screen. Copy the A record value, the www CNAME value, and the TXT verification string before you leave it. Once more than one domain is connected, click Make default next to the one you want traffic on, and point that default at the www subdomain: setting the root domain as the default without matching DNS produces a "too many redirects" loop.

Add host records in Enom

Enom's panel is where the domain actually gets pointed. Go to Domains > My domains, click the domain name, and choose Host records from the Manage domain dropdown, following Enom's DNS records guide. Confirm DNS server settings reads Our servers first, because on the nameserver settings page a Custom selection means panel edits do nothing.

To add the records:

1. Add a record with hostname @, record type A address, and address 198.202.211.1.
2. Add a record with hostname www, record type CNAME, and address cdn.webflow.com. including the trailing period, since Enom's panel help notes the nameserver otherwise appends your domain to the value.
3. Add a record with hostname _webflow, record type TXT record, and the one-time-verification= value from Site settings.
4. Click Save.

Copy those values from Site settings rather than from this page. Webflow is still updating its DNS infrastructure, and a site created before April 21, 2025 may show two A records instead of one, in which case add both. Enom puts host record propagation at 8 to 24 hours and resets the TTL to 3600 seconds after each change, while Webflow's stated window runs up to 48 hours, though most changes take effect within a few hours. SSL provisions automatically through Let's Encrypt and Google Trust Services for sites created after November 14, 2018, so no certificate work lands on you.

Build with the Webflow and Enom APIs

The API path suits resellers and platforms provisioning domains at scale, and it needs server-side development. You build middleware that calls both platforms, because Webflow has no native domain registration through Enom and the two platforms share no direct API connection. Enom's API is command-based and takes GET requests against https://reseller.enom.com/interface.asp with uid and pw on every call, where pw is now an API token rather than your account password; a test environment runs at https://resellertest.enom.com/interface.asp. Live API access requires a whitelisted static IP, added under Resellers > Manage > API, and requests from anywhere else return "User not permitted from this IP address". Run every Enom call from a server or serverless backend with a static outbound IP, never from Webflow hosting or browser code.

The work splits across two Enom command groups and two Webflow interfaces.

• Enom domain commands: The Enom Reseller API covers availability with Check, registration with Purchase, and order state with GetRegistrationStatus.
• Enom DNS commands: GetHosts and SetHosts read and write host records, while GetDNS and ModifyNS report and change the nameservers on a domain you own.
• Webflow Data API: The same API handles sites, custom domains, publishing, and Webflow CMS items, so one integration covers both the domain and the content behind it.
• Webflow webhook events: Events like collection_item_changed push CMS changes to your middleware as they happen, which removes any need to poll the Webflow side.

Enom's API offers no webhooks or event subscriptions, so anything that changes on the domain side has to be polled on a schedule you decide.

Automate Webflow DNS records with SetHosts

The SetHosts command writes a domain's host records in a single call and supports A, AAAA, CNAME, URL, FRAME, MX, MXE, and TXT types. Read the warning in Enom's docs before you use it: the call deletes every existing host record and replaces the set with whatever you send, MX records included. That is the one mistake worth designing against, so retrieve the current records with GetHosts and replay them in the same query string, every time.

To point a domain at Webflow programmatically:

1. Call GetHosts with command=GetHosts, uid, pw, SLD, and TLD, and store the existing records.
2. Call SetHosts with the preserved records plus the Webflow set:

HostName1=@&RecordType1=A&Address1=198.202.211.1
HostName2=www&RecordType2=CNAME&Address2=cdn.webflow.com.
HostName3=_webflow&RecordType3=TXT&Address3=<verification-value>

3. Publish with POST https://api.webflow.com/v2/sites/{site_id}/publish (scope sites:write). Include domain IDs from GET https://api.webflow.com/v2/sites/{site_id}/custom_domains in the customDomains array.

For new registrations, the Preconfigure command sets nameservers and host records on a domain sitting in the cart, using PreConfigDNS=other and UseHostRecords=1 with comma-delimited HostName, RecordType, and Address lists. Domains bought that way come online already pointed at Webflow, and SetHosts takes up to 50 records per domain for later changes.

Sync Enom domain data to the Webflow CMS

A reseller storefront or client dashboard built on Webflow can show live domain data pulled from Enom. Your middleware polls Enom, writes the results into a CMS Collection, and the site renders them through a Collection List. Enom supports polling only, so this sync runs on a schedule rather than on events.

To build the sync:

1. Poll GetExtendInfo for the Expiration and AutoRenew fields, and GetRegistrationStatus for RegistrationStatus and PurchaseStatus.
2. Create items with POST https://api.webflow.com/v2/collections/{collection_id}/items (scope CMS:write), where fieldData must include name and slug.
3. Update in bulk with PATCH on the same collection items path, up to 100 items per request.

Availability search follows the same shape. Middleware calls Check, where an RRPCode of 210 means the domain is available at the registry, and returns the result to a Code Embed element on the page. Code Embed runs client-side HTML, CSS, and JavaScript within a 50,000-character limit, so the Enom call itself stays on your server.

What you can build with the Enom Webflow integration

Enom and Webflow together let you run client sites and reseller storefronts on Webflow hosting while the domain portfolio stays on Enom's reseller platform. The patterns below cover most of what agencies and platforms actually ship on this pairing.

Common builds include:

• Client sites on agency-registered domains: Register client domains through Enom's reseller program, point each at a Webflow-hosted site, then hand the site over with its Site plan and connected domain from a Freelancer or Agency Workspace at project close.
• Branded domain reseller storefronts: Build a Webflow site that surfaces availability through middleware calling Check, with registration handled in Enom's panel or through Purchase. Enom also requires an active reseller website where registrants can renew or get help, and a Webflow portal satisfies that.
• Multi-domain portfolios with one primary site: Connect country or brand domain variants to a single Webflow site and set one as the default, so the rest redirect there and duplicate content does not split your search visibility.
• Automated provisioning for hosting and SaaS platforms: Chain the Preconfigure flow with the publish endpoint so a new customer's domain resolves to a Webflow-hosted site with no manual DNS step at signup.

Most of these builds lean on the same middleware pattern of polling Enom and writing the results into Webflow. If you are wiring that up for the first time, work through the Webflow CMS API guide and add the Enom calls once your CMS writes land cleanly.