IONOS

Point your IONOS domain at a Webflow site with an A record and CNAME, keep your MX records on IONOS, and let Quick Connect handle the DNS wiring through the Domain Connect protocol. Web traffic reaches your pages, email keeps flowing to @yourdomain.com, and neither side takes the other down.

This setup fits small to mid-sized businesses running a domain, email, and a Webflow site as one stack. It also fits agencies managing many client sites, where IONOS APIs and the Webflow Data API automate DNS record creation during onboarding.

How to integrate IONOS with Webflow

What is IONOS? IONOS is a web hosting and cloud services provider offering domains, shared hosting, email, VPS, and dedicated servers. For your purposes, it works mainly as a domain registrar and email host. IONOS manages domain registration and professional email through a browser-based control panel, while your site build and hosting stay in Webflow.

[image placeholder]

Most teams use IONOS and Webflow together to put a custom domain on a Webflow site while keeping email on dedicated mail infrastructure. Your pages render and serve from Webflow, IONOS DNS routes traffic to your site, and IONOS MX records keep @yourdomain.com email flowing. This separation gives you independent uptime for web and email.

The IONOS-Webflow integration supports three approaches:

• DNS record entry and Quick Connect point your IONOS domain at Webflow without writing code.
• Code Embed and custom code let you add IONOS chatbots, tracking scripts, or other third-party widgets to your pages.
• The Webflow Data API and IONOS APIs give you full control over DNS provisioning and Webflow CMS sync, but require server-side development.

Most implementations use the DNS method on its own, then add API automation only when managing many sites.

Connect your IONOS domain with DNS records or Quick Connect

DNS configuration is the primary connection between IONOS and Webflow. You retrieve the records you need from your Site settings, then enter them in the IONOS control panel. This requires no code, and IONOS lets you edit every record in the browser. You need a paid Site plan to connect any custom domain.

This method covers two paths:

• Manual DNS entry, where you add each record yourself
• Quick Connect, where DNS gets configured automatically through Domain Connect

[image placeholder]

Add DNS records manually

Use manual entry when you want direct control over every record or when Quick Connect isn't available in your Site settings. You add an A record at the root and a CNAME for www, plus a TXT record for verification.

To connect the domain manually:

1. Go to Site settings > Publishing > Production, select Add a custom domain, then Manually add domain.
2. Copy the DNS records shown on screen. Always use the values in your own Site settings, since infrastructure is migrating and values can differ per site.
3. In IONOS, log in and open the Domain and SSL tile, select the gear icon for your domain, then open DNS.
4. Add an A record with hostname @ pointing to the IP value shown in your Site settings (currently 198.202.211.1).
5. Add a CNAME record with hostname www pointing to cdn.webflow.com.
6. Add a TXT record with hostname _webflow and the one-time-verification value from your Site settings.

The setup uses an A record at the root rather than a CNAME, because a CNAME at @ conflicts with MX records, and that conflict would break your email. The manual domain connection guide covers the full process and troubleshooting.

Use Quick Connect for automated DNS

Quick Connect configures your DNS records automatically through the Domain Connect protocol. IONOS supports Domain Connect with a default _domainconnect CNAME on all domains, so Quick Connect can write the A, CNAME, and TXT records for you. This is the fastest path when you want to skip manual record entry.

To use Quick Connect:

1. Go to Site settings > Publishing > Production and look for the Quick Connect option for IONOS.
2. Authorize the connection, then let Domain Connect apply the DNS records.

If Quick Connect isn't available for your domain, fall back to manual DNS entry. The IONOS integration page documents both paths.

Keep IONOS email and SSL working

Pointing your domain to Webflow doesn't preserve email on its own. Since email hosting isn't part of the platform, you must keep your IONOS MX records active and add authentication records so mail keeps delivering. SSL provisions automatically once DNS verification completes, so you don't generate a CSR.

To preserve email deliverability:

1. In IONOS DNS settings, edit the first MX record so it points to mx00.ionos.com, then save.
2. Edit the second MX record to point to mx01.ionos.com.
3. Add the IONOS SPF (TXT) record from Add Record > IONOS SPF (TXT).
4. Add each DKIM CNAME record using the hostname and points-to values generated in your IONOS email authentication setup.

If your domain uses CAA records, add both 0 issue "pki.goog; cansignhttpexchanges=yes" and 0 issue "letsencrypt.org" so SSL can provision correctly. The CAA configuration guide explains why both entries are required.

Add IONOS components with Code Embed elements

Use custom code when you want to add IONOS widgets, chatbots, or tracking scripts to your pages. You can inject third-party code in three places: site-wide, per page, and inline on the canvas. This method covers presentation-layer scripts only and doesn't run server-side languages.

[image placeholder]

For site-wide or per-page scripts, add them through custom code in head and body tags. For a specific spot in your layout, drop a Code Embed element on the canvas.

To add a script with a Code Embed element:

1. Open the Add panel and drag a Code Embed element onto the canvas.
2. Paste your IONOS widget or tracking snippet into the element.
3. Save and publish the site to render the embed.

Code Embed doesn't support server-side languages like PHP, Python, Ruby, or Perl. Use it for client-side scripts and HTML widgets only.

Automate with Make

Make is the only no-code automation platform with connectors for both Webflow and IONOS, so you can build workflows that span both services. The other major platforms support Webflow but not consumer IONOS domain and email services — n8n has an IONOS connector, but it is scoped to IONOS Cloud infrastructure only, not consumer ionos.com domain and email services. Use Make when you want to trigger an action in one service based on an event in the other.

The Make connectors support these directions:

• Webflow trigger (new form submission, new order, item changes) → IONOS action
• IONOS event → Webflow action (create or update a live CMS item, publish a site)

The Webflow connector offers 40 modules (2 triggers, 26 actions, and 12 searches), and the IONOS connector handles IONOS operations. There's no pre-built combined template, so you build the scenario from the available modules. Zapier, IFTTT, n8n, and viaSocket support Webflow but do not connect to consumer IONOS services.

Build with the Webflow and IONOS APIs

The API path gives you full control over DNS provisioning and content sync, but it requires server-side development. Agencies use it to create DNS records automatically when onboarding many clients at once. You handle authentication, error handling, and rate limits in your own backend code.

[image placeholder]

Three API surfaces matter for this integration:

• The IONOS DNS Hosting API handles zone and record management using an X-API-Key header
• The Webflow Data API handles CMS collections, custom domains, and site publishing
• Webflow webhooks trigger real-time events like collection_item_created and site_publish

The Data API has no endpoints for creating or modifying DNS records at an external provider, so DNS work happens entirely through the IONOS DNS API.

Automate DNS record creation for agency onboarding

When you onboard multiple clients, you can script the IONOS DNS API to create the A, CNAME, and TXT records each Webflow site needs. This removes the manual record entry step for every new domain. Pair it with the Webflow Data API to read the custom domain values per site.

To provision DNS records programmatically:

1. Call GET /v1/zones on the IONOS DNS API to retrieve the zone ID for the domain.
2. Call POST /v1/zones/{zoneId}/records to create the A record (@ → 198.202.211.1).
3. Call POST /v1/zones/{zoneId}/records again to create the CNAME (www → cdn.webflow.com).
4. Call POST /v1/zones/{zoneId}/records once more to create the TXT verification record.
5. Call POST /v2/sites/{site_id}/publish on the Webflow Data API to publish the site once DNS verifies.

The IONOS DNS Hosting API allows 1,200 requests per hour per key. Always read the current A record value from each site's Site settings before scripting, since infrastructure migration means values can differ per site.

Sync external data into the Webflow CMS

You can push content from an external source into CMS items, then trigger a republish. IONOS doesn't offer webhooks for CMS sync, so the workflow originates from outbound webhooks or from polling IONOS APIs. This pattern keeps your site in step with data managed elsewhere.

To sync and republish:

1. Register a webhook with POST /v2/sites/{site_id}/webhooks for events like collection_item_changed.
2. Use PATCH /v2/collections/{collection_id}/items/{item_id} to update an item when source data changes.
3. Call POST /v2/sites/{site_id}/publish to push the changes live.

The CMS plan supports 2,000 items and the Business plan supports 10,000, so size your sync workflow to the plan tier. Data API rate limits run at 60 requests per minute on Starter and Basic, and 120 on CMS, eCommerce, and Business.

What can you build with the IONOS Webflow integration?

Integrating IONOS with Webflow lets you run a branded domain and professional email alongside a Webflow site without moving your domain registration or hosting into a single locked stack.

• Custom domain on a Webflow site: Point yourbrand.com at Webflow with an A record and CNAME, so visitors reach your Webflow-hosted marketing site at your own domain instead of a .webflow.io subdomain.
• Web and email on separate infrastructure: Keep hello@yourbrand.com running on IONOS mail servers while your site serves from Webflow, so an email outage never takes down your site and a site change never breaks mail.
• Agency multi-client domain provisioning: Script the IONOS DNS API and Webflow Data API to create A, CNAME, and TXT records across dozens of client domains during onboarding, instead of editing each control panel by hand.
• Embedded IONOS widgets on Webflow pages: Drop a Code Embed element on a page to add an IONOS chatbot or tracking script, so a support widget appears on the live site without a separate platform.

If you need more control over bulk DNS provisioning across many client domains, the API integration path covers those cases with full flexibility.