
To set up a TLSA record, you'll need to create a DNS record that points to a specific server or service. This record is used to verify the identity of a server or service.
The TLSA record is a type of DNS record that's used to store the public key of a TLS certificate. It's typically used with DANE (DNS-based Authentication of Named Entities) to authenticate the identity of a server or service.
The TLSA record is usually stored in the DNS zone file, and it's used by clients to verify the identity of a server or service before establishing a secure connection.
Related reading: Aws S3 No Verify Ssl
Understanding TLSA Records
To check your TLSA record, you can use an online lookup tool like ClouDNS Free DNS tool or install WSL (Windows Subsystem for Linux) and follow the Linux/macOS instructions.
Linux and macOS users can open the Terminal and check their TLSA record via DIG with a command like $ dig example.com TLSA.
Explore further: Check Your Dns over Https Settings
A TLSA record must be placed at _[port]._[protocol].[domain] in your DNS zone, and most DNS service providers offer a form to set the 'usage', 'selector', 'matching' and 'certificate association data' fields separately.
TLSA records are not meant to ever change, so you can use a long time-to-live (TTL) value for the record, such as 1 day (86400 seconds) or more.
Why a Record?
A TLSA record is essential for implementing the DANE security protocol, which makes your DNS structure more secure.
The DANE protocol is related to DNSSEC, and it's now widely used.
The TLSA record allows users to verify the certificate received from a website by querying for its information in DNS, which is a fundamental aspect of the DANE protocol.
This verification process helps to ensure that the certificate is legitimate and trustworthy.
The TLSA record plays a crucial role in securing your DNS structure, making it a vital component of the DANE protocol.
By using a TLSA record, you can add an extra layer of security to your website, protecting your users' sensitive information.
For your interest: Important Information regarding Your Google Account
Dane Record Location
When using DANE, a TLSA record must be placed at the following location.
A TLSA record can be placed at multiple locations, but at least one of them has to match a certificate, and the rest will be ignored.
You can have multiple TLSA records at the same location.
Here's a summary of the DANE TLSA record location:
- Multiple TLSA records can exist at the same location.
- At least one TLSA record must match a certificate.
This is important to keep in mind when setting up DANE for your domain.
Checking and Managing TLSA Records
You can check your TLSA record using the DIG command on Linux/macOS systems. Simply open the Terminal and type: $ dig example.com TLSA.
The information about your TLSA records will appear. Alternatively, you can use an online lookup tool like ClouDNS Free DNS tool.
To manage your TLSA record, you'll need to place it in your DNS zone at _[port]._[protocol].[domain]. Most DNS service providers offer a form to set the 'usage', 'selector', 'matching' and 'certificate association data' fields separately, and they expect the data to be in hexadecimal format.
A TTL of 1 day (86400 seconds) or more is not uncommon for TLSA DNS records.
Recommended read: Dig Ptr Record
Checking My Record
If you're running Windows, you can't easily check your TLSA record using Nslookup or Powershell's Resolve-DnsName.
You have a couple of options: install WSL (Windows Subsystem for Linux) and use a Linux/macOS tool, or use an online lookup tool like ClouDNS Free DNS tool.
Linux and macOS users can check their TLSA record via DIG in the Terminal with a simple command: $ dig example.com TLSA.
You might enjoy: Google Identity Check Pixel Phones
Start Managing Your Domain Name
To start managing your domain name, you can begin by opening a free account from a specific website, which is free forever. You'll need to verify your email address before proceeding.
First, you'll need to log in to your control panel to access your domain settings. From there, you can create a new DNS zone using the CREATE ZONE button.
To create a new DNS zone, you'll need to follow a specific process. Here's a step-by-step guide:
- Create a new DNS zone from the CREATE ZONE button.
- Add the TLSA records you need as described in this article.
Once you've created your DNS zone and added your TLSA records, you'll be able to start managing your domain name with ease.
Platform-Specific Instructions
If you're using a Mac, you can easily lookup TLSA records using the terminal.
To open the terminal on a Mac, press [command] + [space] and type 'terminal.app', then press [enter].
The command to type in the terminal is dig example.com tlsa and hit [enter] to get the TLSA records for example.com.
The TLSA records are listed below the ANSWER SECTION heading.
Related reading: How to Turn off Cross Site Tracking on Mac
Creating and Updating TLSA Records
Creating a TLSA record is a straightforward process. Go to your DNS zone management page, click on Add new record, and choose TLSA as the record type.
The TLSA record must be placed at a specific location, which is determined by the protocol and port number. For example, if you're using SMTP, the record must be placed at _25._tcp.[domain].
To create the certificate association data field, you'll need to use OpenSSL. The value should be in hexadecimal form and is case-insensitive. For example, if you're using usage=3 (DANE-EE) and match=1 (SHA256), the input certificate should be the domain certificate.
Intriguing read: Dns Records Example
The TLSA record must be placed in your DNS zone, and most DNS service providers will expect the data to be in hexadecimal format. You can use a long time-to-live (TTL) value for the record, such as 1 day (86400 seconds) or more.
If you're replacing a certificate, you may need to create new TLSA records. The table below highlights the scenarios where a new TLSA record is required:
It's recommended to add a new TLSA record instead of replacing the old one, and remove the old record after some time (e.g., 24 hours) to allow cached properties to expire gracefully.
Revoking and Deleting TLSA Records
Revoking a TLSA record is done by removing the TLSA DNS record.
Unlike for example with DKIM, DANE/TLSA does not specify a 'positive denial' record format.
If a certificate or key is no longer in use, it is recommended to remove the corresponding TLSA record from the DNS zone.
Removing a TLSA record is a straightforward process, simply delete the record from your DNS zone.
TLSA Record Details
A TLSA record is a binary format record, which means most DNS service providers will expect the data to be in hexadecimal format, as outputted by the command line example.
The TLSA record must be placed at _[port]._[protocol].[domain], and a TTL of 1 day (86400 seconds) or more is not uncommon for TLSA DNS records.
The certificate association data should be in hexadecimal form and are case-insensitive, and the name of the TLSA record in punycode format is also a required field.
Here is a list of the required fields for a TLSA record:
Certificate Data
Certificate data is the heart of a TLSA record, and it's essential to get it right. The certificate data should be in hexadecimal form and is case-insensitive.
The certificate data field will be the hash digest of the entire certificate in DER (binary) format when selector=0 (full certificate) is used. This is the most common and recommended hash method, which is SHA256.
Here are the specific requirements for the certificate data field:
The name of the TLSA record in punycode format is also included in the certificate data field. This is an important detail to keep in mind when creating and managing your TLSA records.
Object Reference
As you delve into the world of TLSA records, you'll come across object references, which can be a bit tricky to understand at first. An object reference to a TLSA record has the following components: the name of the record and the name of the view.
The name part of a TLSA record object reference can be broken down into two main components: the name of the record and the name of the view. I've seen this format used in various online tools and documentation.
Here's an example of what a TLSA record object reference might look like: record:tlsa/ZG5zLmhvc3RjkuMC4xLg:9.9.0.1/some.name.com/default. This format is specified in the Object Reference section of the documentation.
If you're working with TLSA records, it's essential to understand the format of object references, as they can be used to retrieve specific records from your DNS zone.
Explore further: Android 16 Pixel 9 Fingerprint Unlock
TLSA Record Fields
A TLSA record has several fields that need to be filled out when creating one. The basic version of the object contains the fields name and view.
The required fields to create a TLSA record object are: certificate_data, certificate_usage, matched_type, name, and selector. These fields are used to specify the certificate association data, usage, matching type, name, and selector of the record.
Here are the details of each field:
Format
The TLSA record format is a binary record format, defined in rfc6698. It's often displayed in a specific format, with the certificate association data in hexadecimal format, case-insensitive.
Most DNS service providers will offer an input form to create a TLSA record, and if they allow text input, it's usually expected in the format of a binary record with hexadecimal values.
The TLSA record type is a binary record format, which is different from DKIM, which uses TXT type DNS records.
The TLSA record format is typically displayed as a series of values, including the Host Label, TTL, Record Class, Record Type, Certificate Usage, Selector, Matching Type, and Certificate Association Data.
Suggestion: Xfinity Wifi Security Type

Here's a breakdown of the TLSA record format:
The Certificate Usage field has four possible values, which are defined as follows:
- 0: Certificate Authority Constraint
- 1: Service Certificate Constraint
- 2: Trust Anchor Assertion
- 3: Domain Issued Certificate
The Matching Type field has three possible values, which are defined as follows:
- 0: No hash
- 1: SHA-256 hash
- 2: SHA-512 hash
Fields List
The fields that make up a TLSA record are quite specific, but understanding them is crucial for creating and working with these records.
The certificate_data field is a string that contains the hex dump of either raw data for matching type 0, or the hash of the raw data for matching types 1 and 2.
The certificate_usage field is an unsigned int that specifies how the TLSA record is used, with values ranging from 0 to 3, corresponding to Certificate Authority Constraint, Service Certificate Constraint, Trust Anchor Assertion, and Domain Issued Certificate, respectively.
The matched_type field is an unsigned int that specifies how the certificate association is presented, with values ranging from 0 to 2, corresponding to No hash, SHA-256 hash, and SHA-512 hash, respectively.

The name field is a string that contains the name of the TLSA record in punycode format.
The selector field is an unsigned int that specifies which part of the TLSA certificate presented by the server will be matched against the association data, with values ranging from 0 to 1, corresponding to Full certificate and Use Subject Public Key, respectively.
The following table summarizes the fields that make up a TLSA record:
TLSA Record Configuration
To configure a TLSA record, you'll need to create a new DNS record with the following settings: Type TLSA, TTL of 1 hour, and a hostname in the format _port._protocol (e.g., _100._tcp).
The TLSA record type is a binary format record, so most DNS service providers will expect the data to be in hexadecimal format. You can use a long time-to-live (TTL) value for the record, such as 1 day (86400 seconds) or more, since TLSA records are not meant to ever change.
To choose a 'selector' value, consider the following options: 0 (full certificate) or 1 (subject public key). If using selector=0, the TLSA record must be replaced every time the certificate is renewed or replaced. On the other hand, if using selector=1, the TLSA record only needs to be replaced when the key is rotated.
Here are some guidelines to keep in mind when choosing a 'selector' value:
For the 'matching' type, you have three options: 0 (exact match), 1 (SHA2-256 hash digest), or 2 (SHA2-512 hash digest). Matching=1 (SHA2-256) is the most common and recommended value to use for the 'matching' value, especially when using DANE for SMTP.
To determine which certificate to use as input, consider the usage value: if using usage=2 (DANE-TA), you should use selector=0 (full certificate).
TLSA Record Options
When creating a TLSA record, you have several options to consider.
The "Usage" field specifies the provided association that will be used to match the certificate presented in the TLS handshake, and it can be set from 0 to 3.
The "Selector" field specifies which part of the TLS certificate presented by the server will be matched against the association data, and it can be set from 0 to 1.
The "Matching-Type" field specifies how the certificate association is presented, and it can be set from 0 to 2.
TLSA records are not meant to ever change, so it's a good idea to use a long time-to-live (TTL) value for the record.
A TTL of 1 day (86400 seconds) or more is not uncommon for TLSA DNS records.
Here's a summary of the TLSA record fields:
TLSA Record Support
You can create a DNS TLSA record by going to your DNS zone management page and clicking on Add new record.
For the Type, choose TLSA and fill in the required fields. The hostname is used as an example, so you can replace it with your own.
Here are the required fields for a TLSA record:
ClouDNS provides full support for TLSA records for all their DNS services, including Free DNS, Premium DNS, DDoS Protected DNS, and GeoDNS.
TLSA Record Lookup
Checking your TLSA record can be a bit tricky, but don't worry, I've got you covered. You can install WSL (Windows Subsystem for Linux) and follow the Linux/macOS instructions, or use an online lookup tool like ClouDNS Free DNS tool.
If you're using a Linux or macOS system, you can simply open a terminal and check your TLSA record via DIG. For example, you can type `$ dig example.com TLSA` to get the information.
The TLSA record type is not supported in Windows, so you'll need to either install WSL or use an online tool. You can also try using an online TLSA lookup tool, which can query the records for you.
To check your TLSA records on a Mac, open a terminal by pressing `[command] + [space]` and then type `dig example.com tlsa` to get the records. You can also use an online lookup tool for this.
Here are the general steps to check your TLSA records:
- Open a terminal or use an online lookup tool
- Enter the domain name and hit enter
- The tool will query the TLSA records and show them to you
You can also check the DANE TLSA record location, which is where the TLSA record must be placed when using DANE. This location is:
- Multiple TLSA records may exist at the same location
- At least one of the TLSA records must match a certificate, the rest will be ignored
Note that the TLSA record location is specific to DANE and may not be relevant to other use cases.
Featured Images: pexels.com


