Hover

Connect Hover domains with Webflow to publish your sites on custom domains with automatic SSL and global CDN delivery.

→
↗
►
↓
←
↑
Install app
→
↗
►
↓
←
↑
View website
→
↗
►
↓
←
↑
View lesson
→
↗
►
↓
←
↑
A record settings
→
↗
►
↓
←
↑
CNAME record settings
Hover

How to integrate Hover with Webflow

Connecting a Hover domain to Webflow lets you publish sites on custom domains with automatic SSL certificates and global content delivery. Manual DNS configuration takes about 15 minutes and gives you direct control over nameserver settings.

You configure DNS records in Hover's management panel to point your domain at Webflow's hosting infrastructure. This guide covers DNS configuration for root and www domains.

Connect Hover domains to Webflow by adding DNS records in your Hover account that point to Webflow's hosting servers. This method works for all domain extensions and gives you complete control over DNS settings.

The manual domain connection process requires three specific record types:

  1. An A record for your root domain
  2. A CNAME record for www
  3. A TXT record for domain verification

Start in your Webflow site settings by adding your custom domain under Site settings > Publishing > Production. Webflow generates a TXT verification code and displays the exact DNS records you need.

Then, log into your Hover account, navigate to DNS management for your domain, and add these records:

  • A Records: Add two A records with host @ pointing to 75.2.70.75 and 99.83.190.102 for your root domain
  • CNAME Record: Add a CNAME record with host www pointing to proxy-ssl.webflow.com for www subdomain
  • TXT Record: Add a TXT record with host _webflow and the verification code from Webflow to confirm ownership

After adding records in Hover, DNS changes propagate globally within 15 minutes to 48 hours. Hover's DNS propagation often takes three to four hours.

Use whatsmydns.net to check propagation status across different locations. Webflow automatically provisions an SSL certificate from Let's Encrypt once DNS records resolve correctly, typically within a few hours of propagation completing.

The most frequent configuration errors involve incorrect A record IP addresses or CNAME records pointing to the wrong target.

According to Webflow's DNS troubleshooting guide, verify that your A records use exactly 75.2.70.75 and 99.83.190.102 and your CNAME uses proxy-ssl.webflow.com without additional paths or trailing slashes.

Remove any conflicting DNS records from previous hosting providers to prevent "too many redirects" errors.

What you can build

Integrating Hover domains with Webflow lets you publish sites on custom domains with automatic SSL certificates and global content delivery.

  • Business websites: Launch company sites on branded domains like company.com with www and root domain both working correctly, automatic HTTPS, and fast loading through Webflow's CDN across global locations
  • Client agency projects: Manage multiple client domains from a single Hover account, point each domain to separate Webflow workspaces, and handle DNS configuration without accessing client registrar accounts
  • Marketing landing pages: Deploy campaign-specific landing pages on dedicated domains or subdomains, update content through Webflow's visual editor without DNS changes, and maintain consistent branding across multiple domains
  • Portfolio and personal sites: Publish creative portfolios on custom domains with full creative control over design, automatic mobile optimization, and professional email addresses through Hover's email forwarding service

Frequently asked questions

  • Connecting a Hover domain requires three specific DNS record types according to Webflow's domain connection documentation. Add an A record with host @ pointing to IP address 198.202.211.1 for your root domain. Add a CNAME record with host www pointing to cdn.webflow.com for the www subdomain. Add a TXT record with host _webflow containing the verification code that Webflow generates in your site settings to confirm domain ownership. These records tell DNS servers to route traffic for your domain to Webflow's hosting infrastructure.

    Connecting a Hover domain requires three specific DNS record types according to Webflow's domain connection documentation. Add an A record with host @ pointing to IP address 198.202.211.1 for your root domain. Add a CNAME record with host www pointing to cdn.webflow.com for the www subdomain. Add a TXT record with host _webflow containing the verification code that Webflow generates in your site settings to confirm domain ownership. These records tell DNS servers to route traffic for your domain to Webflow's hosting infrastructure.

  • Hover.com (the domain registrar) does not provide comprehensive APIs or webhooks suitable for automated domain management integration with Webflow. Domain connection between Hover and Webflow relies on manual DNS configuration through Hover's control panel rather than API automation.

    The Webflow CMS API supports programmatic site publishing to domains you've already configured, but Hover doesn't offer equivalent APIs for DNS record automation. For workflows requiring API-based domain management, consider registrars that provide dedicated domain management APIs.

    Hover.com (the domain registrar) does not provide comprehensive APIs or webhooks suitable for automated domain management integration with Webflow. Domain connection between Hover and Webflow relies on manual DNS configuration through Hover's control panel rather than API automation.

    The Webflow CMS API supports programmatic site publishing to domains you've already configured, but Hover doesn't offer equivalent APIs for DNS record automation. For workflows requiring API-based domain management, consider registrars that provide dedicated domain management APIs.

  • The "unable to verify domain" error typically indicates that the TXT record with your verification code isn't configured correctly in Hover's DNS settings. According to Webflow's DNS troubleshooting guide, verify that you've added a TXT record with hostname _webflow and the exact verification code from your Webflow site settings without extra spaces or characters.

    DNS propagation can delay verification, so wait at least 15 minutes after adding the TXT record before attempting verification again. Use DNS lookup tools to confirm the TXT record appears in public DNS queries for your domain. If verification continues failing after 48 hours, check that no conflicting TXT records exist and that Hover's nameservers are properly configured.

    The "unable to verify domain" error typically indicates that the TXT record with your verification code isn't configured correctly in Hover's DNS settings. According to Webflow's DNS troubleshooting guide, verify that you've added a TXT record with hostname _webflow and the exact verification code from your Webflow site settings without extra spaces or characters.

    DNS propagation can delay verification, so wait at least 15 minutes after adding the TXT record before attempting verification again. Use DNS lookup tools to confirm the TXT record appears in public DNS queries for your domain. If verification continues failing after 48 hours, check that no conflicting TXT records exist and that Hover's nameservers are properly configured.

  • Yes, you can use Hover's email forwarding and hosting services while your domain points to Webflow for website hosting. DNS records for email (MX records) operate independently from website hosting records (A and CNAME records).

    Configure your domain's A and CNAME records to point to Webflow's hosting infrastructure while maintaining separate MX records that point to Hover's email servers. The Hover DNS management guide explains that you can have different DNS record types serving different purposes simultaneously.

    This setup lets you host your website on Webflow's infrastructure while receiving email through Hover's email services without conflicts between the two services.

    Yes, you can use Hover's email forwarding and hosting services while your domain points to Webflow for website hosting. DNS records for email (MX records) operate independently from website hosting records (A and CNAME records).

    Configure your domain's A and CNAME records to point to Webflow's hosting infrastructure while maintaining separate MX records that point to Hover's email servers. The Hover DNS management guide explains that you can have different DNS record types serving different purposes simultaneously.

    This setup lets you host your website on Webflow's infrastructure while receiving email through Hover's email services without conflicts between the two services.

Hover
Hover
Joined in

Category

Domains

Description

Hover is a domain registrar that provides domain registration and DNS management services. Hover supports standard DNS record types including A records, CNAME records, and TXT records required for connecting domains to website hosting platforms. The service is used by developers and agencies managing multiple client domains who require straightforward domain management without upsells.

→
↗
►
↓
←
↑
Install app

This integration page is provided for informational and convenience purposes only.

Other Domains integrations

Other Domains integrations

No items found.

Related integrations

No items found.

Get started for free

Try Webflow for as long as you like with our free Starter plan. Purchase a paid Site plan to publish, host, and unlock additional features.

Try Webflow for as long as you like with our free Starter plan. Purchase a paid Site plan to publish, host, and unlock additional features.

Get started — it’s free