DNS audit for openai.com created on 2026-06-07 01:01:56

PDF

1. Name servers

Name servers listed at the parent server m.gtld-servers.net:

ns1-02.azure-dns.com
ns2-02.azure-dns.net
ns3-02.azure-dns.org
ns4-02.azure-dns.info

Result: 4 name servers found at the parent server (set at the domain provider).
Recommendation: Everything is okay. There is more than one name server added to openai.com.

2. NS records

NS records returned by each name server configured for the domain name

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

ns1-02.azure-dns.com [13.107.236.2] (3ms):
ns1-02.azure-dns.com
ns2-02.azure-dns.net
ns3-02.azure-dns.org
ns4-02.azure-dns.info

ns2-02.azure-dns.net [150.171.21.2] (2ms):
ns1-02.azure-dns.com
ns2-02.azure-dns.net
ns3-02.azure-dns.org
ns4-02.azure-dns.info

ns3-02.azure-dns.org [204.14.183.2] (2ms):
ns1-02.azure-dns.com
ns2-02.azure-dns.net
ns3-02.azure-dns.org
ns4-02.azure-dns.info

ns4-02.azure-dns.info [208.84.5.2] (3ms):
ns1-02.azure-dns.com
ns2-02.azure-dns.net
ns3-02.azure-dns.org
ns4-02.azure-dns.info

ns1-02.azure-dns.com [13.107.236.2] (1ms):
ns1-02.azure-dns.com
ns2-02.azure-dns.net
ns3-02.azure-dns.org
ns4-02.azure-dns.info

ns2-02.azure-dns.net [150.171.21.2] (1ms):
ns1-02.azure-dns.com
ns2-02.azure-dns.net
ns3-02.azure-dns.org
ns4-02.azure-dns.info

ns3-02.azure-dns.org [204.14.183.2] (1ms):
ns1-02.azure-dns.com
ns2-02.azure-dns.net
ns3-02.azure-dns.org
ns4-02.azure-dns.info

ns4-02.azure-dns.info [208.84.5.2] (1ms):
ns1-02.azure-dns.com
ns2-02.azure-dns.net
ns3-02.azure-dns.org
ns4-02.azure-dns.info

ns1-02.azure-dns.com [13.107.236.2] (20ms):
ns1-02.azure-dns.com
ns2-02.azure-dns.net
ns3-02.azure-dns.org
ns4-02.azure-dns.info

ns2-02.azure-dns.net [150.171.21.2] (24ms):
ns1-02.azure-dns.com
ns2-02.azure-dns.net
ns3-02.azure-dns.org
ns4-02.azure-dns.info

ns3-02.azure-dns.org [204.14.183.2] (20ms):
ns1-02.azure-dns.com
ns2-02.azure-dns.net
ns3-02.azure-dns.org
ns4-02.azure-dns.info

ns4-02.azure-dns.info [208.84.5.2] (20ms):
ns1-02.azure-dns.com
ns2-02.azure-dns.net
ns3-02.azure-dns.org
ns4-02.azure-dns.info

ns1-02.azure-dns.com [13.107.236.2] (1ms):
ns1-02.azure-dns.com
ns2-02.azure-dns.net
ns3-02.azure-dns.org
ns4-02.azure-dns.info

ns2-02.azure-dns.net [150.171.21.2] (1ms):
ns1-02.azure-dns.com
ns2-02.azure-dns.net
ns3-02.azure-dns.org
ns4-02.azure-dns.info

ns3-02.azure-dns.org [204.14.183.2] (1ms):
ns1-02.azure-dns.com
ns2-02.azure-dns.net
ns3-02.azure-dns.org
ns4-02.azure-dns.info

ns4-02.azure-dns.info [208.84.5.2] (1ms):
ns1-02.azure-dns.com
ns2-02.azure-dns.net
ns3-02.azure-dns.org
ns4-02.azure-dns.info

Result: The NS records returned by the DNS servers are the same as the name servers set at the parent server.
Recommendation: It is not required to do any changes. All name servers are synchronized.

3. SOA record

SOA record returned by each name server configured for the domain name

San Francisco, US

ns1-02.azure-dns.com [13.107.236.2] (1ms):
ns1-02.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 300

ns2-02.azure-dns.net [150.171.21.2] (1ms):
ns1-02.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 300

ns3-02.azure-dns.org [204.14.183.2] (1ms):
ns1-02.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 300

ns4-02.azure-dns.info [208.84.5.2] (1ms):
ns1-02.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 300

Sydney, AU

ns1-02.azure-dns.com [13.107.236.2] (1ms):
ns1-02.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 300

ns2-02.azure-dns.net [150.171.21.2] (1ms):
ns1-02.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 300

ns3-02.azure-dns.org [204.14.183.2] (1ms):
ns1-02.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 300

ns4-02.azure-dns.info [208.84.5.2] (1ms):
ns1-02.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 300

Johannesburg, ZA

ns1-02.azure-dns.com [13.107.236.2] (16ms):
ns1-02.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 300

ns2-02.azure-dns.net [150.171.21.2] (16ms):
ns1-02.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 300

ns3-02.azure-dns.org [204.14.183.2] (16ms):
ns1-02.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 300

ns4-02.azure-dns.info [208.84.5.2] (16ms):
ns1-02.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 300

Singapore

ns1-02.azure-dns.com [13.107.236.2] (2ms):
ns1-02.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 300

ns2-02.azure-dns.net [150.171.21.2] (1ms):
ns1-02.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 300

ns3-02.azure-dns.org [204.14.183.2] (1ms):
ns1-02.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 300

ns4-02.azure-dns.info [208.84.5.2] (1ms):
ns1-02.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 300

Result: The SOA record returned by the name servers is the same on all of them.
Recommendation: It is not required to do any changes. The name servers are synchronized.

4. A record distribution by location for openai.com

Shows how the name servers respond to requests for openai.com

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

ns1-02.azure-dns.com [13.107.236.2] (1ms):
104.18.33.45
172.64.154.211

ns2-02.azure-dns.net [150.171.21.2] (1ms):
104.18.33.45
172.64.154.211

ns3-02.azure-dns.org [204.14.183.2] (1ms):
104.18.33.45
172.64.154.211

ns4-02.azure-dns.info [208.84.5.2] (18ms):
104.18.33.45
172.64.154.211

ns1-02.azure-dns.com [13.107.236.2] (1ms):
104.18.33.45
172.64.154.211

ns2-02.azure-dns.net [150.171.21.2] (1ms):
104.18.33.45
172.64.154.211

ns3-02.azure-dns.org [204.14.183.2] (2ms):
104.18.33.45
172.64.154.211

ns4-02.azure-dns.info [208.84.5.2] (1ms):
104.18.33.45
172.64.154.211

ns1-02.azure-dns.com [13.107.236.2] (20ms):
104.18.33.45
172.64.154.211

ns2-02.azure-dns.net [150.171.21.2] (20ms):
104.18.33.45
172.64.154.211

ns3-02.azure-dns.org [204.14.183.2] (16ms):
104.18.33.45
172.64.154.211

ns4-02.azure-dns.info [208.84.5.2] (16ms):
104.18.33.45
172.64.154.211

ns1-02.azure-dns.com [13.107.236.2] (1ms):
104.18.33.45
172.64.154.211

ns2-02.azure-dns.net [150.171.21.2] (1ms):
104.18.33.45
172.64.154.211

ns3-02.azure-dns.org [204.14.183.2] (1ms):
104.18.33.45
172.64.154.211

ns4-02.azure-dns.info [208.84.5.2] (1ms):
104.18.33.45
172.64.154.211

5. A record distribution by location for www.openai.com

Shows how the name servers respond to requests for www.openai.com

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

ns1-02.azure-dns.com [13.107.236.2] (1ms):

ns2-02.azure-dns.net [150.171.21.2] (1ms):

ns3-02.azure-dns.org [204.14.183.2] (1ms):

ns4-02.azure-dns.info [208.84.5.2] (1ms):

ns1-02.azure-dns.com [13.107.236.2] (1ms):

ns2-02.azure-dns.net [150.171.21.2] (1ms):

ns3-02.azure-dns.org [204.14.183.2] (1ms):

ns4-02.azure-dns.info [208.84.5.2] (1ms):

ns1-02.azure-dns.com [13.107.236.2] (20ms):

ns2-02.azure-dns.net [150.171.21.2] (16ms):

ns3-02.azure-dns.org [204.14.183.2] (20ms):

ns4-02.azure-dns.info [208.84.5.2] (20ms):

ns1-02.azure-dns.com [13.107.236.2] (1ms):

ns2-02.azure-dns.net [150.171.21.2] (1ms):

ns3-02.azure-dns.org [204.14.183.2] (2ms):

ns4-02.azure-dns.info [208.84.5.2] (1ms):

6. Speed

Result: During the checks in the previous steps, multiple DNS requests were executed to the name servers responsible for the domain name. Average response time of the name servers is 5.98ms.
Recommendation: The name servers have good response time.

Previous reports for openai.com: 2026-05-19 07:44:08
Blog | Cloud DNS
Sponsored by ClouDNS