# Domains and security

Your production keys only work on the domains declared on your account, and your test key on your own machine.

## Declared domains

Your production keys open the viewer only on the domains declared in your [dashboard](https://render.vskin.gg/dashboard), up to 5. A page on any other domain is refused.

- Paste the domain or a full address: only the host is kept, so `https://example.com/shop` becomes `example.com`. It then works over `http` and `https`.
- Each domain is matched exactly: `example.com` does not cover `www.example.com`, and wildcards such as `*.example.com` are not supported.
- A domain has at least one dot: `staging.example.com` can be declared, `staging` alone cannot.
- Leave the port out: a domain covers all of its ports.
- A staging site is declared like any other domain, and uses a production key: your test key never works there.

## Local development

`localhost`, its subdomains and IP addresses cannot be declared: on your own machine, use your test key. It works on `localhost` and `127.0.0.1`, on any port and over plain `http`, with nothing to declare, and never on your declared domains.

## Content Security Policy

If your site sends a `Content-Security-Policy` header, add our origin to these directives:

```http
Content-Security-Policy: frame-src https://embed.render.vskin.gg; script-src 'self' https://embed.render.vskin.gg
```

- `frame-src`, for the iframes and for the SDK, which draws the viewer in an iframe.
- `script-src`, only if you load the SDK with a script tag. Your own inline call to `createViewer` then needs a nonce, or must move to a script file your policy allows.
