App

Monocle Custom Domains

Custom Domains allow you to serve Monocle from a subdomain of your own domain.

This enables:

  • Custom branding
  • Simpler Content Security Policy (CSP) configuration
  • Avoiding third-party script blocking
  • Additional same-origin client-side checks

How It Works

Monocle is served from a dedicated subdomain of your domain.

Note

The subdomain must be mcl and cannot be changed.

For example:
https://mcl.yourdomain.com

Setup

  1. 1
    Configure DNS

    Add the following NS records to your domain:

    mcl NS 3600 a.mcldns.com
    mcl NS 3600 b.mcldns.net
    mcl NS 3600 c.mcldns.org
    mcl NS 3600 d.mcldns.co.uk

    • Use the NS record type
    • Do not use CNAME or ALIAS
    • All four records must be configured
  2. 2
    Verify the subdomain

    Open your browser and go to:

    html
    https://mcl.yourdomain.com
    • An SSL warning is expected initially
    • If the domain doesn’t resolve, wait for DNS propagation
  3. 3
    Wait for provisioning

    When first accessed, Monocle will:

    • Provision the domain
    • Request and apply an SSL certificate

    This usually takes under a minute, but can take up to 5 minutes.

  4. 4
    Update your integration

    Replace mcl.spur.us or js.mcl.io with:

    html
    https://mcl.yourdomain.com

    Monocle will then load from your domain.

Important Notes

  • DNS records must remain in place
  • SSL provisioning is handled automatically
  • This enables first-party delivery of Monocle assets

When to Use Custom Domains

Use Custom Domains when:

  • You want Monocle to appear as a first-party script
  • You have strict CSP rules
  • You want to avoid third-party script blocking
  • You need same-origin access for advanced checks