Skip to contentSkip to navigationSkip to topbar
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 (for global users and subusers)

Base url: https://api.eu.sendgrid.com (for EU regional subusers)

This endpoint allows you to set up reverse DNS.


Authentication

authentication page anchor
Property nameTypeRequiredDescription
authorizationstring
required
Default: Bearer <<YOUR_API_KEY_HERE>>

onBehalfOfstring

Optional

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.

Encoding type:application/json
SchemaExample
Property nameTypeRequiredDescriptionChild properties
ipstring
required

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


subdomainstring

Optional

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.


domainstring
required

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

201
SchemaExample
Property nameTypeRequiredDescriptionChild properties
idinteger

Optional

The ID of the Reverse DNS.


ipstring

Optional

The IP address that this Reverse DNS was created for.


rdnsstring

Optional

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


usersarray[object]

Optional

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


subdomainstring

Optional

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


domainstring

Optional

The root, or sending, domain.


validboolean

Optional

Indicates if this is a valid Reverse DNS.


legacyboolean

Optional

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.


lastValidationAttemptAtinteger

Optional

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


aRecordobject

Optional

Set up reverse DNSLink to code sample: Set up reverse DNS
1
const client = require("@sendgrid/client");
2
client.setApiKey(process.env.SENDGRID_API_KEY);
3
4
const data = {
5
ip: "192.168.1.1",
6
subdomain: "email",
7
domain: "example.com",
8
};
9
10
const request = {
11
url: `/v3/whitelabel/ips`,
12
method: "POST",
13
body: data,
14
};
15
16
client
17
.request(request)
18
.then(([response, body]) => {
19
console.log(response.statusCode);
20
console.log(response.body);
21
})
22
.catch((error) => {
23
console.error(error);
24
});