custom domains

You can serve fonts from your own domain — fonts.yourcompany.com instead of cdn.onlyfonts.ai. Same CDN, your hostname, first-party requests.

why

• first-party font requests: no third-party hostname in your page at all
• your domain in view-source and in CSP rules
• serve your own uploaded fonts and your catalog selections from one place

setup

1. sign in and open the dashboard
2. add the fonts you want to serve: pick catalog fonts or upload your own
3. go to domains, add your hostname (for example fonts.yourcompany.com)
4. add the DNS records the dashboard shows you — a CNAME pointing your hostname at cdn.onlyfonts.ai, plus a verification record
5. wait for the status to turn verified — DNS and SSL checks run automatically, and you can trigger a recheck from the domain’s page

Once verified, the same CSS endpoints work on your hostname:

<link href="https://fonts.yourcompany.com/css2?family=Inter:wght@400;700" rel="stylesheet">

scope

A custom domain serves only the fonts attached to your account — your catalog selections and your uploads. Requests for fonts you haven’t added return 404. This keeps your font surface deliberate instead of mirroring the whole catalog.

uploaded fonts

Custom fonts you upload through the dashboard are served the same way, with the same caching. You confirm you hold a license to serve any font you upload — see licenses.