Skip to main content

Overview

Use Domain Routing when your platform doesn’t support URL rewrites (Framer, Webflow, Wix, Cafe24, ImWeb, etc.).
yourdomain.com → DNS (A records) → Anymorph proxy

                          /a/* → Anymorph pages
                          other → Your origin site
Anymorph acts as a reverse proxy—non-Anymorph paths forward to your original site.

DNS Records Required

Domain Routing uses A records for all domains (root and subdomains).

Step 1: Add ACME Challenge Record

To enable SSL certificate issuance before switching traffic, add this CNAME first:
TypeNameValue
CNAME_acme-challenge.yourdomain.com_acme-challenge.yourdomain.com.challenges.saascustomdomains.com
Adding this CNAME first enables zero-downtime migration. Your SSL certificate is issued before you change A records.

Step 2: Add A Records

After SSL status shows Active, add these A records:
TypeNameValue
A@ (or yourdomain.com)99.83.186.151
A@ (or yourdomain.com)75.2.96.173
Add both A records for high availability (AWS Global Accelerator).

For Subdomains

For subdomains like blog.example.com, follow the same process:
TypeNameValue
CNAME_acme-challenge.blog_acme-challenge.blog.example.com.challenges.saascustomdomains.com
Ablog99.83.186.151
Ablog75.2.96.173

Zero-Downtime Setup

1

Add ACME challenge CNAME

Your existing site stays unaffected. SSL issuance begins in the background.
2

Wait for SSL verification

In Anymorph Dashboard, wait until SSL status shows Active.
3

Add A records

Traffic switches to Anymorph. Non-Anymorph paths continue serving from your origin.

Origin URL Configuration

When setting up Domain Routing, you need to specify your site’s Origin URL—the original platform URL before connecting to Anymorph.
Use your platform’s staging/default URL, not cdn.webflow.com or other shared CDN addresses.

Platform-Specific Origin URLs

Use your .webflow.io staging URL:
Origin URL: https://your-site.webflow.io
How to find it:
  1. Open your site in Webflow Designer
  2. Click Publish button (top right)
  3. Your staging URL appears as yoursite.webflow.io
Or: Site Settings → Publishing → Staging
Do NOT use cdn.webflow.com with Host header. When you change DNS from Webflow’s CNAME to Anymorph’s A records, Webflow detects this and deactivates your custom domain—resulting in 404 errors.
The .webflow.io URL works regardless of your DNS configuration and custom domain status.
Use your .framer.app URL:
Origin URL: https://your-site.framer.app
Find it in: Framer → Site Settings → Domains → Base URL
Use your .wixsite.com URL:
Origin URL: https://username.wixsite.com/mysite
Find it in: Wix → Dashboard → Site Actions → Rename Site
Use your .squarespace.com URL:
Origin URL: https://your-site.squarespace.com
Find it in: Squarespace → Settings → Domains → Built-in Domain
Use the platform’s default/staging URL (usually the URL you had before connecting a custom domain).
Origin URL: https://your-default-platform-url.com

DNS Provider Guides

  1. Go to DNS > Records.
  2. Click Add Record.
  3. Add the ACME CNAME first, then add A records.
  4. Set proxy status to DNS only (gray cloud)—not Proxied.
Cloudflare’s proxy (orange cloud) can interfere with SSL issuance.
  1. Go to My Products > DNS.
  2. Under DNS Records, click Add.
  3. For root domains, enter @ in the Name field.
  4. Add ACME CNAME first, wait for SSL, then add A records.
  1. Go to Domain List > Manage > Advanced DNS.
  2. Click Add New Record.
  3. For root domains, enter @ in the Host field.
  1. Go to Hosted Zones and select your domain.
  2. Click Create Record.
  3. For root domains, leave Name blank.
  4. Set Record type to A.
# CLI example
aws route53 change-resource-record-sets \
  --hosted-zone-id Z1234567890 \
  --change-batch '{
    "Changes": [{
      "Action": "CREATE",
      "ResourceRecordSet": {
        "Name": "example.com",
        "Type": "A",
        "TTL": 300,
        "ResourceRecords": [
          {"Value": "99.83.186.151"},
          {"Value": "75.2.96.173"}
        ]
      }
    }]
  }'
  1. Go to Domain Management > DNS Settings.
  2. Ensure nameservers point to Cafe24.
  3. Add the ACME CNAME record.
  4. Add both A records with Anymorph IPs.
Cafe24 doesn’t support URL rewrites—Domain Routing is required.
  1. Go to Admin > Settings > Domain.
  2. Use ImWeb’s assigned nameservers.
  3. Add DNS records in the ImWeb dashboard.
ImWeb doesn’t support path-based routing. Use a subdomain with Domain Routing if needed.

Domain Status

After adding DNS records, your domain progresses through these states:
StatusMeaning
Pending SSLWaiting for ACME challenge verification
SSL ActiveCertificate issued, waiting for A records
ActiveFully configured and serving traffic
DNS propagation typically takes 5–30 minutes but can take up to 48 hours.

Health Check

To verify your configuration, run:
curl https://yourdomain.com/__check__
Response values:
  • status: "connected" — Working correctly
  • status: "disabled" — Domain disabled
  • status: "not_configured" — Domain not found

Troubleshooting

  • Verify the ACME challenge CNAME record exists and is correct.
  • Check for CAA records that might block certificate issuance.
  • Ensure the CNAME value ends with .challenges.saascustomdomains.com.
  • Verify A record values: 99.83.186.151 and 75.2.96.173.
  • Check DNS propagation at whatsmydns.net.
  • Allow up to 48 hours for full propagation.
  • Clear your browser cache.
  • Verify the Origin URL in Anymorph Dashboard.
  • Confirm both A records point to Anymorph.
  • Wait for SSL certificate issuance to complete.
  • Verify your origin site supports HTTPS.

FAQ

No. Follow zero-downtime setup: add ACME CNAME first, wait for SSL, then switch A records.
Yes. Change A records back to your original hosting provider. With low TTL, changes propagate within minutes.
MX records are unaffected. Anymorph handles only HTTP/HTTPS traffic.
A records work consistently for both root domains and subdomains. CNAME records cannot be used on root domains (RFC 1912).
Not recommended. Cloudflare’s proxy can interfere with SSL issuance. Use DNS only (gray cloud) mode.