If your Webflow site isn't working after 3 days, you may be using the wrong A record IP addresses. Webflow uses shared IP addresses, not individual ones, and the correct IP addresses depend on whether you’re using a Webflow-provided domain or a custom domain.
1. Find the Correct Webflow A Records
- For a custom domain, Webflow currently requires these A records:
- 75.2.70.75
- 99.83.190.102
- The IP you mentioned (23.235.33.229) is outdated and no longer valid. Update your A records in your domain registrar’s DNS settings.
2. Check Your Current DNS Records
- Use a DNS lookup tool like Google Dig or MXToolbox and enter your domain.
- Look for A records to see if they match 75.2.70.75 and 99.83.190.102.
- If your domain still shows the old IP (23.235.33.229), it means your DNS settings haven’t been updated correctly.
3. Update Your DNS Settings
- Log into your domain registrar (e.g., GoDaddy, Namecheap, Google Domains).
- Remove any old A records (including 23.235.33.229).
- Add the correct Webflow A records:
- 75.2.70.75
- 99.83.190.102
- If you use the "www" version of your domain, ensure you set a CNAME record pointing www → proxy-ssl.webflow.com.
4. Allow Proper DNS Propagation
- DNS changes usually take a few minutes to 48 hours to fully propagate.
- You can track propagation using WhatsMyDNS.
5. Publish Your Webflow Site Again
- Go to Webflow → Project Settings → Publishing → Publish to Custom Domain.
- If everything is set up correctly, your site should go live within minutes.
Summary
Your issue is likely caused by using the wrong A record IP address (23.235.33.229 is outdated). Replace it with 75.2.70.75 and 99.83.190.102, then republish your Webflow site. Propagation may take up to 48 hours before your site is fully live.