A 403 Forbidden error on your Webflow site, but only when using your Ionos domain, typically indicates a misconfiguration in your domain DNS settings or Webflow's security settings. Follow these steps to resolve the issue:
1. Check Webflow's Required DNS Settings
- Go to Webflow Project Settings > Hosting.
- Under Custom Domains, find the required A records and CNAME record:
- A records: (a) 75.2.70.75, (b) 99.83.190.102
- CNAME record:
proxy-ssl.webflow.com
(for the www subdomain) - In your Ionos DNS settings, confirm that:
- Your A records point to Webflow (not Ionos default IPs).
- Your CNAME record for www points to Webflow’s proxy and not Ionos.
2. Remove Conflicting or Redundant DNS Entries
- If Ionos has existing A records pointing to their own servers, delete those.
- Ensure you only have one set of A records pointing to Webflow.
- If you see an AAAA record (IPv6), remove it—Webflow doesn’t use IPv6.
3. Check SSL Settings in Webflow
- In Project Settings > Hosting, make sure SSL is enabled.
- If SSL is off, Webflow may block access via HTTPS, leading to a 403 error.
4. Double-Check Ionos Domain Forwarding
- Ionos sometimes applies automatic domain forwarding that can cause conflicts.
- Ensure your domain does not have HTTP forwarding set up within Ionos.
5. Wait for DNS Propagation (Up to 48 Hours)
- After making corrections, allow up to 48 hours for the changes to take effect.
- Use a DNS checker tool (like whatsmydns.net) to confirm that your domain points to Webflow’s IPs globally.
Summary
Your Ionos DNS settings likely have incorrect A records or CNAME settings. Update them to match Webflow’s requirements, remove any conflicting entries, and ensure SSL is enabled. Then, allow time for changes to propagate. If the issue persists, flush your local DNS cache or contact Ionos support to ensure no blocking occurs on their side.