Point the root at Framer’s two addresses — 31.43.160.6 and 31.43.161.6 — and www (or any subdomain) with a CNAME to sites.framer.app. Framer’s older addresses stopped working on 1 July 2025, so a domain still on them is down. Framer does not serve IPv6: remove every AAAA record.
The records to add
| Name | Type | Value |
|---|---|---|
@ | A | 31.43.160.6 |
@ | A | 31.43.161.6 |
www | CNAME | sites.framer.app |
Some DNS hosts need the trailing dot: sites.framer.app.
| Old records | 52.223.52.2 and 35.71.142.77 — no longer supported since 1 July 2025 |
| IPv6 | Not supported — remove AAAA records |
| Certificate | Let’s Encrypt and ZeroSSL |
Check your domain
Enter your domain: we look up its records and compare them with what Framer expects — the root, www, and any record left over from before.
Step by step
- In Framer, open Site settings → Domains and add the domain.
- At your DNS host, set the root’s A records to 31.43.160.6 and 31.43.161.6, and www to a CNAME for sites.framer.app.
- Remove every other A record, every AAAA record, parking records and URL forwarding.
- Wait for Framer to confirm the domain and issue the certificate.
What to remove
- The old 52.223.52.2 and 35.71.142.77.
- All AAAA records — they also block the certificate.
- Parking records, hidden extra A records and URL forwarding.
The certificate
Framer issues certificates from Let’s Encrypt and ZeroSSL; if the domain has CAA records, allow both (Framer’s own domain lists letsencrypt.org and sectigo.com).
Common mistakes
- Keeping the old addresses after July 2025.
- Cloudflare’s proxy switched on — it must be DNS only.
- AAAA records left from the previous host.
Sources
Records checked on 26 September 2026 against these official sources:
- Framer Help: How to connect a custom domain — framer.com
- Framer Help: Troubleshooting custom domain issues — framer.com
- Framer Help: Connect to our improved hosting — framer.com