Help Center
Seller Guide

Domain verification

NS, TXT, and CNAME verification in globNIC — the only methods supported by the product API, with exact values and where to click.

Updated 2026-04-26

What verification does

  • Proves you control the domain (DNS-level check).
  • Unblocks listing where applicable and sets nameServerStatus in the database so DNS management and parking can go live, depending on method and follow-up.
  • The verify API only accepts these methods: NS, TXT, CNAME (see POST /api/member/domains/verify — invalid methods return 400).

Older documentation sometimes mentioned file-upload or HTML meta methods — the current member and API flow is DNS-only as above. Ignore any out-of-date third-party text.

Where to do it in the app

  • Per domain: go to /member/domains/{domain}/verify (replace with your FQDN). The page loads your token and status with GET /api/member/domains/verify?domain=... and runs checks with POST /api/member/domains/verify.

Method A — NS (nameservers)

  • Set only:
    • ns1.globnic.com
    • ns2.globnic.com
  • The member UI (DnsSetupGuide) states this path unlocks the full experience (parking, SSL, analytics, AI) once verification completes.

Method B — TXT (keep existing nameservers)

  • Name / Host: _globnic-verify (or full name _globnic-verify.{domain} if your host requires the FQDN).
  • Value: your per-domain verification token from the verify page (from GET /api/member/domains/verify response).
  • TTL: auto or 300 as suggested in the UI.

Method C — CNAME (point root to globNIC)

  • Name / Host: @ or the bare domain; some UIs use the full example.com label.
  • Target / Points to: parking.globnic.com
  • Cloudflare: use DNS only (grey cloud), not proxied, per the in-app CNAME section.

Cloudflare: automatic record creation (optional)

  • On the same verify page, Using Cloudflare? Auto-Configure DNS uses POST /api/member/domains/cloudflare-dns with a one-time token using Cloudflare’s Edit zone DNS template. The token is not stored; you still need to run verification after propagation (typically 1–2 minutes per on-screen text).

Bulk verification

Troubleshooting (short)

  • ESERVFAIL / not pointing to globNIC: for NS, ensure both ns1/ns2 are set; no mixed registrar defaults.
  • TIMEOUT / slow: retry later — bulk verify can mark pending_propagation.
  • Wrong token: re-copy TXT from the verify page; each domain’s token is separate.

Related