Eleventy builds ship to four CDN platforms.
Each platform manages its own SSL certificate — independently.
Eleventy agencies deploy client builds to Netlify, Cloudflare Pages, Vercel, and GitHub Pages. Every custom domain requires a CNAME pointing at the platform hostname — and every platform provisions SSL on its own schedule, with its own renewal mechanism. Multilingual Eleventy sites create per-locale subdomains, each with independent SSL. Platform migrations leave stale CNAMEs. Merlonix monitors SSL and DNS so you know before clients find out.
No credit card for the trial. Cancel any time.
- Check cadence (Agency)
- 5 min
- SSL pre-expiry alert
- 30 days
- Independent DNS resolvers
- 3
- Vendors watched
- 11
Where Eleventy agencies get caught out
Three failure modes specific to Eleventy client deployments on Netlify, Cloudflare Pages, and GitHub Pages.
Eleventy agencies deploying to multiple CDN platforms deal with platform migration CNAME residue, per-locale subdomain SSL that expires independently, and headless CMS API subdomains that agencies often discover only after client reports of broken runtime features.
Platform migrations leave stale GitHub Pages CNAMEs active in client DNS
After migrating an Eleventy client site from GitHub Pages to Netlify, the old github.io CNAME entry stays in the client's DNS zone and continues to resolve — until a GitHub account is closed or the old Pages site is removed
Eleventy agencies frequently start client projects on GitHub Pages because of its zero-cost static hosting and simple deployment pipeline. When clients grow and require features like branch previews, form handling, or serverless functions, agencies migrate the build output to Netlify or Cloudflare Pages. The DNS CNAME is updated to point at the new platform, but the old GitHub Pages custom domain configuration — and the GitHub Pages site itself — often remains active. The stale CNAME in the client's DNS zone points at GitHub's infrastructure. After the GitHub repository is eventually made private or the Pages configuration is removed, the old CNAME becomes a dangling record. Depending on client DNS TTL, this causes intermittent resolution failures that are difficult to diagnose without CNAME integrity monitoring that tracks what each record actually points to.
Multilingual Eleventy sites create per-locale subdomains with independent SSL on each
An Eleventy i18n build serving fr.client.com, de.client.com, and es.client.com requires three separate custom domain configurations on the CDN platform — each with its own SSL certificate provisioned and renewed independently
Eleventy's internationalization features allow agencies to build multilingual client sites where each locale is served from a separate subdomain. Netlify, Cloudflare Pages, and Vercel each manage SSL for custom subdomains independently — a certificate renewal that succeeds on the primary domain does not guarantee renewal on the locale subdomains. Locale subdomain SSL certificates can expire weeks or months before or after the primary domain certificate, depending on when each was provisioned and which renewal mechanism the platform uses. Agencies monitoring only the primary client domain miss locale subdomain expiry until a client reports that French-speaking or German-speaking visitors are seeing SSL errors — which takes longer than primary-domain outages to surface because users in that locale are a smaller segment of the client's traffic.
Headless CMS integrations add API subdomains with SSL independent from the Eleventy build
An Eleventy site using Contentful, Sanity, or a self-hosted headless CMS via a custom API subdomain introduces independent SSL that expires on a different schedule from the CDN-hosted static output
Eleventy's data pipeline supports fetching content from headless CMS APIs at build time — and many agencies also run client-side JavaScript that queries the same CMS API at runtime for preview functionality, form submissions, or personalization. When a self-hosted headless CMS or a custom API layer runs on api.clientdomain.com or cms.clientdomain.com, that subdomain has its own SSL certificate provisioned by whatever platform hosts the CMS — not by the CDN platform serving the Eleventy build output. The two certificates expire independently. Agencies that monitor only the CDN-hosted primary domain miss API subdomain SSL expiry until a client reports that preview mode is broken, form submissions are failing, or runtime content fetches are returning SSL errors to end users.
How it works
SSL and DNS monitoring for Eleventy builds on Netlify, Cloudflare Pages, Vercel, and GitHub Pages.
Merlonix monitors CNAME integrity and SSL health for every subdomain your Eleventy clients use — locale subdomains, headless CMS APIs, branch previews, and legacy platform CNAMEs from prior migrations.
01
Add primary domain, locale subdomains, API endpoints, and legacy platform CNAMEs
Verify ownership with a DNS TXT record on the apex domain. Locale subdomains (fr., de., es.), headless CMS API subdomains, staging branch previews, and legacy GitHub Pages CNAMEs from prior migrations are added without additional verification. Monitoring legacy CNAMEs catches GitHub Pages decommission problems before dangling records surface as intermittent failures. Under two minutes per client.
02
CNAME integrity checks on Netlify, Cloudflare Pages, Vercel, and GitHub Pages hostnames
Three independent DNS resolvers check every CNAME delegation on every monitoring interval — whether the target is a Netlify hostname, a Cloudflare Pages workers.dev hostname, a Vercel deployment URL, or a GitHub Pages username.github.io target. When a platform migration leaves a conflicting old CNAME, the target mismatch is detected immediately. When a Vercel redeployment reassigns a custom domain to a new project and the CNAME loses its routing, the break is detected before clients report it.
03
SSL monitoring 30 days before expiry on every subdomain — primary, locale, and API
Full SSL chain validation on the primary domain, every locale subdomain, and every headless CMS or API subdomain. An expiry alert fires 30 days before the certificate expires — enough lead time to ensure the platform renews or to provision a replacement manually. Netlify, Cloudflare Pages, and Vercel each manage certificate renewal independently; Merlonix monitors every certificate regardless of which platform provisions it.
04
Vendor status for Netlify, Cloudflare Pages, Vercel, and GitHub Pages
Merlonix monitors Netlify, Cloudflare, and Vercel platform status alongside client SSL and DNS. When a Netlify CDN incident affects SSL delivery across multiple client builds simultaneously, you see the vendor event — not a cascade of individual client alerts that each require separate investigation to distinguish from a client-specific DNS change.
What the numbers mean for Eleventy agencies
Monitoring built for Eleventy agencies where one client build touches four CDN platforms.
Eleventy agencies managing multilingual client sites and multi-platform deployments need SSL monitoring that covers every subdomain — because per-locale and API subdomain certificates expire on completely independent schedules from the primary domain.
< 10 min
Time from DNS change to alert — catches GitHub Pages CNAME residue and Netlify custom domain routing breaks before clients notice
30 days
SSL expiry warning lead time — enough time for Netlify, Cloudflare Pages, or Vercel to renew, or for the agency to provision a replacement before clients see SSL errors
11 vendors
Upstream services monitored — Netlify, Cloudflare, and Vercel included to distinguish platform incidents from client-specific DNS changes on Eleventy deployments
200 assets
Maximum monitored domains on the Agency plan — covers primary domains, locale subdomains, API endpoints, staging, and legacy CNAMEs across a full Eleventy client roster
Pricing
Flat monthly fee. Every locale subdomain and API endpoint included.
No per-domain charges. No per-platform fees. Pick the tier that fits your Eleventy client count and monitor every subdomain without billing surprises.
Starter
For individual Eleventy developers managing a small static site client portfolio.
$29/ month
- 10 monitored assets
- 1 seat
- 15-min check cadence
- SSL + DNS + vendor monitoring
- Email + Slack alerts
Team
For Eleventy agencies managing multilingual builds and multi-platform client deployments.
$79/ month
- 50 monitored assets
- 5 seats
- 10-min check cadence
- SSL + DNS + vendor monitoring
- Email + Slack alerts
Agency
For agencies with a full Eleventy client roster across Netlify, Cloudflare Pages, Vercel, and GitHub Pages.
$199/ month
- 200 monitored assets
- 15 seats
- 5-min check cadence
- SSL + DNS + vendor monitoring
- Email + Slack alerts
Know when an Eleventy client's locale subdomain or API cert is about to expire.
Add your first Eleventy client domain in under two minutes. Locale subdomains, headless CMS API endpoints, branch previews, and legacy platform CNAMEs are monitored from the same dashboard. 14-day trial, no card required.