Skip to main content

Domain Validation

Written by Adrian ESCRIVA

Domain Validation

Overview

Domain validation lets you prove that a domain you've configured in Axeptio actually belongs to you, and optionally restrict your widget to run only on that domain.

Validation works by adding a TXT DNS record to your domain's DNS zone. Once the domain is validated, you can choose between two modes:

  1. Allow the Axeptio SDK to run on any domain (default behavior).

  2. Restrict SDK execution to the validated domain only, to prevent your widget from being used on an unauthorized domain.

After any change, you must publish the widget for the new settings to take effect.


Prerequisites

Before you start, make sure you have:

  • access to your Axeptio project;

  • the permissions required to edit the project configuration;

  • access to the DNS zone of the domain you want to validate, through your hosting provider, registrar, or DNS management tool;

  • identified the main domain of your website.

Example:

mysite.com

Step 1 — Set the project's main domain

From the Axeptio interface, open the project you want to configure.

  1. Open the project details.

  2. Go to the Domain management section.

  3. Enter or update the main domain of your website.

  4. Save your changes.

The main domain must match the domain you want to validate.

Use:

mysite.com

Do not use a full URL with protocol or path:

https://www.mysite.com/page

Step 2 — Add the DNS validation record

Once the main domain is set, Axeptio generates a validation key that you need to add to your DNS zone. This key lets Axeptio verify that you have access to the domain's DNS configuration.

DNS record to create

In your DNS management tool, add a new record with the following values:

DNS field

Value

Type

TXT

Name / Host / Subdomain

_axeptio-verify

Value

The validation key provided by Axeptio

TTL

Default or automatic

Depending on your DNS provider, the Name, Host, or Subdomain field may be requested in different formats. You may need to enter either the short form:

_axeptio-verify

Or the full form:

_axeptio-verify.mysite.com

The TXT value must be copied exactly as displayed in Axeptio.

Example:

axeptio-verify=xxxxxxxxxxxxxxxx

Step 3 — Validate the domain in Axeptio

Once the DNS record has been added, return to Axeptio.

  1. Trigger the verification.

  2. Axeptio checks for the TXT record in your DNS zone.

  3. If the record is found, the domain status changes to validated.

Once validated, Axeptio considers you the owner or administrator of the configured domain.


Step 4 — Choose how the SDK should behave

After validation, two behaviors are available.

Option 1 — Let the SDK run on any domain

By default, the Axeptio SDK can run on every domain where it's installed. This mode is useful if your widget is intentionally used across multiple domains, environments, or sites.

Examples:

mysite.com blog.mysite.com partner-landing-page.com preprod.mysite.com

In this case, domain validation only proves ownership of the main domain. It does not block the SDK from running elsewhere.

Option 2 — Restrict the SDK to the validated domain

You can also enable domain restriction using the dedicated checkbox. When this option is on, the Axeptio SDK is only allowed to run on the validated domain.

This gives you tighter control over where your widget is used and prevents an Axeptio configuration from being executed on an unauthorized domain.

To enable the restriction:

  1. Go to Domain management.

  2. Make sure the main domain has been validated.

  3. Enable the domain restriction checkbox.

  4. Save your changes.

From this point on, after publishing, the widget will be limited to the validated domain.


Step 5 — Publish the widget

After updating the domain, validating ownership, or enabling restriction, you must publish the widget. This step is required for the changes to be applied on your website.

  1. Click Publish at the top of the window.

  2. Wait for the publication confirmation.

  3. Reload your website to verify that everything works as expected.

Without publishing, changes made in domain management will not yet be applied by the SDK.

Did this answer your question?