Duda SSL provisioning stalls with external DNS.
Clients see the warning. You see a green monitor.
Duda auto-provisions SSL certificates when clients connect custom domains. When those clients manage DNS at an external registrar, the provisioning handshake can fail silently. The site resolves. The certificate stalls. Your uptime monitor reports a clean 200 while browsers warn visitors the connection is not secure.
No credit card for the trial. Cancel any time.
- Check cadence (Agency)
- 5 min
- SSL pre-expiry alert
- 30 days
- Vendors watched
- 11
- Independent DNS resolvers
- 3
Where Duda agencies get caught out
Three failure modes specific to Duda client portfolios.
Uptime monitors check HTTP response codes. The Duda-specific failures — SSL provisioning gaps during external DNS connection, client DNS changes hidden by the white-label layer, and Duda platform incidents — all fail at a layer below HTTP. They generate the client calls that damage agency relationships.
External DNS provisioning gap
Duda SSL stalls when clients use external DNS
Duda's SSL provisioning works cleanly when clients point their domains to Duda's nameservers. When clients manage DNS at Namecheap, GoDaddy, Cloudflare, or another external registrar, the CNAME-based provisioning challenge can fail mid-handshake. The site resolves correctly while the certificate never fully provisions — a gap no standard uptime monitor catches.
White-label DNS opacity
Your white-label dashboard hides client DNS changes
Duda's white-label dashboard is designed to simplify client management — which means DNS change visibility is limited by design. When a client modifies their DNS records without notifying the agency, the first symptom is often a browser warning or a failed SSL renewal rather than a visible DNS change in the platform.
Multi-site platform dependency
Duda platform incidents affect your entire portfolio
White-label Duda agencies are dependent on Duda's infrastructure. A CDN issue, DNS propagation problem, or certificate authority incident at Duda affects every client site under your management simultaneously. Without upstream vendor monitoring, you diagnose each site independently before realizing the root cause is upstream.
How it works
Set up once per client. Watch every site from there.
Merlonix is designed for Duda agencies managing client sites across a mix of Duda-managed and externally-pointed domains — one account, every domain, one alert flow that only fires when something actually needs attention.
01
Add your Duda client domains
Verify ownership with a DNS TXT record — works for Duda-nameserver domains and externally pointed custom domains at any registrar. One verification per domain establishes the monitoring baseline. Takes under two minutes per client, regardless of where their DNS is managed.
02
SSL provisioning checked end-to-end every 5 minutes
Merlonix validates the full certificate chain — not just the expiry date. Issuer authority, chain completeness, domain match, and SAN coverage are all checked. Duda SSL provisioning failures during external DNS connection are detected within one check interval, before any browser surfaces a warning to visitors.
03
DNS changes tracked outside your Duda dashboard
Three independent DNS resolvers verify your expected records on every check interval. When a client changes their external DNS records without telling you, Merlonix detects the change and alerts your team immediately — closing the visibility gap the white-label dashboard creates.
04
Duda platform status in your alert feed
Duda infrastructure incidents appear alongside your client-specific alerts in a separate vendor status feed. When a Duda CDN issue is responsible for multiple client sites loading slowly or showing errors, you see the upstream cause instantly — instead of working through your portfolio one site at a time.
What the numbers mean for Duda agencies
Monitoring that covers the Duda-specific failure surface.
Duda agencies rely on the platform to handle most of the infrastructure complexity — which means failures at the platform or DNS layer are harder to detect without external monitoring. Merlonix sits outside your Duda account and watches what the dashboard can't show you.
30 days
SSL expiry warning lead time — enough runway to fix Duda provisioning issues before any browser shows a warning to visitors
< 10 min
Time from DNS change to alert — catches external DNS record changes that the Duda white-label dashboard does not surface
11 vendors
Upstream services monitored — including Duda platform status and payment providers common in Duda ecommerce client stacks
200 assets
Maximum monitored domains on the Agency plan — enough for a full Duda white-label client portfolio
Pricing
Flat monthly fee. Every client domain included.
No per-domain charges. No per-alert fees. Pick the tier that fits your client count and grow without billing surprises.
Starter
For solo Duda developers watching a handful of client sites.
$29/ month
- 10 monitored assets
- 1 seat
- 15-min check cadence
- SSL + DNS + vendor monitoring
- Email + Slack alerts
Team
For growing Duda agencies with multiple team members.
$79/ month
- 50 monitored assets
- 5 seats
- 10-min check cadence
- SSL + DNS + vendor monitoring
- Email + Slack alerts
Agency
For agencies with a full Duda white-label client portfolio.
$199/ month
- 200 monitored assets
- 15 seats
- 5-min check cadence
- SSL + DNS + vendor monitoring
- Email + Slack alerts
Stop finding out from clients.
Add your first Duda client domain in under two minutes. The first SSL or DNS alert tells you whether monitoring was worth it — usually within the first week. 14-day trial, no card required.