Crazy Domain (Freeparking)

A Webflow site publishes to a webflow.io address until you attach a custom domain on a paid Site plan. Webflow isn't a domain registrar, and its hosting doesn't include email. So a business that registered its domain and mailboxes at Crazy Domains needs both to keep working while the site moves.

Three DNS records send web traffic to Webflow while MX records keep delivering mail to Titan, cPanel, Exchange or Google Workspace mailboxes. An SSL certificate issues automatically once the records resolve. The domain registration itself stays at Crazy Domains.

Webflow designers and agencies in Australia and New Zealand can use these steps with the business owners and IT admins they work with. A .com.au can host a single-site launch, while a subdomain can host a campaign microsite. In an agency handoff, the client keeps the domain. Agencies holding a Crazy Domains reseller account can use the API workflows after reseller support confirms account compatibility.

How to integrate Crazy Domains with Webflow

What is Crazy Domains? Crazy Domains is a domain registrar and web hosting company established in 2007 and run as a division of Dreamscape Networks International Pte Ltd. It sells .com.au and .au direct domains, Standard and Premium DNS, email hosting, cPanel web hosting, SSL certificates and a website builder. Its New Zealand sister brand Freeparking became Crazy Domains New Zealand on 22 September 2025, so .co.nz customers now use the same Account Manager.

Teams pair the two when the domain already lives at Crazy Domains, and the site is moving to Webflow from cPanel, WordPress or the Crazy Domains website builder. The domain and its mailboxes stay put; only the web traffic records change. Former Freeparking customers follow the same steps, since their accounts moved to the Crazy Domains Account Manager at https://www.crazydomains.co.nz/members/login/ in the September 2025 rebrand. Crazy Domains says existing nameservers, A records and MX records carried over unchanged.

As of October 2026, there is no Crazy Domains app on the Webflow Marketplace. The Crazy Domains-Webflow integration therefore supports three approaches:

• Manual DNS records in the Crazy Domains Account Manager point the root domain, www or a subdomain at Webflow without writing code.
• Quick connect through Entri writes the same records for you if Crazy Domains appears in its provider search.
• The Webflow Data API and Dreamscape reseller APIs can support custom-domain audits, publishing and DNS changes through server-side development, provided reseller support confirms that your Crazy Domains account supports the Dreamscape APIs.

Most implementations use the manual DNS method on its own; agencies with reseller accounts combine it with the API path for bulk work.

Add Webflow DNS records in the Crazy Domains Account Manager

Manual DNS pointing is the core of this integration. You add an A record, a CNAME and a TXT verification record in the DNS Settings tab, then verify and publish from Site settings. Every site you connect needs a paid Site plan. The Account Manager zone only controls the domain while it uses ns1.crazydomains.com and ns2.crazydomains.com, or ns1.dnspackage.com and ns2.dnspackage.com on Premium DNS. Copy record values from Site settings > Publishing > Production rather than from an older guide, because the current set is a single A record and older two-record setups no longer publish (see the legacy note below).

The DNS method handles:

• Root and www on one Webflow site, with www as the default domain
• Subdomains such as blog. or campaign. while the root stays elsewhere
• Up to 50 custom domains per site on one paid Site plan
• Automatic SSL issuance and renewal for as long as DNS points at Webflow

If the Crazy Domains zone already has CAA records, they must include 0 issue "letsencrypt.org" and 0 issue "pki.goog; cansignhttpexchanges=yes" or certificate issuance fails.

Point the root domain and www at Webflow

This path connects yourdomain.com.au and www.yourdomain.com.au to a single Webflow site. Before you start, delete any existing root A records and the www CNAME at Crazy Domains, as Webflow's domain prep guide describes, since extra root A records conflict with the Webflow one. That guide asks you to clear A and CNAME records only, so leave MX records and email TXT records such as SPF in place, or mail stops arriving. One caveat applies at the registrar side. Crazy Domains help pages disagree on whether TXT records need Premium DNS, and the _webflow verification record is a TXT record (see the FAQ below).

To connect the root domain and www:

1. In Webflow, go to Site settings > Publishing > Production and click Add a custom domain. Choose Manually add domain, enter your domain and click Add domain.
2. Copy the records shown. Current values are A @ → 198.202.211.1, CNAME www → cdn.webflow.com, and TXT _webflow → a value beginning one-time-verification=.
3. Log in to the Crazy Domains Account Manager, open the domain and click the DNS Settings tab.
4. Click ADD RECORD, set Choose Type to A Record and leave Sub Domain empty. Enter 198.202.211.1 in IP Address and click SAVE RECORD. Crazy Domains treats an empty Sub Domain and @ as the same root entry, per its Account Manager DNS guide.
5. Add a CNAME Record with Sub Domain www and Hostname cdn.webflow.com.
6. Add a TXT Record with Sub Domain _webflow and the verification value in Content.
7. Back in Webflow, click Check status, then Verify domain, and wait for "Custom domain verified".
8. Click Publish, select the domains and publish. Then click Make default next to the www domain.

Crazy Domains says new records work within 48 hours, and Webflow's DNS error guide says changes typically propagate within a few hours, with up to 48 hours for every location. If your zone still holds the legacy values 75.2.70.75, 99.83.190.102 or proxy-ssl.webflow.com, swap them for the current set using the manual migration steps. Since January 13, 2026, Webflow has blocked publishing to custom domains that still point at legacy records. Keep www as the default unless you need the root: Webflow supports a root default domain once the zone uses the current records.

Use Quick connect through Entri

Quick connect uses Entri to write the records for you after you authorize access to your registrar account. Webflow doesn't publish a list of supported providers, so start the flow and search for Crazy Domains; if it isn't offered, the manual path is the documented fallback. Test it on one domain before relying on it across a client portfolio. It connects both root and www and adds the TXT verification record in one pass.

To use Quick connect:

1. Go to Site settings > Publishing > Production and click Add a custom domain.
2. Choose Quick connect domain, click Continue, enter your domain and click Continue.
3. Choose your DNS provider, authorize Entri, close the window and click Done.

Quick connect sets www as the default domain, and SSL is enabled by default on sites created after November 14th, 2018. If Entri can't find your account or you'd rather not authorize it, the manual path above produces the same result.

Connect a subdomain only

A campaign or blog site can run on blog.yourdomain.com.au while the root domain keeps pointing at Crazy Domains hosting. Each connected subdomain needs one CNAME to cdn.webflow.com plus the _webflow TXT verification record, and you can use Quick connect subdomain or the manual subdomain route. In Crazy Domains, the subdomain label goes in the Sub Domain field.

To connect a subdomain manually:

1. In Webflow, add the subdomain under Add a custom domain and copy the records shown in Production settings.
2. At Crazy Domains, click ADD RECORD, choose CNAME Record, enter the label (for example blog) in Sub Domain and cdn.webflow.com in Hostname, then click SAVE RECORD.
3. Add the _webflow TXT record from Production settings the same way, with the value in Content.
4. In Webflow, click Check status, Verify domain, then publish to the subdomain.

Some providers want a trailing dot on the CNAME target (cdn.webflow.com.); if verification stalls at Crazy Domains, try that form.

Keep Crazy Domains email running through the cutover

Editing only A, CNAME and TXT records leaves mail untouched, because MX records route email independently of web traffic. Webflow doesn't host email, so the provider in your MX records keeps receiving. cPanel email also depends on its MX and mail A records: Crazy Domains warns that "Without them, your email will not function at all". Do not delete any of these when you add the Webflow records, and leave email TXT records such as SPF in place too.

The MX values Crazy Domains documents per mail provider are:

• Titan Email: MX 10 mx1.titan.email, MX 20 mx2.titan.email, plus TXT v=spf1 include:spf.titan.email ~all (Titan MX and TXT)
• Google Workspace in Account Manager DNS: priority 1 SMTP.GOOGLE.COM (Gmail for Google Workspace)
• Exchange on AU servers: priority 5 smtp.ds.network and priority 10 smtp-uk.ds.network, with an SRV record that needs Premium DNS (Exchange MX)
• cPanel email: MX priority 0 or 1 pointing at mail.yourdomain.com.au, plus an A record for mail pointing at the cPanel mail server IP, both preconfigured when DNS sits in the cPanel zone

Form notifications come from no-reply@webflow.com, no-reply@webforms.io and no-reply-forms@webflow.com; if submissions don't reach a Crazy Domains mailbox, allow-list those senders.

Build with the Webflow Data API and the Dreamscape reseller APIs

The API path suits agencies that hold a Crazy Domains reseller account and manage many client sites. No public API or outbound webhook is documented for retail Crazy Domains accounts, so their DNS changes stay manual. Dreamscape Networks International, of which Crazy Domains is a division, publishes documentation for a SOAP API (API-2.1) and a REST API. On the Webflow side, the Data API v2 lists sites and custom domains, publishes sites and registers webhooks. Run these APIs server-side and keep tokens and reseller keys out of page code.

The APIs involved are:

• Dreamscape SOAP API-2.1 handles domain checks, registration, renewal, nameservers and DNS records (DomainDNSAdd, DomainDNSUpdate, DomainDNSRemove) for domains in a reseller account
• Dreamscape REST reseller API covers customers, domain names and hosting products, with DNS record types A, AAAA, TXT, CNAME, MX, CAA, SRV, WEBFWD and MAILFWD
• Webflow's Data API handles sites, custom domains, publishing, Webflow CMS collections and form submissions
• Webflow webhooks send a signed POST on events such as site_publish and form_submission

The Crazy Domains reseller page and the Dreamscape docs are not cross-linked, so confirm with reseller support whether your account supports SOAP API-2.1 or the REST API before using the reseller workflows below.

Audit custom domains across Webflow sites

An agency with dozens of client sites can pull every connected domain in one call and compare it against the Crazy Domains account dashboard, which groups products by domain. This needs a token with the sites:read scope. Use an OAuth token to cover more than one site, since a Site Token covers only one.

To run the audit:

1. Send GET https://api.webflow.com/v2/sites with the header authorization: Bearer YOUR_TOKEN. Each site returns id, displayName, lastPublished and a customDomains array.
2. For one site, call GET https://api.webflow.com/v2/sites/{site_id}/custom_domains. Each item has id, url and a nullable lastPublished.
3. Match each url against your Crazy Domains domain list and note any domain whose lastPublished is null.

Webflow's API doesn't expose a registrar expiry date. Renewal tracking stays with Crazy Domains auto-renewal, which is on by default, or with the SOAP DomainInfo and DomainRenew operations for reseller-held domains. Crazy Domains notes that some domain names can only be renewed within 90 days of expiry.

Trigger a DNS check when a site publishes

A site_publish webhook tells your server which domains a publish went to, so you can resolve each one and alert the team if a Crazy Domains zone still points at legacy records. Registering the webhook needs a sites:write token. The payload carries siteId, publishedOn, domains and publishedBy.

To build the check:

1. Send POST https://api.webflow.com/v2/sites/{site_id}/webhooks with "triggerType": "site_publish" and the url of your receiver.
2. On each request, compute a SHA-256 HMAC of timestamp + ":" + JSON.stringify(request_body) and compare it with the x-webflow-signature header. Treat an x-webflow-timestamp older than 5 minutes as a possible replay.
3. Resolve every entry in domains and compare the answers with 198.202.211.1 and cdn.webflow.com.
4. Return HTTP 200. Anything else is retried up to three times at 10-minute intervals, and repeated failures can deactivate the webhook.

Each site accepts up to 75 webhooks per trigger type, and the site_publish payload carries domain names and a timestamp rather than DNS values, so the record lookup itself is your code.

Update DNS from a reseller account with DomainDNSAdd

Reseller accounts can write the Webflow records to a client zone without opening Account Manager. The SOAP API-2.1 production endpoint is https://soap.secureapi.com.au/API-2.1, with the WSDL at https://soap.secureapi.com.au/wsdl/API-2.1.wsdl and a test endpoint at https://soap-test.secureapi.com.au/API-2.1. Requests use SOAP 1.2 over HTTP.

To write the records:

1. In the Reseller Console, retrieve your API key at Account Settings > API & WHMCS > API Setup. Place the ResellerID and 32-character APIKey in the SOAP header.
2. Call DomainDNSAdd with the root A record, the www CNAME and the _webflow TXT in its Records list, using values from the site's Production settings.
3. Use DomainDNSUpdate only when you intend to replace the zone's records, since it deletes the existing records and writes the ones you send. Use DomainDNSRemove to delete legacy Webflow values.
4. Run the flow against soap-test.secureapi.com.au first, then verify the domain in Webflow exactly as in the manual method.

The REST reseller API exposes the same record types and authenticates with Api-Request-Id and Api-Signature headers, where the signature is MD5 of the request ID plus the API key, if you'd rather avoid SOAP.

What you can build with the Crazy Domains (Freeparking) Webflow integration

• .com.au business site with email left in place: A trades or professional-services business points yourdomain.com.au and www at Webflow with three records while its Titan or cPanel mailboxes keep their MX records. The result is a Webflow marketing site on the .com.au with no mail outage on launch day.
• Campaign microsite on a subdomain: A startup marketer connects campaign.yourdomain.com.au with a single CNAME and leaves the root domain on Crazy Domains hosting. The landing page ships from Webflow while the main site stays untouched.
• Agency build and handoff: A Freelancer or Agency Workspace builds the site, cuts over the client's Crazy Domains DNS, then transfers the site; the Site plan, custom domains and 301 redirects move with it. The client keeps domain ownership and billing at Crazy Domains.
• Secondary domains forwarded to the main site: An owner with extra .com.au names forwards them to the Webflow default domain with Crazy Domains Web Forwarding on Premium DNS. Forwarding requires removing A records on those domains, so use it only for names that aren't connected to Webflow directly.

Once the site is live on your Crazy Domains domain, customize form notification emails so each submission reaches the right mailbox.