Overview

When setting up the FilPass TXT record, we recommend adding it to a subdomain (e.g., verified.domain.com or issuance.domain.com) rather than the root domain (e.g., domain.com). This article explains why this is the recommended approach.

1. Risk of Conflict with Existing TXT Records

The root domain commonly has existing TXT records already configured for other platforms and services, such as:

• Google Workspace

• Microsoft 365

• Email authentication tools such as SPF and DKIM

• Other third-party integrations

In the past, adding the FilPass TXT record to the root domain caused conflicts with these existing records, which led to issues with both FilPass document verification and other platform services running on the same domain.

2. Isolation and Clean Configuration

Using a dedicated subdomain keeps the FilPass TXT record isolated from other DNS configurations. This provides the following benefits:

• Easier to manage and update the TXT record independently

• Reduces the risk of affecting other services when changes are made

• Simplifies troubleshooting if verification issues arise in the future

3. Current Status

While the root domain may technically work in some cases, as DNS providers have become more accommodating of multiple TXT records, it is still not the recommended approach. The risk of conflicts remains, especially as more third-party services are added to the domain over time.

Using a subdomain is the safer, cleaner, and more future-proof approach.

Summary

The subdomain approach is recommended because it:

• Protects existing DNS settings on the root domain

• Prevents potential conflicts with other platform configurations

• Ensures reliable and consistent document verification through FilPass

Related Articles

• How to Add a TXT Record

• How to Integrate the FilPass Custom Verifier

• TXT Record Removed – Action Required to Restore Verification