Strikingly custom domain SSL stalls
when client DNS changes after setup.
Strikingly provisions SSL for custom domains using CNAME verification. If a client changes their nameservers or DNS provider after setup — for any unrelated reason — that CNAME stops resolving to Strikingly's CDN. The SSL provisioning breaks silently, and the next renewal fails. Your client's site is the one showing a browser warning.
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 Strikingly agencies get caught out
Three failure modes specific to Strikingly client portfolios.
Strikingly abstracts most of the technical configuration for agencies — but that abstraction also means infrastructure failures are invisible until they reach the browser. External monitoring fills the gap.
CNAME verification gap
SSL provisioning stalls when CNAME is incomplete at activation
Strikingly activates SSL for custom domains by verifying a CNAME record pointing to its CDN. If DNS propagation is incomplete when Strikingly's system checks — which often happens when clients connect domains close to launch — provisioning stalls in a pending state. The custom domain serves without SSL or fails entirely. The agency is left troubleshooting with no visibility into which step failed.
Post-setup DNS drift
Client nameserver changes break the Strikingly CNAME silently
Clients sometimes move their domain to a new DNS provider or registrar after the Strikingly site is live — for email hosting changes, to consolidate domains, or after an IT change. When the CNAME record isn't correctly migrated, the Strikingly CDN loses the domain delegation. The site continues loading from browser cache for days while the underlying DNS is broken.
Platform status opacity
Strikingly platform incidents affect all client sites simultaneously
Strikingly does not maintain a public status page with real-time incident data. When Strikingly's CDN or platform experiences degradation, agencies diagnose each client site independently before realizing the cause is upstream. Without external vendor monitoring, the root cause determination takes significantly longer than necessary.
How it works
Set up once per client. Watch every Strikingly site from there.
Merlonix is designed for agencies managing client portfolios across website builders — one account covering every domain, one alert flow that only fires when something needs attention.
01
Add Strikingly client domains
Verify ownership with a DNS TXT record — works for any custom domain connected to a Strikingly site. One verification per domain establishes the monitoring baseline. Takes under two minutes per client.
02
SSL chain validated every 5 minutes
Merlonix validates the full certificate chain on every check interval — expiry date, issuer, chain completeness, and domain match. SSL provisioning stalls and CNAME drift are detected before the browser shows a warning to your client.
03
CNAME and DNS record changes flagged immediately
Three independent DNS resolvers verify the expected CNAME to Strikingly's CDN on every check interval. When a client's DNS migration breaks the CNAME, the alert fires within minutes — before the site starts returning errors to visitors.
04
Vendor status in your alert feed
Strikingly platform status is monitored alongside your per-client SSL and DNS checks. When a Strikingly infrastructure incident causes multiple client sites to degrade simultaneously, you see the upstream cause in your alert feed rather than discovering it one client call at a time.
What the numbers mean for Strikingly agencies
Monitoring that covers the Strikingly-specific failure surface.
Strikingly agencies typically don't have a dedicated technical team. You're managing sites for clients who treat their Strikingly presence as a utility — and expect it to just work. Merlonix is built around that constraint: minimal setup, maximum signal per alert.
30 days
SSL expiry warning lead time — enough runway to resolve Strikingly CNAME issues before the certificate expires
< 10 min
Time from DNS change to alert — catches CNAME drift on client domains before the Strikingly CDN loses the delegation
11 vendors
Upstream services monitored — including website builder platform status for agencies managing client portfolios
200 assets
Maximum monitored domains on the Agency plan — enough for a full Strikingly client roster
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 consultants watching a handful of Strikingly client sites.
$29/ month
- 10 monitored assets
- 1 seat
- 15-min check cadence
- SSL + DNS + vendor monitoring
- Email + Slack alerts
Team
For growing agencies with multiple Strikingly clients.
$79/ month
- 50 monitored assets
- 5 seats
- 10-min check cadence
- SSL + DNS + vendor monitoring
- Email + Slack alerts
Agency
For agencies with a full Strikingly 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 Strikingly 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.