This reference article lists each domain that Miro uses in its SaaS application.
✏️ Some third-party applications developed for Miro, and Miroverse applications, may rely on external domains and services that Miro does not control.
Global production domains
Organizations that use a secured network must allow the following global production domains:
*.miro.com
Include derivatives, for example: *.api.miro.com | *.svc.miro.com
*.miro-apps.com
mirostatic.com
*.mirostatic.com
onlinewhiteboard.com
realtimeboard.com
*.realtimeboard.com
webwhiteboard.com
Production tooling domains
Organizations that use a secured network must allow the following production tooling domains:
braze.eu
*.braze.eu
browser.sentry-cdn.io
cdn.cookielaw.org
fonts.googleapis.com
fonts.gstatic.com
miroapp.github.io
realtimeboardhelp.zendesk.com
*.sentry.io
split.io
*.split.io
Regional production domains
Organizations that use a secured network must allow the following regional production domains.
✏️ In addition to global production domains, and production tooling domains, you must also allow regional production domains for data residency in Australia, or United States, whichever applies.
Australia
*.au.miro.com
Include derivatives, for example: *.api.au.miro.com | *.svc.au.miro.com
*.au01.miro.com
United States
*.us.miro.com
Include derivatives, for example: *.api.us.miro.com | *.svc.us.miro.com
*.us01.miro.com
More information:
-
How to allowlist Miro mailers
Learn about Miro mailer domains -
Add Miro to allowed apps
Learn about websockets and proxy