Namecheap - Advanced DNS editor

Notes an AI agent reads before it works on namecheap.com: what to open, what to call, what breaks. Written by browser-harness contributors after real runs, and kept on GitHub under the MIT license.

Run it in Browser Use Cloud Source on GitHub

Give it to your agent

Any coding agent

Start the task with this line. The Markdown version is the same notes without the page around them.

Read https://browser-use.com/skills/namecheap.md, then <your task>

Browser Harness

Save the files into your workspace and turn domain skills on. The code below calls its helpers, such as http_get and js. What Browser Harness is.

d="${BH_AGENT_WORKSPACE:-$HOME/.config/browser-harness/agent-workspace}/domain-skills/namecheap"
mkdir -p "$d" && cd "$d"
curl -sLO https://raw.githubusercontent.com/browser-use/browser-harness/main/agent-workspace/domain-skills/namecheap/advanced-dns.md
export BH_DOMAIN_SKILLS=1

Route and selectors

Domain DNS: https://ap.www.namecheap.com/domains/domaincontrolpanel/<domain>/advancedns.
Host Records and Custom MX each have an ADD NEW RECORD link. Scope to the intended section.
New host rows use input[placeholder="Host"]. TXT values use input[placeholder="Value"]; CNAME targets use input[placeholder="Target"].
Record types use Select2. Match the desired li.select2-result by text, scroll it into view inside the dropdown, then measure its rectangle and click.
Host-row save: visible a.save[data-ng-click="listItem.saveRecord()"]. An earlier hidden a.save belongs to DNS Templates; never use an unfiltered document.querySelector('a.save').

Saving and verification

The Angular editor saves asynchronously. Blur populated inputs, click the row's save control, and wait until that row leaves editing state before adding another. Verify the saved row's type, host and value. Filling the first Host/Value input while an earlier row remains editable can overwrite that earlier row.

Custom MX has a separate SAVE ALL CHANGES control. Changing Mail Settings from Email Forwarding to Custom MX removes the forwarding SPF record; publish the chosen provider's SPF separately.

An expired account session can leave the DNS page rendered while save requests fail after redirecting to login. Reload and check whether authentication is required. Do not assume a filled row was saved.

Use a fresh page load and public DNS resolution to verify persistence. Recent negative DNS responses may remain cached at one recursive resolver after another already returns the new record.

advanced-dns.md · updated Oct 9, 2026 · 232 words

Sites change. These notes describe what worked when they were last updated, not a guarantee they still do. If something broke, the fix is a pull request to browser-harness.