{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Blog",
      "@id": "https://approximated.app/blog/#blog",
      "url": "https://approximated.app/blog/",
      "name": "Approximated Blog",
      "inLanguage": "en",
      "blogPost": [
        {
          "@id": "https://approximated.app/blog/https-custom-tracking-domains-for-email-platforms/#article"
        },
        {
          "@id": "https://approximated.app/blog/caddy-on-demand-tls-vs-managed-custom-domains/#article"
        },
        {
          "@id": "https://approximated.app/blog/lets-encrypt-rate-limits-custom-domains/#article"
        },
        {
          "@id": "https://approximated.app/blog/custom-domain-security/#article"
        },
        {
          "@id": "https://approximated.app/blog/custom-domain-onboarding-checklist/#article"
        },
        {
          "@id": "https://approximated.app/blog/apex-domains-for-saas/#article"
        },
        {
          "@id": "https://approximated.app/blog/best-custom-domain-apis-for-saas/#article"
        },
        {
          "@id": "https://approximated.app/blog/custom-domains-for-saas-guide/#article"
        }
      ]
    },
    {
      "@type": "BlogPosting",
      "@id": "https://approximated.app/blog/https-custom-tracking-domains-for-email-platforms/#article",
      "url": "https://approximated.app/blog/https-custom-tracking-domains-for-email-platforms/",
      "headline": "HTTPS custom tracking domains for email platforms",
      "description": "Give customers branded click and open tracking domains over HTTPS without asking them to set up Cloudflare. How it works, why it matters, and your options.",
      "abstract": "a custom tracking domain is a customer subdomain, such as track.customer.example, that points at your click and open tracker with a CNAME. To serve those links over HTTPS, something on your side has to hold a valid certificate for that exact hostname. You don't need every customer to set up Cloudflare or another CDN to get one. Verify the customer's CNAME, then either issue the certificate yourself on proxies that use on-demand TLS, or route the hostname through a managed custom-domain proxy that issues and renews it for you.",
      "datePublished": "2026-11-02",
      "dateModified": "2026-11-02",
      "inLanguage": "en",
      "articleSection": "Email",
      "author": {
        "@type": "Organization",
        "@id": "https://approximated.app/#organization",
        "name": "Approximated",
        "url": "https://approximated.app/"
      },
      "publisher": {
        "@type": "Organization",
        "@id": "https://approximated.app/#organization",
        "name": "Approximated",
        "url": "https://approximated.app/"
      },
      "mainEntityOfPage": {
        "@type": "WebPage",
        "@id": "https://approximated.app/blog/https-custom-tracking-domains-for-email-platforms/"
      },
      "isPartOf": {
        "@id": "https://approximated.app/blog/#blog"
      },
      "isAccessibleForFree": true,
      "wordCount": 2423,
      "keywords": [
        "Custom tracking domain SSL",
        "HTTPS click tracking",
        "Email platform custom domains",
        "Branded tracking links",
        "Open tracking domains"
      ],
      "about": [
        {
          "@type": "DefinedTerm",
          "name": "Custom tracking domain SSL"
        },
        {
          "@type": "DefinedTerm",
          "name": "HTTPS click tracking"
        },
        {
          "@type": "DefinedTerm",
          "name": "Email platform custom domains"
        },
        {
          "@type": "DefinedTerm",
          "name": "Branded tracking links"
        },
        {
          "@type": "DefinedTerm",
          "name": "Open tracking domains"
        }
      ],
      "citation": [
        "https://docs.aws.amazon.com/ses/latest/dg/configure-custom-open-click-domains.html",
        "https://postmarkapp.com/developer/user-guide/tracking-links",
        "https://postmarkapp.com/blog/how-we-built-link-tracking-to-be-reliable-fast-and-secure",
        "https://postmarkapp.com/migration-guides/sparkpost",
        "https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Strict-Transport-Security",
        "https://www.registry.google/domains/app/",
        "https://buttondown.com/blog/support-for-https-tracking-links",
        "https://aws.amazon.com/about-aws/whats-new/2024/09/amazon-ses-https-tracking-custom-domains",
        "https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content",
        "https://www.twilio.com/docs/sendgrid/ui/sending-email/content-delivery-networks/using-cloudflare-as-your-content-delivery-network-cdn",
        "https://caddyserver.com/docs/automatic-https",
        "https://caddyserver.com/docs/caddyfile/options",
        "https://caddy.community/t/serving-tens-of-thousands-of-domains-over-https-with-caddy/11179",
        "https://caddy.community/t/caddy-with-on-demand-tls-total-outage-after-an-unattended-restart-when-ask-endpoint-is-down/33898",
        "https://letsencrypt.org/docs/rate-limits/",
        "https://letsencrypt.org/2026/10/07/64-day-certs",
        "https://letsencrypt.org/2025/12/02/from-90-to-45",
        "https://approximated.app/blog/best-custom-domain-apis-for-saas/",
        "https://approximated.app/blog/custom-domain-onboarding-checklist/",
        "https://approximated.app/blog/apex-domains-for-saas/",
        "https://letsencrypt.org/2025/01/22/ending-expiration-emails",
        "https://approximated.app/blog/custom-domain-security/#faq-dangling-dns",
        "https://approximated.app/for/outbound-email-platforms/",
        "https://approximated.app/docs/#virtual-hosts-api",
        "https://approximated.app/docs/#what-is-a-proxy-cluster",
        "https://approximated.app/docs/#virtual-host-statuses",
        "https://approximated.app/docs/#webhooks",
        "https://approximated.app/#waf",
        "https://approximated.app/#faq",
        "https://approximated.app/pricing/",
        "https://approximated.app/self-hosted/"
      ],
      "hasPart": [
        {
          "@id": "https://approximated.app/blog/https-custom-tracking-domains-for-email-platforms/#faq"
        }
      ],
      "encoding": {
        "@type": "MediaObject",
        "encodingFormat": "text/markdown",
        "contentUrl": "https://approximated.app/blog/https-custom-tracking-domains-for-email-platforms/index.md"
      }
    },
    {
      "@type": "FAQPage",
      "@id": "https://approximated.app/blog/https-custom-tracking-domains-for-email-platforms/#faq",
      "url": "https://approximated.app/blog/https-custom-tracking-domains-for-email-platforms/#faq",
      "name": "HTTPS custom tracking domains for email platforms: frequently asked questions",
      "inLanguage": "en",
      "isPartOf": {
        "@id": "https://approximated.app/blog/https-custom-tracking-domains-for-email-platforms/#article"
      },
      "mainEntity": [
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/https-custom-tracking-domains-for-email-platforms/#faq-tracking-domain-ssl",
          "url": "https://approximated.app/blog/https-custom-tracking-domains-for-email-platforms/#faq-tracking-domain-ssl",
          "name": "Why doesn't my tracking certificate cover customer tracking domains?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/https-custom-tracking-domains-for-email-platforms/#faq-tracking-domain-ssl-answer",
            "text": "A certificate is valid only for the hostnames listed in it. When a reader opens https://track.customer.example, the browser checks for a certificate covering that exact name before any request is sent. A certificate for your own tracking hostname doesn't qualify, even though the customer's CNAME points at it. Each branded tracking domain needs its own certificate."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/https-custom-tracking-domains-for-email-platforms/#faq-without-cloudflare",
          "url": "https://approximated.app/blog/https-custom-tracking-domains-for-email-platforms/#faq-without-cloudflare",
          "name": "How can I get SSL on a custom tracking domain without making customers set up Cloudflare?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/https-custom-tracking-domains-for-email-platforms/#faq-without-cloudflare-answer",
            "text": "Hold the certificate on your side. Ask the customer for one CNAME to a hostname you control, verify it, and then issue a certificate for their tracking hostname on your own proxies with on-demand TLS, or register it with a managed custom-domain proxy that issues and renews it. The customer keeps their DNS provider and never configures a CDN."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/https-custom-tracking-domains-for-email-platforms/#faq-https-deliverability",
          "url": "https://approximated.app/blog/https-custom-tracking-domains-for-email-platforms/#faq-https-deliverability",
          "name": "Do HTTPS tracking links improve email deliverability?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/https-custom-tracking-domains-for-email-platforms/#faq-https-deliverability-answer",
            "text": "AWS says HTTPS tracking reduces the chances of delivery issues with mailbox providers that reject non-secure links. We haven't found a primary source that measures the effect on inbox placement. The firmer reasons are in the browser. On HSTS hosts such as every .app domain, HTTP-only tracking links fail, and readers may see warnings on mixed HTTP and HTTPS links."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/https-custom-tracking-domains-for-email-platforms/#faq-apex-tracking",
          "url": "https://approximated.app/blog/https-custom-tracking-domains-for-email-platforms/#faq-apex-tracking",
          "name": "Can a customer use their root domain as a tracking domain?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/https-custom-tracking-domains-for-email-platforms/#faq-apex-tracking-answer",
            "text": "Use a dedicated subdomain such as track.customer.example instead. A CNAME can't sit at the root of a DNS zone, and pointing the root at your tracker would also take over the customer's website. A subdomain keeps tracking traffic separate and lets the customer use an ordinary CNAME record at their existing DNS provider."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/https-custom-tracking-domains-for-email-platforms/#faq-cname-removed",
          "url": "https://approximated.app/blog/https-custom-tracking-domains-for-email-platforms/#faq-cname-removed",
          "name": "What happens when a customer removes their tracking domain CNAME?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/https-custom-tracking-domains-for-email-platforms/#faq-cname-removed-answer",
            "text": "Requests to that hostname stop reaching your tracker, so tracked links in emails already sent stop working and certificate renewals for the name start failing validation. Detect the DNS change, warn the customer about links in sent mail, and remove the hostname from your proxy so it stops retrying issuance that can't succeed."
          }
        }
      ]
    },
    {
      "@type": "BlogPosting",
      "@id": "https://approximated.app/blog/caddy-on-demand-tls-vs-managed-custom-domains/#article",
      "url": "https://approximated.app/blog/caddy-on-demand-tls-vs-managed-custom-domains/",
      "headline": "Caddy on-demand TLS vs a managed service for customer domains",
      "description": "How Caddy on-demand TLS issues certificates for customer domains, what production adds on top, and when DIY Caddy or a managed service is simpler.",
      "abstract": "Caddy's on-demand TLS is a good, production-capable way to give customer custom domains automatic HTTPS. It gets a certificate during the first TLS handshake for a hostname your ask endpoint approves. The certificate is only part of the job. You also run the permission endpoint, shared certificate storage, CA rate-limit budgets, monitoring, abuse handling and routing. If your team wants to own that edge, Caddy is an excellent base. If it doesn't, a managed custom domain service moves that work off your plate.",
      "datePublished": "2026-10-26",
      "dateModified": "2026-10-26",
      "inLanguage": "en",
      "articleSection": "TLS",
      "author": {
        "@type": "Organization",
        "@id": "https://approximated.app/#organization",
        "name": "Approximated",
        "url": "https://approximated.app/"
      },
      "publisher": {
        "@type": "Organization",
        "@id": "https://approximated.app/#organization",
        "name": "Approximated",
        "url": "https://approximated.app/"
      },
      "mainEntityOfPage": {
        "@type": "WebPage",
        "@id": "https://approximated.app/blog/caddy-on-demand-tls-vs-managed-custom-domains/"
      },
      "isPartOf": {
        "@id": "https://approximated.app/blog/#blog"
      },
      "isAccessibleForFree": true,
      "wordCount": 2399,
      "keywords": [
        "Caddy on-demand TLS",
        "Caddy ask endpoint",
        "Custom domain SSL",
        "Managed custom domain service",
        "Self-hosted TLS proxy"
      ],
      "about": [
        {
          "@type": "DefinedTerm",
          "name": "Caddy on-demand TLS"
        },
        {
          "@type": "DefinedTerm",
          "name": "Caddy ask endpoint"
        },
        {
          "@type": "DefinedTerm",
          "name": "Custom domain SSL"
        },
        {
          "@type": "DefinedTerm",
          "name": "Managed custom domain service"
        },
        {
          "@type": "DefinedTerm",
          "name": "Self-hosted TLS proxy"
        }
      ],
      "citation": [
        "https://caddyserver.com/docs/automatic-https",
        "https://caddyserver.com/docs/caddyfile/options",
        "https://github.com/caddyserver/caddy/blob/v2.11.4/modules/caddytls/ondemand.go",
        "https://caddy.community/t/serving-tens-of-thousands-of-domains-over-https-with-caddy/11179",
        "https://caddy.community/t/caddy-with-on-demand-tls-total-outage-after-an-unattended-restart-when-ask-endpoint-is-down/33898",
        "https://letsencrypt.org/docs/integration-guide/",
        "https://zerossl.com/documentation/acme/",
        "https://letsencrypt.org/docs/rate-limits/",
        "https://letsencrypt.org/2026/10/07/64-day-certs",
        "https://letsencrypt.org/2025/01/22/ending-expiration-emails",
        "https://approximated.app/blog/custom-domain-onboarding-checklist/",
        "https://approximated.app/blog/custom-domain-security/",
        "https://approximated.app/blog/apex-domains-for-saas/",
        "https://approximated.app/approximated-diy-comparison/",
        "https://approximated.app/docs/#webhooks",
        "https://approximated.app/#waf",
        "https://approximated.app/self-hosted/",
        "https://approximated.app/pricing/"
      ],
      "hasPart": [
        {
          "@id": "https://approximated.app/blog/caddy-on-demand-tls-vs-managed-custom-domains/#faq"
        }
      ],
      "encoding": {
        "@type": "MediaObject",
        "encodingFormat": "text/markdown",
        "contentUrl": "https://approximated.app/blog/caddy-on-demand-tls-vs-managed-custom-domains/index.md"
      }
    },
    {
      "@type": "FAQPage",
      "@id": "https://approximated.app/blog/caddy-on-demand-tls-vs-managed-custom-domains/#faq",
      "url": "https://approximated.app/blog/caddy-on-demand-tls-vs-managed-custom-domains/#faq",
      "name": "Caddy on-demand TLS vs a managed service for customer domains: frequently asked questions",
      "inLanguage": "en",
      "isPartOf": {
        "@id": "https://approximated.app/blog/caddy-on-demand-tls-vs-managed-custom-domains/#article"
      },
      "mainEntity": [
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/caddy-on-demand-tls-vs-managed-custom-domains/#faq-production-ready",
          "url": "https://approximated.app/blog/caddy-on-demand-tls-vs-managed-custom-domains/#faq-production-ready",
          "name": "Is Caddy on-demand TLS good enough for production custom domains?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/caddy-on-demand-tls-vs-managed-custom-domains/#faq-production-ready-answer",
            "text": "Yes, when you run it carefully. Caddy handles ACME, storage, renewal, retries and CA fallback well. Production use also needs a fast and highly available permission endpoint, durable shared storage for more than one instance, attention to CA rate limits, certificate monitoring, and abuse protection. Those parts decide whether it is good enough for you."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/caddy-on-demand-tls-vs-managed-custom-domains/#faq-multi-tenant",
          "url": "https://approximated.app/blog/caddy-on-demand-tls-vs-managed-custom-domains/#faq-multi-tenant",
          "name": "How do I use Caddy on-demand TLS for a multi-tenant SaaS?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/caddy-on-demand-tls-vs-managed-custom-domains/#faq-multi-tenant-answer",
            "text": "Enable on_demand inside a catch-all HTTPS site, point the global on_demand_tls ask setting at an internal endpoint, and have that endpoint return 200 only for hostnames that belong to an active tenant. Proxy requests to your app, and let the app pick the tenant from the trusted Host header. Add shared storage before you run a second Caddy instance."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/caddy-on-demand-tls-vs-managed-custom-domains/#faq-ask-check",
          "url": "https://approximated.app/blog/caddy-on-demand-tls-vs-managed-custom-domains/#faq-ask-check",
          "name": "What should a Caddy ask endpoint check?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/caddy-on-demand-tls-vs-managed-custom-domains/#faq-ask-check-answer",
            "text": "It should check whether the exact, normalized hostname belongs to an active customer, and nothing slower. Caddy recommends answering in a few milliseconds and avoiding DNS queries or other network calls. Read from a local table or cache, keep the endpoint off the public internet, and return a non-2xx status for anything unknown."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/caddy-on-demand-tls-vs-managed-custom-domains/#faq-ask-down",
          "url": "https://approximated.app/blog/caddy-on-demand-tls-vs-managed-custom-domains/#faq-ask-down",
          "name": "What happens to existing certificates if the ask endpoint goes down?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/caddy-on-demand-tls-vs-managed-custom-domains/#faq-ask-down-answer",
            "text": "In current Caddy, the permission check also controls loading certificates from storage, not only issuing new ones. A forum user reported a full TLS outage after a restart while their endpoint was down, and Caddy's author confirmed that behavior is intended. Run the endpoint locally and keep it as reliable as the proxy itself."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/caddy-on-demand-tls-vs-managed-custom-domains/#faq-managed",
          "url": "https://approximated.app/blog/caddy-on-demand-tls-vs-managed-custom-domains/#faq-managed",
          "name": "When should I pay for a managed custom domain service instead of running Caddy?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/caddy-on-demand-tls-vs-managed-custom-domains/#faq-managed-answer",
            "text": "Pay for a service when the work around certificates costs more than the bill. That usually means you need several regions, stable apex IP addresses, WAF and DDoS protection, domain status APIs and webhooks, or on-call coverage you don't want to staff. If your team already runs that kind of infrastructure, DIY Caddy can be the better fit."
          }
        }
      ]
    },
    {
      "@type": "BlogPosting",
      "@id": "https://approximated.app/blog/lets-encrypt-rate-limits-custom-domains/#article",
      "url": "https://approximated.app/blog/lets-encrypt-rate-limits-custom-domains/",
      "headline": "Let's Encrypt rate limits for SaaS custom domains",
      "description": "Which Let's Encrypt rate limits hit SaaS platforms issuing certificates for customer domains, how DIY setups trip them, and how to stay under them.",
      "abstract": "Let's Encrypt can issue certificates for thousands of customer domains, and most of its rate limits never come into play. Three usually do. New Orders per Account caps a burst of new domains at 300 orders every three hours. Authorization Failures caps retries on a hostname with broken DNS at 5 per hour, and a hostname that keeps failing for weeks gets paused. New Certificates per Registered Domain caps you at 50 a week when many tenants share one parent domain. Issue only for hostnames a tenant has claimed, back off hard when validation fails, renew with ARI, and request an override before launch day.",
      "datePublished": "2026-10-19",
      "dateModified": "2026-10-19",
      "inLanguage": "en",
      "articleSection": "SSL",
      "author": {
        "@type": "Organization",
        "@id": "https://approximated.app/#organization",
        "name": "Approximated",
        "url": "https://approximated.app/"
      },
      "publisher": {
        "@type": "Organization",
        "@id": "https://approximated.app/#organization",
        "name": "Approximated",
        "url": "https://approximated.app/"
      },
      "mainEntityOfPage": {
        "@type": "WebPage",
        "@id": "https://approximated.app/blog/lets-encrypt-rate-limits-custom-domains/"
      },
      "isPartOf": {
        "@id": "https://approximated.app/blog/#blog"
      },
      "isAccessibleForFree": true,
      "wordCount": 2150,
      "keywords": [
        "Let's Encrypt rate limits",
        "SSL for customer domains",
        "Certificate issuance at scale",
        "ACME failed validations",
        "Certificate renewals"
      ],
      "about": [
        {
          "@type": "DefinedTerm",
          "name": "Let's Encrypt rate limits"
        },
        {
          "@type": "DefinedTerm",
          "name": "SSL for customer domains"
        },
        {
          "@type": "DefinedTerm",
          "name": "Certificate issuance at scale"
        },
        {
          "@type": "DefinedTerm",
          "name": "ACME failed validations"
        },
        {
          "@type": "DefinedTerm",
          "name": "Certificate renewals"
        }
      ],
      "citation": [
        "https://letsencrypt.org/docs/rate-limits/",
        "https://letsencrypt.org/2026/02/24/rate-limits-45-day-certs",
        "https://letsencrypt.org/docs/integration-guide/",
        "https://letsencrypt.org/2025/12/02/from-90-to-45",
        "https://letsencrypt.org/2026/10/07/64-day-certs",
        "https://caddyserver.com/docs/automatic-https",
        "https://caddyserver.com/docs/caddyfile/options",
        "https://isrg.formstack.com/forms/rate_limit_adjustment_request",
        "https://letsencrypt.org/2025/01/22/ending-expiration-emails",
        "https://zerossl.com/documentation/acme/",
        "https://approximated.app/blog/custom-domains-for-saas-guide/#tls",
        "https://approximated.app/blog/custom-domain-onboarding-checklist/#faq-dns-before-ssl",
        "https://approximated.app/approximated-diy-comparison/",
        "https://approximated.app/docs/#virtual-host-statuses",
        "https://approximated.app/docs/#webhooks",
        "https://approximated.app/pricing/"
      ],
      "hasPart": [
        {
          "@id": "https://approximated.app/blog/lets-encrypt-rate-limits-custom-domains/#faq"
        }
      ],
      "encoding": {
        "@type": "MediaObject",
        "encodingFormat": "text/markdown",
        "contentUrl": "https://approximated.app/blog/lets-encrypt-rate-limits-custom-domains/index.md"
      }
    },
    {
      "@type": "FAQPage",
      "@id": "https://approximated.app/blog/lets-encrypt-rate-limits-custom-domains/#faq",
      "url": "https://approximated.app/blog/lets-encrypt-rate-limits-custom-domains/#faq",
      "name": "Let's Encrypt rate limits for SaaS custom domains: frequently asked questions",
      "inLanguage": "en",
      "isPartOf": {
        "@id": "https://approximated.app/blog/lets-encrypt-rate-limits-custom-domains/#article"
      },
      "mainEntity": [
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/lets-encrypt-rate-limits-custom-domains/#faq-how-many",
          "url": "https://approximated.app/blog/lets-encrypt-rate-limits-custom-domains/#faq-how-many",
          "name": "How many new certificates can a SaaS get from Let's Encrypt per day?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/lets-encrypt-rate-limits-custom-domains/#faq-how-many-answer",
            "text": "As of October 2026, one ACME account can place 300 new orders in a burst, refilling one every 36 seconds. That is about 100 an hour or 2,400 a day sustained, by our arithmetic from the published refill rate. Hostnames under one registered domain are separately capped at 50 new certificates a week. Let's Encrypt accepts override requests for both limits."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/lets-encrypt-rate-limits-custom-domains/#faq-renewals",
          "url": "https://approximated.app/blog/lets-encrypt-rate-limits-custom-domains/#faq-renewals",
          "name": "Do Let's Encrypt renewals count against rate limits?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/lets-encrypt-rate-limits-custom-domains/#faq-renewals-answer",
            "text": "Renewals made through ACME Renewal Information (ARI) are exempt from all Let's Encrypt rate limits. Renewals without ARI for the exact same hostnames are exempt from the new-orders and registered-domain limits, but still count against authorization failures and the exact-set limit. Shorter certificate lifetimes from February 2027 increase renewal volume, and Let's Encrypt says the limits won't change."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/lets-encrypt-rate-limits-custom-domains/#faq-failed-validation",
          "url": "https://approximated.app/blog/lets-encrypt-rate-limits-custom-domains/#faq-failed-validation",
          "name": "What happens when a customer's DNS is wrong and validation keeps failing?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/lets-encrypt-rate-limits-custom-domains/#faq-failed-validation-answer",
            "text": "Each account can fail validation for one hostname 5 times an hour before new orders for it are blocked. After 1,152 consecutive failures, refilling one per day, Let's Encrypt pauses issuance for that hostname until you unpause it through the self-service portal linked in the error. Check DNS before ordering and back off to once a day."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/lets-encrypt-rate-limits-custom-domains/#faq-multiple-accounts",
          "url": "https://approximated.app/blog/lets-encrypt-rate-limits-custom-domains/#faq-multiple-accounts",
          "name": "Should I use multiple ACME accounts to avoid Let's Encrypt rate limits?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/lets-encrypt-rate-limits-custom-domains/#faq-multiple-accounts-answer",
            "text": "Usually not. Extra accounts raise the per-account order limit but not the registered-domain limit, which counts across all accounts. Let's Encrypt's integration guide recommends a single account for large hosting providers, because it can't adjust limits effectively across many accounts. Use one account, request an override, and add a second CA as a fallback."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/lets-encrypt-rate-limits-custom-domains/#faq-reset",
          "url": "https://approximated.app/blog/lets-encrypt-rate-limits-custom-domains/#faq-reset",
          "name": "Can Let's Encrypt reset a rate limit I've already hit?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/lets-encrypt-rate-limits-custom-domains/#faq-reset-answer",
            "text": "No. Let's Encrypt says it has no way to temporarily reset a limit, and revoking certificates doesn't reset one. Limits refill gradually, so capacity returns over hours or days. The override form raises the new-orders and registered-domain limits for the future, but processing takes a few weeks, so file it before a large launch."
          }
        }
      ]
    },
    {
      "@type": "BlogPosting",
      "@id": "https://approximated.app/blog/custom-domain-security/#article",
      "url": "https://approximated.app/blog/custom-domain-security/",
      "headline": "Custom domain security for multi-tenant SaaS",
      "description": "Secure SaaS custom domains with safe tenant claims, WAF and DDoS protection, Edge Verify, monitoring, and verified hostname reassignment.",
      "abstract": "secure custom domains at three boundaries: who may bind a hostname, which tenant a request may reach, and what happens when the binding is removed. Managed TLS protects the connection, but it doesn't decide whether the right customer owns a name or whether your application selected the right tenant.",
      "datePublished": "2026-09-23",
      "dateModified": "2026-09-28",
      "inLanguage": "en",
      "articleSection": "Security",
      "author": {
        "@type": "Organization",
        "@id": "https://approximated.app/#organization",
        "name": "Approximated",
        "url": "https://approximated.app/"
      },
      "publisher": {
        "@type": "Organization",
        "@id": "https://approximated.app/#organization",
        "name": "Approximated",
        "url": "https://approximated.app/"
      },
      "mainEntityOfPage": {
        "@type": "WebPage",
        "@id": "https://approximated.app/blog/custom-domain-security/"
      },
      "isPartOf": {
        "@id": "https://approximated.app/blog/#blog"
      },
      "isAccessibleForFree": true,
      "wordCount": 1262,
      "keywords": [
        "Custom domain security",
        "Multi-tenant SaaS",
        "WAF and DDoS protection",
        "Edge Verify"
      ],
      "about": [
        {
          "@type": "DefinedTerm",
          "name": "Custom domain security"
        },
        {
          "@type": "DefinedTerm",
          "name": "Multi-tenant SaaS"
        },
        {
          "@type": "DefinedTerm",
          "name": "WAF and DDoS protection"
        },
        {
          "@type": "DefinedTerm",
          "name": "Edge Verify"
        }
      ],
      "citation": [
        "https://approximated.app/docs/#virtual-hosts-api",
        "https://approximated.app/blog/custom-domain-onboarding-checklist/",
        "https://approximated.app/guides/",
        "https://cheatsheetseries.owasp.org/cheatsheets/Subdomain_Takeover_Prevention_Cheat_Sheet.html",
        "https://approximated.app/#waf",
        "https://approximated.app/docs/#edge-verify",
        "https://approximated.app/docs/#webhooks",
        "https://approximated.app/#faq",
        "https://approximated.app/self-hosted/",
        "https://approximated.app/pricing/",
        "https://approximated.app/product/",
        "https://approximated.app/docs/",
        "https://approximated.app/blog/best-custom-domain-apis-for-saas/"
      ],
      "hasPart": [
        {
          "@id": "https://approximated.app/blog/custom-domain-security/#faq"
        }
      ],
      "encoding": {
        "@type": "MediaObject",
        "encodingFormat": "text/markdown",
        "contentUrl": "https://approximated.app/blog/custom-domain-security/index.md"
      }
    },
    {
      "@type": "FAQPage",
      "@id": "https://approximated.app/blog/custom-domain-security/#faq",
      "url": "https://approximated.app/blog/custom-domain-security/#faq",
      "name": "Custom domain security for multi-tenant SaaS: frequently asked questions",
      "inLanguage": "en",
      "isPartOf": {
        "@id": "https://approximated.app/blog/custom-domain-security/#article"
      },
      "mainEntity": [
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/custom-domain-security/#faq-https-ownership",
          "url": "https://approximated.app/blog/custom-domain-security/#faq-https-ownership",
          "name": "Does automatic HTTPS prevent custom domain takeover in a multi-tenant SaaS?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/custom-domain-security/#faq-https-ownership-answer",
            "text": "HTTPS encrypts a connection to a hostname; it doesn't decide which tenant is allowed to use that hostname. Your application must authorize domain changes, enforce one active tenant claim per normalized hostname, and reject unknown hosts. We handle certificates and edge protection, while tenant identity, hostname ownership, and application authorization remain your controls."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/custom-domain-security/#faq-dangling-dns",
          "url": "https://approximated.app/blog/custom-domain-security/#faq-dangling-dns",
          "name": "How do I prevent a disconnected custom domain from being claimed by another tenant?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/custom-domain-security/#faq-dangling-dns-answer",
            "text": "Stop serving the old tenant but retain a non-routing hostname reservation while DNS can still point at your shared edge. Require fresh proof bound to the exact hostname and requesting account before reassignment. A stale A or CNAME record isn't sufficient proof for a different tenant. Tell the former customer to remove obsolete DNS and make transfer an explicit audited action."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/custom-domain-security/#faq-control-layers",
          "url": "https://approximated.app/blog/custom-domain-security/#faq-control-layers",
          "name": "What security controls should a SaaS custom domain feature include?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/custom-domain-security/#faq-control-layers-answer",
            "text": "Use authorized hostname claims, exact tenant mappings, trusted proxy headers, unknown-host rejection, and safe transfer and removal. Add edge request inspection, traffic-abuse controls, form protection, and ongoing domain monitoring. Our dedicated cloud clusters combine WAF and DDoS protection, Edge Verify, and operational signals for many customer domains; your app continues to enforce login, sessions, and tenant access."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/custom-domain-security/#faq-multi-tenant-waf",
          "url": "https://approximated.app/blog/custom-domain-security/#faq-multi-tenant-waf",
          "name": "How does Approximated protect traffic across many tenant domains?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/custom-domain-security/#faq-multi-tenant-waf-answer",
            "text": "Our WAF and DDoS protection operates in the dedicated cluster serving your SaaS domains. It combines request inspection, client fingerprints, and traffic analysis, using shared threat intelligence alongside evidence from your own traffic. It can challenge suspicious clients and restrict qualifying attacks before they reach your origin. Monitor the outcome for legitimate customer flows as you introduce protection rules."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/custom-domain-security/#faq-edge-verify-forms",
          "url": "https://approximated.app/blog/custom-domain-security/#faq-edge-verify-forms",
          "name": "How does Edge Verify protect forms on customer-owned domains?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/custom-domain-security/#faq-edge-verify-forms-answer",
            "text": "Edge Verify serves its browser script from the customer's own domain and checks form submissions at the edge. Verification tokens are short-lived, single-use, and bound to the domain and visitor. Monitor mode records outcomes without blocking; enforce mode rejects missing or invalid verification. It complements our WAF and DDoS protection while your application still owns identity, authorization, and domain claims."
          }
        }
      ]
    },
    {
      "@type": "BlogPosting",
      "@id": "https://approximated.app/blog/custom-domain-onboarding-checklist/#article",
      "url": "https://approximated.app/blog/custom-domain-onboarding-checklist/",
      "headline": "A custom domain onboarding checklist customers can follow",
      "description": "Design a custom-domain setup flow around five checks: tenant claim, edge configuration, DNS, certificate, and a real application request.",
      "abstract": "make custom-domain onboarding a sequence of five evidence checks: the right tenant claimed the hostname, the edge configuration exists, DNS points where expected, HTTPS is ready, and a real request reaches the right application. These are application UI states, not names of a particular provider's API statuses. Keeping them separate gives customers a useful next action instead of a generic “pending” badge. We built our DNS onboarding, monitoring, and webhooks to help you ship that clarity inside your own product.",
      "datePublished": "2026-09-04",
      "dateModified": "2026-09-28",
      "inLanguage": "en",
      "articleSection": "Product design",
      "author": {
        "@type": "Organization",
        "@id": "https://approximated.app/#organization",
        "name": "Approximated",
        "url": "https://approximated.app/"
      },
      "publisher": {
        "@type": "Organization",
        "@id": "https://approximated.app/#organization",
        "name": "Approximated",
        "url": "https://approximated.app/"
      },
      "mainEntityOfPage": {
        "@type": "WebPage",
        "@id": "https://approximated.app/blog/custom-domain-onboarding-checklist/"
      },
      "isPartOf": {
        "@id": "https://approximated.app/blog/#blog"
      },
      "isAccessibleForFree": true,
      "wordCount": 1145,
      "keywords": [
        "Custom domain onboarding",
        "DNS verification",
        "TLS readiness",
        "Domain monitoring"
      ],
      "about": [
        {
          "@type": "DefinedTerm",
          "name": "Custom domain onboarding"
        },
        {
          "@type": "DefinedTerm",
          "name": "DNS verification"
        },
        {
          "@type": "DefinedTerm",
          "name": "TLS readiness"
        },
        {
          "@type": "DefinedTerm",
          "name": "Domain monitoring"
        }
      ],
      "citation": [
        "https://approximated.app/docs/#virtual-hosts-api",
        "https://approximated.app/blog/apex-domains-for-saas/",
        "https://approximated.app/dns-widget/",
        "https://approximated.app/docs/#dns-widget-headless",
        "https://approximated.app/docs/#webhook-events-virtual-host-monitor-updated",
        "https://approximated.app/docs/#webhook-events-virtual-host-created",
        "https://approximated.app/#waf",
        "https://approximated.app/docs/#edge-verify",
        "https://approximated.app/blog/custom-domain-security/",
        "https://approximated.app/blog/custom-domains-for-saas-guide/",
        "https://approximated.app/docs/",
        "https://approximated.app/#faq",
        "https://approximated.app/pricing/",
        "https://approximated.app/self-hosted/"
      ],
      "hasPart": [
        {
          "@id": "https://approximated.app/blog/custom-domain-onboarding-checklist/#faq"
        }
      ],
      "encoding": {
        "@type": "MediaObject",
        "encodingFormat": "text/markdown",
        "contentUrl": "https://approximated.app/blog/custom-domain-onboarding-checklist/index.md"
      }
    },
    {
      "@type": "FAQPage",
      "@id": "https://approximated.app/blog/custom-domain-onboarding-checklist/#faq",
      "url": "https://approximated.app/blog/custom-domain-onboarding-checklist/#faq",
      "name": "A custom domain onboarding checklist customers can follow: frequently asked questions",
      "inLanguage": "en",
      "isPartOf": {
        "@id": "https://approximated.app/blog/custom-domain-onboarding-checklist/#article"
      },
      "mainEntity": [
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/custom-domain-onboarding-checklist/#faq-connected-state",
          "url": "https://approximated.app/blog/custom-domain-onboarding-checklist/#faq-connected-state",
          "name": "When should my SaaS show that a custom domain is connected?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/custom-domain-onboarding-checklist/#faq-connected-state-answer",
            "text": "Show connected only after the authorized tenant claim is recorded, the edge is configured, DNS points correctly, a valid certificate is active, and a real HTTPS request reaches the intended tenant. Keep saved, DNS, and certificate progress separate. Our monitoring and webhooks provide edge observations, while your application verifies the final customer experience."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/custom-domain-onboarding-checklist/#faq-dns-time",
          "url": "https://approximated.app/blog/custom-domain-onboarding-checklist/#faq-dns-time",
          "name": "How long does a customer DNS change take to become visible?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/custom-domain-onboarding-checklist/#faq-dns-time-answer",
            "text": "There is no single reliable time for every DNS change. The provider must publish the record, and recursive resolvers can retain the previous answer until its cache expires. Check the authoritative answer and public resolvers, show the record actually observed, and offer a check-again action. Treat certificate readiness as a separate step after DNS rather than promising an immediate connection."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/custom-domain-onboarding-checklist/#faq-in-product-dns",
          "url": "https://approximated.app/blog/custom-domain-onboarding-checklist/#faq-in-product-dns",
          "name": "Can customers follow DNS setup inside my SaaS product?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/custom-domain-onboarding-checklist/#faq-in-product-dns-answer",
            "text": "Yes. Our DNS widget presents provider-specific instructions and verifies requested records inside your product. Headless mode lets your own UI use those instructions and checks. The customer still makes the required change at their DNS provider; your application controls who may claim the hostname and confirms the final HTTPS route to the tenant."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/custom-domain-onboarding-checklist/#faq-polling-webhooks",
          "url": "https://approximated.app/blog/custom-domain-onboarding-checklist/#faq-polling-webhooks",
          "name": "Should I use polling or webhooks for custom domain status?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/custom-domain-onboarding-checklist/#faq-polling-webhooks-answer",
            "text": "Webhooks let your application react to domain observations, while API reads let it reconcile the current state. We provide creation and monitor-update events with distinct meanings: creation doesn't mean HTTPS is ready. Authenticate deliveries, process repeats idempotently, and reconcile current API status so retries or delayed events don't move the onboarding UI backward."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/custom-domain-onboarding-checklist/#faq-dns-before-ssl",
          "url": "https://approximated.app/blog/custom-domain-onboarding-checklist/#faq-dns-before-ssl",
          "name": "Why can DNS be verified while a custom domain SSL certificate is still pending?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/custom-domain-onboarding-checklist/#faq-dns-before-ssl-answer",
            "text": "DNS and certificate issuance are different checks. The record may point correctly while domain validation, certificate issuance, or the actual HTTPS route is still pending. Show that DNS is correct and that the domain is being secured, then confirm a valid certificate and tenant response. A proxy in front of the edge can also change the validation path, so test the public route."
          }
        }
      ]
    },
    {
      "@type": "BlogPosting",
      "@id": "https://approximated.app/blog/apex-domains-for-saas/#article",
      "url": "https://approximated.app/blog/apex-domains-for-saas/",
      "headline": "Apex domains for SaaS: DNS choices and SSL",
      "description": "Support customer root domains with A records, ALIAS or CNAME flattening, or redirects. Learn the DNS and HTTPS checks each choice needs.",
      "abstract": "a customer can point www.example.com at your SaaS with a normal CNAME, but the root example.com needs another path. Offer an A record to an address your proxy controls, a DNS provider's ALIAS or CNAME-flattening feature, or a redirect from the root to www. The right instruction depends on the customer's DNS provider and on how your edge provisions HTTPS.",
      "datePublished": "2026-08-13",
      "dateModified": "2026-09-28",
      "inLanguage": "en",
      "articleSection": "DNS",
      "author": {
        "@type": "Organization",
        "@id": "https://approximated.app/#organization",
        "name": "Approximated",
        "url": "https://approximated.app/"
      },
      "publisher": {
        "@type": "Organization",
        "@id": "https://approximated.app/#organization",
        "name": "Approximated",
        "url": "https://approximated.app/"
      },
      "mainEntityOfPage": {
        "@type": "WebPage",
        "@id": "https://approximated.app/blog/apex-domains-for-saas/"
      },
      "isPartOf": {
        "@id": "https://approximated.app/blog/#blog"
      },
      "isAccessibleForFree": true,
      "wordCount": 1029,
      "keywords": [
        "Apex domains",
        "DNS records",
        "CNAME flattening",
        "HTTPS redirects"
      ],
      "about": [
        {
          "@type": "DefinedTerm",
          "name": "Apex domains"
        },
        {
          "@type": "DefinedTerm",
          "name": "DNS records"
        },
        {
          "@type": "DefinedTerm",
          "name": "CNAME flattening"
        },
        {
          "@type": "DefinedTerm",
          "name": "HTTPS redirects"
        }
      ],
      "citation": [
        "https://www.rfc-editor.org/rfc/rfc1034",
        "https://developers.cloudflare.com/dns/cname-flattening/set-up-cname-flattening/",
        "https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-choosing-alias-non-alias.html",
        "https://approximated.app/docs/#what-is-a-proxy-cluster",
        "https://approximated.app/approximated-cloudflare-comparison/",
        "https://letsencrypt.org/docs/challenge-types/",
        "https://approximated.app/docs/#virtual-host-statuses",
        "https://approximated.app/docs/#webhooks",
        "https://approximated.app/dns-widget/",
        "https://approximated.app/blog/custom-domain-onboarding-checklist/",
        "https://approximated.app/#waf",
        "https://approximated.app/docs/#edge-verify",
        "https://approximated.app/#faq",
        "https://approximated.app/pricing/",
        "https://approximated.app/self-hosted/"
      ],
      "hasPart": [
        {
          "@id": "https://approximated.app/blog/apex-domains-for-saas/#faq"
        }
      ],
      "encoding": {
        "@type": "MediaObject",
        "encodingFormat": "text/markdown",
        "contentUrl": "https://approximated.app/blog/apex-domains-for-saas/index.md"
      }
    },
    {
      "@type": "FAQPage",
      "@id": "https://approximated.app/blog/apex-domains-for-saas/#faq",
      "url": "https://approximated.app/blog/apex-domains-for-saas/#faq",
      "name": "Apex domains for SaaS: DNS choices and SSL: frequently asked questions",
      "inLanguage": "en",
      "isPartOf": {
        "@id": "https://approximated.app/blog/apex-domains-for-saas/#article"
      },
      "mainEntity": [
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/apex-domains-for-saas/#faq-cname-restriction",
          "url": "https://approximated.app/blog/apex-domains-for-saas/#faq-cname-restriction",
          "name": "Why can't a standard CNAME record be used at the domain apex?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/apex-domains-for-saas/#faq-cname-restriction-answer",
            "text": "A standard CNAME can't coexist with other records at the same DNS name. A zone apex already needs records such as SOA and NS, so a plain apex CNAME conflicts with the DNS model. Provider features called ALIAS, ANAME, or CNAME flattening work around that constraint through provider-specific behavior. Their availability and target restrictions vary."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/apex-domains-for-saas/#faq-record-type",
          "url": "https://approximated.app/blog/apex-domains-for-saas/#faq-record-type",
          "name": "Which DNS record should a SaaS customer use for a root domain?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/apex-domains-for-saas/#faq-record-type-answer",
            "text": "Use an A record when your edge provides a stable IPv4 address, or a DNS-provider alias or flattening feature when that provider supports your target. We give each proxy cluster a dedicated IPv4 address that serves its configured customer domains, making an apex A record a straightforward option without requiring customers to change DNS providers."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/apex-domains-for-saas/#faq-redirect-certificate",
          "url": "https://approximated.app/blog/apex-domains-for-saas/#faq-redirect-certificate",
          "name": "Does redirecting an apex domain to www require an SSL certificate?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/apex-domains-for-saas/#faq-redirect-certificate-answer",
            "text": "Yes, for an HTTPS redirect. A browser establishes TLS with the apex hostname before it can read the HTTP redirect to www or another hostname. The apex therefore needs a valid certificate even if it only redirects. Verify the certificate and the redirect separately, using the exact public hostname the customer will visit."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/apex-domains-for-saas/#faq-shared-address",
          "url": "https://approximated.app/blog/apex-domains-for-saas/#faq-shared-address",
          "name": "Does every customer apex domain need its own IP address?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/apex-domains-for-saas/#faq-shared-address-answer",
            "text": "No. A proxy can serve many configured hostnames on one address and select the appropriate certificate and route for each request. We provide a dedicated IPv4 address per proxy cluster, rather than one IP per customer hostname. Your application must still map each hostname to the correct tenant and enforce that tenant's authorization."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/apex-domains-for-saas/#faq-ongoing-checks",
          "url": "https://approximated.app/blog/apex-domains-for-saas/#faq-ongoing-checks",
          "name": "What should I monitor after a customer apex domain connects?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/apex-domains-for-saas/#faq-ongoing-checks-answer",
            "text": "Monitor DNS answers, certificate validity, and the real HTTPS response for the intended tenant. A customer can later change DNS or place another proxy in front of the route, so setup success isn't permanent proof. Our DNS, SSL, and proxy-hit monitoring and webhooks keep edge changes visible; application request checks confirm that the origin still serves the right content."
          }
        }
      ]
    },
    {
      "@type": "BlogPosting",
      "@id": "https://approximated.app/blog/best-custom-domain-apis-for-saas/#article",
      "url": "https://approximated.app/blog/best-custom-domain-apis-for-saas/",
      "headline": "How to choose the best custom domain API for your SaaS",
      "description": "Compare Approximated, Cloudflare for SaaS, and Entri Power on TLS, apex DNS, WAF, DDoS protection, monitoring, support, self-hosting, and pricing.",
      "abstract": "choose a custom-domain API by how well it runs the feature in production: DNS and TLS, safe tenant routing, protection against abusive traffic, useful monitoring, and help when something goes wrong. We built Approximated for SaaS teams that want those capabilities together, with a dedicated cluster, straightforward apex support, public pricing with automatic volume discounts, and a self-hosting path as your app grows.",
      "datePublished": "2026-07-24",
      "dateModified": "2026-10-06",
      "inLanguage": "en",
      "articleSection": "Comparison",
      "author": {
        "@type": "Organization",
        "@id": "https://approximated.app/#organization",
        "name": "Approximated",
        "url": "https://approximated.app/"
      },
      "publisher": {
        "@type": "Organization",
        "@id": "https://approximated.app/#organization",
        "name": "Approximated",
        "url": "https://approximated.app/"
      },
      "mainEntityOfPage": {
        "@type": "WebPage",
        "@id": "https://approximated.app/blog/best-custom-domain-apis-for-saas/"
      },
      "isPartOf": {
        "@id": "https://approximated.app/blog/#blog"
      },
      "isAccessibleForFree": true,
      "wordCount": 1873,
      "keywords": [
        "Custom domain APIs",
        "SaaS infrastructure",
        "API pricing",
        "Self-hosted proxy infrastructure"
      ],
      "about": [
        {
          "@type": "DefinedTerm",
          "name": "Custom domain APIs"
        },
        {
          "@type": "DefinedTerm",
          "name": "SaaS infrastructure"
        },
        {
          "@type": "DefinedTerm",
          "name": "API pricing"
        },
        {
          "@type": "DefinedTerm",
          "name": "Self-hosted proxy infrastructure"
        }
      ],
      "citation": [
        "https://approximated.app/blog/custom-domains-for-saas-guide/",
        "https://developers.entri.com/power/overview",
        "https://approximated.app/#waf",
        "https://approximated.app/docs/#edge-verify",
        "https://approximated.app/docs/#virtual-host-statuses",
        "https://approximated.app/docs/#webhooks",
        "https://approximated.app/self-hosted/",
        "https://approximated.app/#faq",
        "https://approximated.app/pricing/",
        "https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/plans/",
        "https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/apex-proxying/",
        "https://www.reddit.com/r/CloudFlare/comments/1ey3jiu/price_of_entreprise_plan/",
        "https://www.entri.com/plans",
        "https://customdomain.ai/compare/entri",
        "https://approximated.app/#pricing",
        "https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started/",
        "https://developers.entri.com/power/configuration"
      ],
      "hasPart": [
        {
          "@id": "https://approximated.app/blog/best-custom-domain-apis-for-saas/#faq"
        }
      ],
      "encoding": {
        "@type": "MediaObject",
        "encodingFormat": "text/markdown",
        "contentUrl": "https://approximated.app/blog/best-custom-domain-apis-for-saas/index.md"
      }
    },
    {
      "@type": "FAQPage",
      "@id": "https://approximated.app/blog/best-custom-domain-apis-for-saas/#faq",
      "url": "https://approximated.app/blog/best-custom-domain-apis-for-saas/#faq",
      "name": "How to choose the best custom domain API for your SaaS: frequently asked questions",
      "inLanguage": "en",
      "isPartOf": {
        "@id": "https://approximated.app/blog/best-custom-domain-apis-for-saas/#article"
      },
      "mainEntity": [
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/best-custom-domain-apis-for-saas/#faq-criteria",
          "url": "https://approximated.app/blog/best-custom-domain-apis-for-saas/#faq-criteria",
          "name": "What should I compare in custom domain APIs for SaaS?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/best-custom-domain-apis-for-saas/#faq-criteria-answer",
            "text": "Compare Approximated, Cloudflare for SaaS, and Entri Power across the complete domain lifecycle: apex and subdomain DNS, automated HTTPS, origin routing, onboarding, removal, and ongoing monitoring. Include WAF and DDoS protection, form verification, webhooks, engineering support, deployment options, and the full domain-and-bandwidth bill. We built Approximated to bring these production capabilities together in dedicated proxy infrastructure for SaaS teams."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/best-custom-domain-apis-for-saas/#faq-approximated-fit",
          "url": "https://approximated.app/blog/best-custom-domain-apis-for-saas/#faq-approximated-fit",
          "name": "When is Approximated a good custom domain API choice?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/best-custom-domain-apis-for-saas/#faq-approximated-fit-answer",
            "text": "We're a strong fit when customer domains are a production feature your SaaS depends on. Our cloud combines dedicated clusters, automatic HTTPS, straightforward apex A records, WAF and DDoS protection, Edge Verify, domain monitoring, webhooks, and DNS onboarding. Real engineers can help with integration and incidents, and our published cloud and self-hosted plans let you evaluate costs and deployment scope up front."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/best-custom-domain-apis-for-saas/#faq-apex-providers",
          "url": "https://approximated.app/blog/best-custom-domain-apis-for-saas/#faq-apex-providers",
          "name": "Which custom domain providers support apex domains?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/best-custom-domain-apis-for-saas/#faq-apex-providers-answer",
            "text": "Our cloud supports apex A records through a dedicated anycast IPv4 address for each customer cluster; its configured tenant hostnames share that address. Entri Power documents a root-domain hosting workflow. Cloudflare's IP-based Apex Proxying requires an Enterprise plan plus a paid add-on; other apex routes can depend on the customer's DNS provider. Test the actual DNS instructions and plan requirements alongside the provider's production tools."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/best-custom-domain-apis-for-saas/#faq-cloud-cost",
          "url": "https://approximated.app/blog/best-custom-domain-apis-for-saas/#faq-cloud-cost",
          "name": "How much does Approximated Cloud cost for customer domains?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/best-custom-domain-apis-for-saas/#faq-cloud-cost-answer",
            "text": "Our published cloud rate is $0.25 per domain per month with a $50 monthly minimum. It includes 400 GB of bandwidth, with additional bandwidth at $0.05 per GB. Domain volume discounts apply automatically: four percentage points for each full 1,000 domains, up to 40%. At 10,000 domains, the domain charge is $0.15 per domain per month, before any bandwidth overage. Self-hosted plans have their own published prices and scope, and custom SLA terms are agreed separately. Use expected domains and traffic to calculate the complete bill."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/best-custom-domain-apis-for-saas/#faq-self-hosting",
          "url": "https://approximated.app/blog/best-custom-domain-apis-for-saas/#faq-self-hosting",
          "name": "Can I self-host custom domains as my SaaS grows?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/best-custom-domain-apis-for-saas/#faq-self-hosting-answer",
            "text": "Yes. You can start with Approximated Cloud, then move toward hybrid or full self-hosting as traffic and infrastructure requirements grow. Hybrid keeps our cloud API and dashboard while traffic and certificates run on your servers. Full self-hosting provides a separate installation with a local API and dashboard, with a different feature scope. Cloudflare for SaaS and Entri Power document managed proxy services without an equivalent published self-hosted platform. Our engineers can help plan deployment and any customer DNS migration."
          }
        }
      ]
    },
    {
      "@type": "BlogPosting",
      "@id": "https://approximated.app/blog/custom-domains-for-saas-guide/#article",
      "url": "https://approximated.app/blog/custom-domains-for-saas-guide/",
      "headline": "Custom domains for SaaS: a production guide",
      "description": "A production guide to SaaS custom domains: DNS, TLS, tenant routing, WAF and DDoS protection, monitoring, webhooks, and self-hosting.",
      "abstract": "a SaaS custom-domain feature is a lifecycle, not a DNS field. You need to decide which customer may claim a hostname, give them the right DNS record, prepare HTTPS, route the request to the correct tenant, and keep checking the connection after launch. A domain is ready only when the application answers on that hostname over valid HTTPS. We built Approximated to make this production path easier to ship and operate, from your first customer domain to a large SaaS fleet.",
      "datePublished": "2026-06-30",
      "dateModified": "2026-09-28",
      "inLanguage": "en",
      "articleSection": "Guide",
      "author": {
        "@type": "Organization",
        "@id": "https://approximated.app/#organization",
        "name": "Approximated",
        "url": "https://approximated.app/"
      },
      "publisher": {
        "@type": "Organization",
        "@id": "https://approximated.app/#organization",
        "name": "Approximated",
        "url": "https://approximated.app/"
      },
      "mainEntityOfPage": {
        "@type": "WebPage",
        "@id": "https://approximated.app/blog/custom-domains-for-saas-guide/"
      },
      "isPartOf": {
        "@id": "https://approximated.app/blog/#blog"
      },
      "isAccessibleForFree": true,
      "wordCount": 1457,
      "keywords": [
        "Custom domains for SaaS",
        "TLS certificates",
        "Tenant routing",
        "DNS onboarding"
      ],
      "about": [
        {
          "@type": "DefinedTerm",
          "name": "Custom domains for SaaS"
        },
        {
          "@type": "DefinedTerm",
          "name": "TLS certificates"
        },
        {
          "@type": "DefinedTerm",
          "name": "Tenant routing"
        },
        {
          "@type": "DefinedTerm",
          "name": "DNS onboarding"
        }
      ],
      "citation": [
        "https://approximated.app/docs/#virtual-host-statuses",
        "https://www.rfc-editor.org/rfc/rfc1034",
        "https://approximated.app/dns-widget/",
        "https://letsencrypt.org/docs/challenge-types/",
        "https://letsencrypt.org/docs/rate-limits/",
        "https://approximated.app/guides/",
        "https://approximated.app/self-hosted/",
        "https://approximated.app/#waf",
        "https://approximated.app/docs/#edge-verify",
        "https://approximated.app/docs/#webhooks",
        "https://approximated.app/#faq",
        "https://approximated.app/pricing/",
        "https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started/",
        "https://approximated.app/blog/best-custom-domain-apis-for-saas/",
        "https://approximated.app/blog/custom-domain-onboarding-checklist/",
        "https://approximated.app/blog/custom-domain-security/"
      ],
      "hasPart": [
        {
          "@id": "https://approximated.app/blog/custom-domains-for-saas-guide/#faq"
        }
      ],
      "encoding": {
        "@type": "MediaObject",
        "encodingFormat": "text/markdown",
        "contentUrl": "https://approximated.app/blog/custom-domains-for-saas-guide/index.md"
      }
    },
    {
      "@type": "FAQPage",
      "@id": "https://approximated.app/blog/custom-domains-for-saas-guide/#faq",
      "url": "https://approximated.app/blog/custom-domains-for-saas-guide/#faq",
      "name": "Custom domains for SaaS: a production guide: frequently asked questions",
      "inLanguage": "en",
      "isPartOf": {
        "@id": "https://approximated.app/blog/custom-domains-for-saas-guide/#article"
      },
      "mainEntity": [
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/custom-domains-for-saas-guide/#faq-definition",
          "url": "https://approximated.app/blog/custom-domains-for-saas-guide/#faq-definition",
          "name": "What is a custom domain for a SaaS application?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/custom-domains-for-saas-guide/#faq-definition-answer",
            "text": "A custom domain lets a customer use a hostname they own, such as app.customer.example, to access their workspace in your SaaS. DNS sends traffic to your edge, HTTPS secures the connection, and your application maps the hostname to the correct tenant. We handle the custom-domain proxy infrastructure while your app keeps control of tenant identity and authorization."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/custom-domains-for-saas-guide/#faq-setup",
          "url": "https://approximated.app/blog/custom-domains-for-saas-guide/#faq-setup",
          "name": "How do I add custom domains to a multi-tenant SaaS?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/custom-domains-for-saas-guide/#faq-setup-answer",
            "text": "Record the hostname against one authorized tenant, create its edge mapping, and show the customer the exact DNS record to publish. Check DNS and certificate readiness separately, then make a real HTTPS request that confirms the expected tenant answers. Our API, DNS onboarding, monitoring, and webhooks cover the edge workflow; your application owns the tenant association."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/custom-domains-for-saas-guide/#faq-root-subdomain",
          "url": "https://approximated.app/blog/custom-domains-for-saas-guide/#faq-root-subdomain",
          "name": "Can SaaS customers connect both root domains and subdomains?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/custom-domains-for-saas-guide/#faq-root-subdomain-answer",
            "text": "Yes, if your edge supports both hostname types. Subdomains usually use a CNAME. Root or apex domains need an A record, a supported DNS-provider alias or flattening feature, or a redirect to a subdomain. Our cloud provides a dedicated anycast IPv4 address per customer proxy cluster, shared by the tenant hostnames configured in that cluster. Your customers can connect apex domains with an A record at their existing DNS provider."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/custom-domains-for-saas-guide/#faq-readiness",
          "url": "https://approximated.app/blog/custom-domains-for-saas-guide/#faq-readiness",
          "name": "Does managed SSL mean a custom domain is ready to use?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/custom-domains-for-saas-guide/#faq-readiness-answer",
            "text": "A certificate is only one readiness check. The hostname must also resolve to the intended edge, reach a working origin, and render the correct tenant over HTTPS. We expose DNS, SSL, and proxy-hit observations separately. Use those signals for the onboarding UI and complete the check with an actual application request before marking the domain connected."
          }
        },
        {
          "@type": "Question",
          "@id": "https://approximated.app/blog/custom-domains-for-saas-guide/#faq-self-hosting",
          "url": "https://approximated.app/blog/custom-domains-for-saas-guide/#faq-self-hosting",
          "name": "Can I start with managed custom domains and later self-host?",
          "acceptedAnswer": {
            "@type": "Answer",
            "@id": "https://approximated.app/blog/custom-domains-for-saas-guide/#faq-self-hosting-answer",
            "text": "We offer cloud, hybrid, and full self-hosted deployment paths. Hybrid keeps our cloud API and dashboard while traffic and certificates run on your infrastructure. Full self-hosting provides a separate installation with a local API and dashboard, and its feature scope differs. Plan the deployment, address changes, and any customer DNS migration with our engineers before moving traffic."
          }
        }
      ]
    }
  ]
}
