Staticbot logoStaticbot.dev

    Connect your domain at Name.com

    Add the certificate and website records in Name.com DNS, including an ANAME record for your root domain.

    Provider steps checked November 18, 2026. Provider dashboards change; if a button has moved, the official help links at the bottom have the current wording.

    N

    You’ll add two or three records in your Name.com account: one that proves you own the domain, and the ones that point it at your site. It takes about 10 minutes, it can be undone, and it doesn’t touch your email.

    Your Staticbot deployment page shows the exact values to paste, with a copy button next to each, and checks whether Name.com is already answering with them. Keep it open next to this guide.

    Before you start

    • Name.com’s URL forwarding is built from A records on the root (ANAME on Domain Safe Pro). Remove a URL forward on the root before adding the ANAME, or the two collide.
    • Records here only work while the domain uses Name.com’s nameservers (the default for domains bought there).

    Open the DNS records at Name.com

    1. Log in to Name.com and click MY DOMAINS (top right).
    2. Click your domain, then Manage DNS Records under Domain Actions.
    3. Choose the Type, fill in Host and Answer, and click Add Record.

    Host and Answer are Name.com’s names for the two boxes you fill in. Type only the part before your domain. Leave Host empty only for a record on the domain itself; a CNAME must always have a Host.

    Server-rendered app hosted on Cloudflare? Its deployment page lists TXT records and a CNAME on www pointing at apps.staticbot.app instead of the records below. Add them in the same form, with the same Host rule.

    Step 1: Add the certificate record

    This record lets Amazon issue the HTTPS certificate for your domain. It doesn’t change where your site or email points. Add one record per certificate record shown on the deployment page:

    TypeCNAME
    Hostthe part before your domain, e.g. _599c0e75…
    Answerthe value ending in .acm-validations.aws
    TTLleave the default

    Save, then go back to the deployment page and click Check my records. Staticbot asks Name.com’s own servers, so you see the answer within seconds. Once it shows Found, the certificate is usually issued within a few minutes.

    Step 2: Point your domain at your site

    The deployment page shows these records once the certificate is issued. If your site lives on a subdomain such as app.yourdomain.com, you only add one CNAME for it.

    For yourdomain.com (the domain itself):

    TypeANAME (Name.com’s ALIAS record)
    Hostleave Host empty
    Answerthe CloudFront address from the deployment page (ends in .cloudfront.net)

    An ANAME can sit next to other records on the domain, such as MX for email.

    For www.yourdomain.com:

    TypeCNAME
    Hostwww
    Answerthe same CloudFront address

    Check it worked

    The deployment page checks each record and tells you what it sees: Found, Not found yet, Wrong value, or Domain typed twice (the domain was typed into the Host box). Most records show up within a minute. Your browser may keep showing the old page for a while after that; a private window shows the new one sooner.

    Working with an AI agent connected to Staticbot? Ask it whether your DNS records are live; it runs the same check.

    Common problems at Name.com

    The root domain still shows the old site or a forwarding page
    A URL forward or old A record is still on the root. Remove it and keep only the ANAME.

    Advanced: change nameservers instead

    Instead of adding records, you can point the domain’s nameservers at Staticbot. You then add no records at all: the certificate and the site, the domain itself included, are set up automatically.

    It’s the right choice when you don’t use the domain for anything else yet: no email on it, no other subdomains. The deployment page recommends it in that case. If the domain has email, Staticbot copies the email records it can see on the domain itself before you switch; records on other names (such as blog.yourdomain.com or email signing keys) have to be re-created, so adding records is usually the safer route there. The deployment page only offers the switch when it’s safe to.

    At Name.com:

    Click MY DOMAINS and select the domain. Under Domain Actions click Manage Nameservers, click Delete All, add each Staticbot nameserver and click Save Changes. Turn off DNSSEC first if it is on.

    More about what moves and what to check: changing nameservers.

    Name.com’s own help pages

    ← All DNS providers