Skip to main content

TXT records

TXT records store text associated with a DNS name. Use them to publish domain verification values, email authentication information, and other text required by a service.

DigiCert®​​ DNS provides five TXT syntax options: Generic, SPF, DKIM, DMARC, and BIMI. All five publish DNS TXT records.

What a TXT record is

A TXT record associates a DNS name with one or more text values. The service reading the record determines how those values are interpreted.

For example, a service might ask you to publish a verification value at example.com to demonstrate control of that domain.

You can create TXT records at the zone apex or at a name within the zone. Use the exact name and value supplied by the service requesting the record.

For secondary zones, make record changes at the primary DNS provider. See Secondary DNS zones.

Explore TXT records on the Records page

To view TXT records, go to DNS > Zones, select Primary zones, open the zone, and select the Records tab.

In Grouped view, expand TXT (Text).

The table displays the following information:

Column

Description

Record name

The complete DNS name, including the zone name

Contains

The text published by the record

TTL

How long the record can be cached, in seconds

Source

Whether the record is User-defined or System

Use Search to locate a record or switch to Table view to review records in a table.

Each row provides the available management actions. System records cannot be deleted directly from the Records page.

Create a TXT record

To create a TXT record, open the zone’s Records tab:

  1. Select Add record, either at the top of the page or beside TXT (Text).

  2. Set Record type to TXT (Text).

  3. Enter the Name, or use @ for the zone apex.

  4. Enter the TTL in seconds.

  5. Under Syntax, select the TXT record type.

  6. Enter the text value in Contains.

  7. If available, select Add another to include another value.

  8. Select Save and close, or Save and add another to continue creating records.

    If a duplicate is found when you save, a banner directs you to edit the existing record. Update that entry instead of creating another.

The form contains these fields:

Field

Description

Record type

Select TXT (Text)

Name

The name within the zone, or @ for the zone apex

TTL

The cache duration, in seconds

TXT record type

The syntax option: Generic, SPF, DKIM, DMARC, or BIMI

Contains

The text value to publish

The zone name appears beneath Name. For a zone named example.com, entering _dmarc produces _dmarc.example.com.

You can also add records through Import records. See Import DNS records.

Update or delete a TXT record

To update a TXT record:

  1. Locate the record on the Records tab.

  2. Open its actions menu and select Edit.

  3. Update the editable fields, such as TTL or Contains.

  4. Select Update.

When an entry contains multiple values, retain the values still required by other services. Remove only the value you intend to retire.

To delete a user-defined TXT entry, open its actions menu, select Delete, and confirm the deletion.

To delete multiple eligible entries, select their checkboxes and choose Delete from the selection toolbar. Review the selected records before confirming.

Deleting an entry can affect domain verification or email authentication. System-managed entries must be managed through the controlling feature or integration.

Previously cached values may remain available until their TTL expires.

Choose a TXT syntax type

Choose the syntax option that matches the purpose of the value you are publishing.

Syntax type

Purpose

Typical record name

Generic

Publishes generic text

The name supplied by the requesting service

SPF

Identifies servers authorized to send email using a domain

@ for the zone apex, or the relevant sending subdomain

DKIM

Publishes a public key used to verify email signatures

selector._domainkey

DMARC

Publishes email authentication policy and reporting preferences

_dmarc

BIMI

Publishes brand logo information for participating email providers

default._bimi, or another configured selector

For SPF, use the policy supplied or approved by your email administrator. Publish only one SPF policy at a given name; multiple records beginning with v=spf1 at that name are not permitted. Other TXT values, such as verification tokens, can coexist with the SPF policy.

For DKIM, use the selector and complete public key value supplied by your email provider. For example, selector selector1 uses the name selector1._domainkey. Publishing the key is one part of setup; the sending service must also sign messages.

For DMARC, use the policy and reporting destinations approved for your domain. A policy containing p=none requests monitoring without requesting quarantine or rejection based on DMARC failure. See DNS integrations if Valimail Monitor manages the domain’s DMARC configuration.

For BIMI, use the correct selector, logo location, and any required certificate information. Publishing a TXT record alone does not guarantee that an email provider will display the logo.

Generic TXT values and multiple entries

Choose Generic when publishing text that does not use one of the specialized syntax options. Common examples include domain verification tokens and service-specific identifiers.

Before entering a Generic value, identify:

  • The service requesting the record

  • The exact record name

  • The complete text value

  • Whether the service requires the record to remain after verification

Enter only the text value in Contains. Do not paste a complete zone file definition containing the name, TTL, class, and record type. Use Import DNS records for BIND-format definitions.

Preserve the supplied value, including capitalization, punctuation, and meaningful spaces. TXT records are publicly queryable, so do not use them to store passwords or private keys.

To publish multiple independent values at the same name, select Add another where available. Enter each value separately. For example, two services can each require a different verification token at the zone apex.

Do not combine unrelated verification tokens into a single value. Likewise, do not use Add another to split one long DKIM key or other single logical value across separate entries.

The availability of Add another depends on the syntax selection. Multiple TXT values at one name do not mean that every specialized syntax permits multiple policies or keys there.

Validate your TXT syntax

Enter the value in Contains, then save the record. The form automatically validates all TXT record types, including Generic, SPF, DKIM, DMARC, and BIMI.

If validation fails, review the selected TXT record type and the entered value, correct the issue, and save again.

Successful validation does not confirm that the complete service configuration is working. After saving, verify the record through the service that requested it. For example:

Syntax type

Additional verification

Generic

Confirm that the requesting service accepts the verification value

SPF

Confirm that the policy covers the intended sending services

DKIM

Confirm that outgoing messages are signed and their signatures verify

DMARC

Review authentication results and reporting

BIMI

Confirm that the logo, certificate where required, and provider requirements are satisfied

User-defined and system TXT records

The Source column identifies how a TXT record is managed.

Source

Meaning

User-defined

A record created and managed by a user

System

A record managed by DigiCert®​​ DNS or an integration, with restrictions on direct changes

System records cannot be deleted directly from the Records page. Manage their lifecycle through the feature or integration that controls them.

Enabling Valimail Monitor changes how DigiCert®​​ DNS creates, validates, edits, and deletes global and regional DMARC records to preserve the required Valimail reporting address. See Valimail Monitor for the applicable rules.

TTL and record changes

The TTL, or time to live, specifies how long a DNS record can be cached before it expires. Enter this value in seconds.

For example, a TTL of 300 represents five minutes.

After you update a TXT value, resolvers may continue returning a previously cached value until its TTL expires. Changing the TTL does not shorten the lifetime of copies already cached using the previous value.

When planning a change, consider lowering the TTL in advance and allowing the previous TTL to expire before updating the value.

A service may also have its own verification or polling schedule. Successful saving in DigiCert®​​ DNS does not mean that the service has already detected the change.