Find the active DNS provider
Manage the records wherever the domain's nameservers currently point. That may be different from the company that sold the domain.
Domain → site, without a transfer
Connect a domain you already own to a live AI website
You already chose the name. Kleap builds what visitors see when they type it.
connect_domain / dns_config pending_dns
DNS
Universal setup
Any registrar
TypeHostValueTTL
A@178.104.71.55default
Awww178.104.71.55default
CNAME
None required by the current flow.
SSL
Automatic after DNS validation.
The short answer
A domain is the address, not the website. Keep the domain at GoDaddy, Hostinger, Infomaniak, or your current registrar. Describe your business in Kleap, review the generated site, and publish it. Then connect the domain in Kleap and add the two A records returned by connect_domain: @ and www both point to 178.104.71.55. You do not need to transfer the domain or replace its nameservers. Leave MX and TXT records untouched so existing email continues to work. Once public DNS resolves to Kleap, Caddy validates the domain, routes both the root and www hostnames, and provisions SSL automatically. Your Kleap site publishes first; the custom address becomes live after DNS propagation.
Step 2 · describe the business
The domain is waiting. Build what goes behind it.
The first version is generated before you change any DNS record.
The complete route
From a name you bought to a secure live site
- 01
Keep the domain
Ownership, renewal, and nameservers stay with your current registrar.
- 02
Describe the business
Tell Kleap what you do, who it serves, and what visitors should do next.
- 03
Publish the site
Review the generated page and publish it before attaching a custom domain.
- 04
Connect the domain
Open Settings → Domains or call connect_domain with the live app id and domain.
- 05
Add DNS; SSL follows
Paste the exact A records below. Kleap verifies routing and provisions TLS automatically.
DNS
Where to click in Any registrar
The screen names vary, but every registrar has a DNS or DNS zone page. Edit only the records that route web traffic. Do not replace nameservers and do not delete email records.
Registrar dashboard → Domain → DNS / DNS zone
Learn how A records work at GoDaddy Official documentation checked August 28, 2026.
Replace conflicting web records
For @ and www, remove old A, AAAA, ALIAS, or CNAME records that point elsewhere. Add A records to 178.104.71.55.
Keep mail and verification records
MX, SPF, DKIM, DMARC, and unrelated TXT records do not route the website. Leave them in place.
Wait for public DNS
The dashboard may update quickly, but cached DNS can take longer. Kleap completes SSL after the new records resolve publicly.
Propagation: Registrar guidance ranges from minutes to 24–72 hours. Do not remove email records while waiting.
What changes — and what stays
The website moves. Domain ownership and email do not.
You keep
- Domain ownership and renewals
- Nameservers and registrar account
- MX, SPF, DKIM, DMARC, and other TXT records
- Existing email inboxes and forwarding
You change
- A record @ → 178.104.71.55
- A record www → 178.104.71.55
- Old A/AAAA/CNAME records for @ or www that conflict
- Nothing else in the DNS zone
Agent tool
connect_domain, documented
connect_domain attaches a domain the user already owns to a live Kleap app. It does not buy or transfer the domain, and it cannot edit the registrar account for the user.
Inputs
- app_id: number
- A published app owned by the caller.
- domain: string
- Bare domain, without protocol or path.
Outputs
status
already_connected
dns_config
warnings
connect_domain({
app_id: 123,
domain: "mybusiness.com"
})
→ status: "pending_dns"
→ A @ 178.104.71.55
→ A www 178.104.71.55
→ SSL: automatic after DNS resolves01
Publish first
A completed create_app or modify_app already counts as live.
02
Return DNS exactly
Present dns_config without inventing a CNAME target.
03
Verify before claiming live
pending_dns is not the same as a working custom URL.
Troubleshooting
If the domain does not show the site yet
The old site still appears
Check that the active nameservers belong to the DNS panel you edited, then wait for resolver caches to expire.
The root works but www does not
Add the second A record: host www, value 178.104.71.55. Remove an old www CNAME first if one conflicts.
SSL is pending
Confirm both A records resolve to Kleap and remove conflicting AAAA records. Certificate provisioning starts automatically after validation.
Common questions
Before you touch DNS
Do I need to transfer my domain to Kleap?
No. The domain remains registered and renewed where you bought it. You only point its web records to the published Kleap site.
Will changing these A records break my email?
Not if you leave MX and email-related TXT records untouched. A records route website traffic; MX, SPF, DKIM, and DMARC control mail delivery and trust.
Does Kleap require a CNAME?
No CNAME is required by the current connect_domain flow. It returns A records for @ and www, both pointing to 178.104.71.55.
When does SSL turn on?
Kleap provisions SSL automatically after the domain resolves publicly to its proxy. DNS propagation speed depends on the registrar and cached TTL.
Can the agent buy or renew a domain for me?
No. connect_domain only attaches a domain you already own. Domain purchases and renewals still require your confirmation with the registrar or in Kleap's domain checkout.