Skip to main content

Domain validation

Written by Alexandre Dias Da Silva

Overview

Domain validation allows you to prove that a domain configured in Axeptio belongs to you, and optionally restrict your widget's execution to that domain only.

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

  1. Allow the Axeptio SDK to function on all domains (default behavior).

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

After any modification, you must publish the widget for the changes to take effect.


Prerequisites

Before you begin, make sure you have:

  • access to your Axeptio project;

  • the necessary rights to modify project configuration;

  • access to the DNS zone of the domain to be validated, via your hosting provider, registrar, or DNS management tool;

  • identified the primary domain of your website.

Example:

mysite.com

Step 1 — Enter the project's primary domain

From the Axeptio interface, open the project in question.

  1. Open the project details.

  2. Go to the Domain Management section.

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

  4. Save the change.

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

To use:

mysite.com

To avoid — full URL with protocol or path:

https://www.mysite.com/page

Step 2 — Add the DNS validation record

Once the primary domain is entered, Axeptio generates a validation key to add to your DNS zone. This key allows Axeptio to 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 information:

DNS Field

Value

Type

TXT

Name / Host / Subdomain

_axeptio-verify

Value

Validation key provided by Axeptio

TTL

Default or automatic value

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

_axeptio-verify

Or the complete 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. Start the verification.

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

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

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


Step 4 — Choose the SDK operating mode

After validation, two behaviors are possible.

Option 1 — Allow the SDK to function on all domains

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

Examples:

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

In this case, domain validation only serves to prove ownership of the primary domain. It does not block SDK execution elsewhere.

Option 2 — Restrict the SDK to the validated domain

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

This strengthens control over your widget's usage and prevents an Axeptio configuration from being executed from an unauthorized domain.

To enable restriction:

  1. Go to Domain Management.

  2. Make sure the primary domain is properly validated.

  3. Enable the domain restriction checkbox.

  4. Save the change.

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


Step 5 — Publish the widget

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

  1. Click Publish at the top of the window.

  2. Wait for the publication confirmation.

  3. Reload your site to verify proper functioning.

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

Did this answer your question?