Observed by Atlas — nobody has proved they control this domain. Is it yours?
Custom Domain
OBSERVEDAutomated custom domain connection, DNS, and HTTPS for SaaS
- FRESHNESS
- 0.66
- DECAYS BETWEEN READS
- READINGS
- —
- VERIFIED / MEASURED
- VOUCHES
- 0
- SIGNED STATEMENTS
- THREADS
- 0
- FIELD NOTES
- CLICKS · 28D
- 1
- BOT-FILTERED
- FIRST SEEN
- AUG 18
- IN THE FLOW

Custom Domain lets a SaaS product's customers connect their own domain without ever opening a DNS panel. It detects the customer's DNS provider, writes the necessary records, verifies ownership, and issues and renews TLS certificates automatically. It is built for developers via a REST API, SDKs, a drop-in widget, and an MCP server for AI agents.
Nothing measured yet. A reading is a measurement with its evidence attached — uptime checked, pricing re-read against what the page claims. Raise a checkable claim in a field note below and Atlas will measure it.
10 domain connections per year · Connect DNS engine · REST API, webhooks & dashboard · Drift detection included
600 domain connections/yr · Everything in Starter · 600 automatic domain connections/yr
600 domain connections/yr + overage · Everything in Startup · Reverse-proxy edge + automatic HTTPS · Overage in 1,000-domain blocks
12,000 domain connections/yr · Everything in Growth · Fleet-scale monitoring policies + alerting
12,000+ domain connections/yr · Everything in Premium · White-label branding & domain resale
Every crawl is diffed. Material changes are listed.
Nobody has vouched for Custom Domain yet.
A vouch says you use it. Your handle, how long, and an optional note.
I use this — vouchHave a question about Custom Domain? Ask the people using it.
No field notes yet. A field note is about use: what broke, what it replaced, what the docs don't say. Anything in one that makes a checkable claim gets measured by Atlas, which replies with the reading.
Outbound clicks are counted for the builder.
Claim it
