Skip to contentSkip to navigationSkip to topbar
Rate this page:
On this page

Set up reverse DNS



API Overview

api-overview page anchor

Reverse DNS (formerly IP Whitelabel) allows mailbox providers to verify the sender of an email by performing a reverse DNS lookup upon receipt of the emails you send.

Reverse DNS is available for dedicated IP addresses only.

When setting up reverse DNS, Twilio SendGrid will provide an A Record (address record) for you to add to your DNS records. The A Record maps your sending domain to a dedicated Twilio SendGrid IP address.

A Reverse DNS consists of a subdomain and domain that will be used to generate a reverse DNS record for a given IP address. Once Twilio SendGrid has verified that the appropriate A record for the IP address has been created, the appropriate reverse DNS record for the IP address is generated.

You can also manage your reverse DNS settings in the Sender Authentication setion of the Twilio SendGrid App(link takes you to an external page).

For more about Reverse DNS, see "How to set up reverse DNS" in the Twilio SendGrid documentation.


POST/v3/whitelabel/ips

Base url: https://api.sendgrid.com

This endpoint allows you to set up reverse DNS.


Authentication

authentication page anchor
Authorizationstringrequired
Default: Bearer <<YOUR_API_KEY_HERE>>

on-behalf-ofstring

The on-behalf-of header allows you to make API calls from a parent account on behalf of the parent's Subusers or customer accounts. You will use the parent account's API key when using this header. When making a call on behalf of a customer account, the property value should be "account-id" followed by the customer account's ID (e.g., on-behalf-of: account-id <account-id>). When making a call on behalf of a Subuser, the property value should be the Subuser's username (e.g., on-behalf-of: <subuser-username>). See On Behalf Of for more information.

SchemaExample
ipstringrequired

The IP address for which you want to set up reverse DNS.


subdomainstring

The subdomain that will be used to send emails from the IP address. This should be the same as the subdomain used to set up an authenticated domain.


domainstringrequired

The root, or sending, domain that will be used to send message from the IP address.

201
SchemaExample
idinteger

The ID of the Reverse DNS.


ipstring

The IP address that this Reverse DNS was created for.


rdnsstring

The reverse DNS record for the IP address. This points to the Reverse DNS subdomain.


usersarray[object]

The users who are able to send mail from the IP address.


subdomainstring

The subdomain created for this reverse DNS. This is where the rDNS record points.


domainstring

The root, or sending, domain.


validboolean

Indicates if this is a valid Reverse DNS.


legacyboolean

Indicates if this Reverse DNS was created using the legacy whitelabel tool. If it is a legacy whitelabel, it will still function, but you'll need to create a new Reverse DNS if you need to update it.


last_validation_attempt_atinteger

A Unix epoch timestamp representing the last time of a validation attempt.


a_recordobject

Set up reverse DNS

set-up-reverse-dns page anchor
Node.js
Python
C#
Java
Go
PHP
Ruby
curl

_23
const client = require('@sendgrid/client');
_23
client.setApiKey(process.env.SENDGRID_API_KEY);
_23
_23
const data = {
_23
"ip": "192.168.1.1",
_23
"subdomain": "email",
_23
"domain": "example.com"
_23
};
_23
_23
const request = {
_23
url: `/v3/whitelabel/ips`,
_23
method: 'POST',
_23
body: data
_23
}
_23
_23
client.request(request)
_23
.then(([response, body]) => {
_23
console.log(response.statusCode);
_23
console.log(response.body);
_23
})
_23
.catch(error => {
_23
console.error(error);
_23
});


Rate this page: