Allowed Domains

Your Organization’s content only shows on websites you allowed. Configure them in NXT under Settings → General → Allowed embed domains.

The list starts empty, and an empty list allows no website except local development hosts (localhost, 127.0.0.1), which are always allowed. Add your domains before your embeds go live.

What an entry allows

An entry allows a whole domain, including every subdomain:

Entry Allows
example.com https://example.com, https://www.example.com, https://news.example.com, …
myapp: an app whose pages run under the custom URL scheme myapp: (see App Integration)

You don’t need to list www.example.com separately when example.com is listed. You can also enter a full address such as https://www.example.com/news/: NXT stores it as its domain, example.com.

To allow an app’s custom URL scheme, enter the scheme followed by a colon, for example myapp: (or myapp://).

Pages whose origin is null, which some WebViews send, are always blocked, and no entry can allow them. Pages opened from a local file (file:) are blocked unless you list file:. For apps, load a hosted https:// page instead (see App Integration).

What we check

When the embed loads content, or a reader votes or sends a form, the reader’s browser sends the address of your page (its origin, e.g. https://www.example.com). We reduce it to its domain and compare that with your list. Polls, quizzes and forms are checked the same way when a reader votes, answers or submits.

On a website that is not allowed

The element shows:

This content is not enabled for this website

and the browser console shows a warning that names your website’s host:

[nxt1] This website (www.example.com) is not enabled to embed this content. Add its domain to the allowed embed domains in nxt CMS settings.

To fix it, add the domain under Settings → General → Allowed embed domains in NXT. A change takes effect within about two minutes; then reload the page.

Content previews inside NXT itself always work, whatever your list contains.