DNS audit for gdcmanaged.com created on 2026-06-04 17:16:03

1. Name servers

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

ns1.companydns.net
ns2.companydns.net
ns3.companydns.net
ns4.companydns.net

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 gdcmanaged.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.companydns.net [185.136.96.111] (2ms):
ns1.companydns.net
ns2.companydns.net
ns3.companydns.net
ns4.companydns.net

ns2.companydns.net [185.136.97.111] (1ms):
ns1.companydns.net
ns2.companydns.net
ns3.companydns.net
ns4.companydns.net

ns3.companydns.net [185.136.98.111] (1ms):
ns1.companydns.net
ns2.companydns.net
ns3.companydns.net
ns4.companydns.net

ns4.companydns.net [185.136.99.111] (1ms):
ns1.companydns.net
ns2.companydns.net
ns3.companydns.net
ns4.companydns.net

ns1.companydns.net [185.136.96.111] (1ms):
ns1.companydns.net
ns2.companydns.net
ns3.companydns.net
ns4.companydns.net

ns2.companydns.net [185.136.97.111] (92ms):
ns1.companydns.net
ns2.companydns.net
ns3.companydns.net
ns4.companydns.net

ns3.companydns.net [185.136.98.111] (0ms):
ns1.companydns.net
ns2.companydns.net
ns3.companydns.net
ns4.companydns.net

ns4.companydns.net [185.136.99.111] (0ms):
ns1.companydns.net
ns2.companydns.net
ns3.companydns.net
ns4.companydns.net

ns1.companydns.net [185.136.96.111] (0ms):
ns1.companydns.net
ns2.companydns.net
ns3.companydns.net
ns4.companydns.net

ns2.companydns.net [185.136.97.111] (0ms):
ns1.companydns.net
ns2.companydns.net
ns3.companydns.net
ns4.companydns.net

ns3.companydns.net [185.136.98.111] (0ms):
ns1.companydns.net
ns2.companydns.net
ns3.companydns.net
ns4.companydns.net

ns4.companydns.net [185.136.99.111] (4ms):
ns1.companydns.net
ns2.companydns.net
ns3.companydns.net
ns4.companydns.net

ns1.companydns.net [185.136.96.111] (0ms):
ns1.companydns.net
ns2.companydns.net
ns3.companydns.net
ns4.companydns.net

ns2.companydns.net [185.136.97.111] (1ms):
ns1.companydns.net
ns2.companydns.net
ns3.companydns.net
ns4.companydns.net

ns3.companydns.net [185.136.98.111] (1ms):
ns1.companydns.net
ns2.companydns.net
ns3.companydns.net
ns4.companydns.net

ns4.companydns.net [185.136.99.111] (1ms):
ns1.companydns.net
ns2.companydns.net
ns3.companydns.net
ns4.companydns.net

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.companydns.net [185.136.96.111] (1ms):
ns1.companydns.net. hostmaster.companydns.net. 2026060406 1200 180 1209600 3600

ns2.companydns.net [185.136.97.111] (1ms):
ns1.companydns.net. hostmaster.companydns.net. 2026060406 1200 180 1209600 3600

ns3.companydns.net [185.136.98.111] (1ms):
ns1.companydns.net. hostmaster.companydns.net. 2026060406 1200 180 1209600 3600

ns4.companydns.net [185.136.99.111] (1ms):
ns1.companydns.net. hostmaster.companydns.net. 2026060406 1200 180 1209600 3600

Sydney, AU

ns1.companydns.net [185.136.96.111] (0ms):
ns1.companydns.net. hostmaster.companydns.net. 2026060406 1200 180 1209600 3600

ns2.companydns.net [185.136.97.111] (135ms):
ns1.companydns.net. hostmaster.companydns.net. 2026060406 1200 180 1209600 3600

ns3.companydns.net [185.136.98.111] (0ms):
ns1.companydns.net. hostmaster.companydns.net. 2026060406 1200 180 1209600 3600

ns4.companydns.net [185.136.99.111] (1ms):
ns1.companydns.net. hostmaster.companydns.net. 2026060406 1200 180 1209600 3600

Johannesburg, ZA

ns1.companydns.net [185.136.96.111] (4ms):
ns1.companydns.net. hostmaster.companydns.net. 2026060406 1200 180 1209600 3600

ns2.companydns.net [185.136.97.111] (0ms):
ns1.companydns.net. hostmaster.companydns.net. 2026060406 1200 180 1209600 3600

ns3.companydns.net [185.136.98.111] (0ms):
ns1.companydns.net. hostmaster.companydns.net. 2026060406 1200 180 1209600 3600

ns4.companydns.net [185.136.99.111] (4ms):
ns1.companydns.net. hostmaster.companydns.net. 2026060406 1200 180 1209600 3600

Singapore

ns1.companydns.net [185.136.96.111] (2ms):
ns1.companydns.net. hostmaster.companydns.net. 2026060405 1200 180 1209600 3600

ns2.companydns.net [185.136.97.111] (1ms):
ns1.companydns.net. hostmaster.companydns.net. 2026060406 1200 180 1209600 3600

ns3.companydns.net [185.136.98.111] (1ms):
ns1.companydns.net. hostmaster.companydns.net. 2026060406 1200 180 1209600 3600

ns4.companydns.net [185.136.99.111] (1ms):
ns1.companydns.net. hostmaster.companydns.net. 2026060406 1200 180 1209600 3600

Result: The SOA record returned by the name servers is not the same on all of them.
Recommendation: Check the synchronization between the DNS servers. Returned SOA record must be exactly the same on all DNS servers.

4. A record distribution by location for gdcmanaged.com

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

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

ns1.companydns.net [185.136.96.111] (1ms):
213.109.149.29

ns2.companydns.net [185.136.97.111] (1ms):
213.109.149.29

ns3.companydns.net [185.136.98.111] (1ms):
213.109.149.29

ns4.companydns.net [185.136.99.111] (1ms):
213.109.149.29

ns1.companydns.net [185.136.96.111] (1ms):
213.109.149.29

ns2.companydns.net [185.136.97.111] (135ms):
213.109.149.29

ns3.companydns.net [185.136.98.111] (1ms):
213.109.149.29

ns4.companydns.net [185.136.99.111] (0ms):
213.109.149.29

ns1.companydns.net [185.136.96.111] (0ms):
213.109.149.29

ns2.companydns.net [185.136.97.111] (0ms):
213.109.149.29

ns3.companydns.net [185.136.98.111] (0ms):
213.109.149.29

ns4.companydns.net [185.136.99.111] (0ms):
213.109.149.29

ns1.companydns.net [185.136.96.111] (1ms):
213.109.149.29

ns2.companydns.net [185.136.97.111] (1ms):
213.109.149.29

ns3.companydns.net [185.136.98.111] (1ms):
213.109.149.29

ns4.companydns.net [185.136.99.111] (1ms):
213.109.149.29

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

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

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

ns1.companydns.net [185.136.96.111] (1ms):
213.109.149.29

ns2.companydns.net [185.136.97.111] (1ms):
213.109.149.29

ns3.companydns.net [185.136.98.111] (1ms):
213.109.149.29

ns4.companydns.net [185.136.99.111] (1ms):
213.109.149.29

ns1.companydns.net [185.136.96.111] (0ms):
213.109.149.29

ns2.companydns.net [185.136.97.111] (92ms):
213.109.149.29

ns3.companydns.net [185.136.98.111] (1ms):
213.109.149.29

ns4.companydns.net [185.136.99.111] (1ms):
213.109.149.29

ns1.companydns.net [185.136.96.111] (0ms):
213.109.149.29

ns2.companydns.net [185.136.97.111] (0ms):
213.109.149.29

ns3.companydns.net [185.136.98.111] (4ms):
213.109.149.29

ns4.companydns.net [185.136.99.111] (0ms):
213.109.149.29

ns1.companydns.net [185.136.96.111] (1ms):
213.109.149.29

ns2.companydns.net [185.136.97.111] (2ms):
213.109.149.29

ns3.companydns.net [185.136.98.111] (0ms):
213.109.149.29

ns4.companydns.net [185.136.99.111] (3ms):
213.109.149.29

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 8.56ms.
Recommendation: The name servers have good response time.


Previous reports for gdcmanaged.com: 2026-01-12 04:23:08 , 2024-01-14 04:41:16 , 2019-10-07 16:38:41
Blog | Cloud DNS
Sponsored by ClouDNS