Skip to content
Docs

basemodo domains verify

Look for a custom domain's DNS records now; once found, the App answers there.

Terminal window
basemodo domains verify [OPTIONS] <HOSTNAME>

Basemodo also looks by itself every few minutes for a week. Verified, the App answers at the hostname at once, and over HTTPS once its certificate is issued (status active); the error says which record is missing otherwise.

Arguments

  • HOSTNAME (required): The hostname, as added.
  • --app <APP>: The App whose custom domains to change. Default: the one named after the current folder.

Like every command, it also takes the global options --json and --api-url.

Examples

Check the records you added:

Terminal window
basemodo domains verify app.example.com

Output

With --json, it prints {"hostname", "url", "status" (pending, issuing, active or failed), "records": [{"type", "name", "value"}], "problem", "created_at", "verified_at", "certificate_expires_at"}. Records not found yet are an error with code domain_not_verified naming the missing one.

From an agent

The local MCP serves it as the tool domains_verify. It changes things, so an agent's client may ask you before it runs. Its arguments are the command's, named as JSON keys: hostname (text), app (text). It answers what the command prints with --json.

Explained in