DNS audit for apexrouter.com created on 2026-05-05 19:51:13

PDF

1. Name servers

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

ns1dhl.name.com
ns2ckr.name.com
ns3dgj.name.com
ns4cpw.name.com

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 apexrouter.com.

2. NS records

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

Frankfurt, DE San Francisco, US Sydney, AU Johannesburg, ZA Singapore

ns1dhl.name.com [163.114.216.17] (1ms):
ns1dhl.name.com
ns2ckr.name.com
ns3dgj.name.com
ns4cpw.name.com

ns2ckr.name.com [163.114.216.49] (1ms):
ns1dhl.name.com
ns2ckr.name.com
ns3dgj.name.com
ns4cpw.name.com

ns3dgj.name.com [163.114.217.17] (0ms):
ns1dhl.name.com
ns2ckr.name.com
ns3dgj.name.com
ns4cpw.name.com

ns4cpw.name.com [163.114.217.49] (1ms):
ns1dhl.name.com
ns2ckr.name.com
ns3dgj.name.com
ns4cpw.name.com

ns1dhl.name.com [163.114.216.17] (3ms):
ns1dhl.name.com
ns2ckr.name.com
ns3dgj.name.com
ns4cpw.name.com

ns2ckr.name.com [163.114.216.49] (1ms):
ns1dhl.name.com
ns2ckr.name.com
ns3dgj.name.com
ns4cpw.name.com

ns3dgj.name.com [163.114.217.17] (2ms):
ns1dhl.name.com
ns2ckr.name.com
ns3dgj.name.com
ns4cpw.name.com

ns4cpw.name.com [163.114.217.49] (1ms):
ns1dhl.name.com
ns2ckr.name.com
ns3dgj.name.com
ns4cpw.name.com

ns1dhl.name.com [163.114.216.17] (1ms):
ns1dhl.name.com
ns2ckr.name.com
ns3dgj.name.com
ns4cpw.name.com

ns2ckr.name.com [163.114.216.49] (1ms):
ns1dhl.name.com
ns2ckr.name.com
ns3dgj.name.com
ns4cpw.name.com

ns3dgj.name.com [163.114.217.17] (0ms):
ns1dhl.name.com
ns2ckr.name.com
ns3dgj.name.com
ns4cpw.name.com

ns4cpw.name.com [163.114.217.49] (0ms):
ns1dhl.name.com
ns2ckr.name.com
ns3dgj.name.com
ns4cpw.name.com

ns1dhl.name.com [163.114.216.17] (4ms):
ns1dhl.name.com
ns2ckr.name.com
ns3dgj.name.com
ns4cpw.name.com

ns2ckr.name.com [163.114.216.49] (0ms):
ns1dhl.name.com
ns2ckr.name.com
ns3dgj.name.com
ns4cpw.name.com

ns3dgj.name.com [163.114.217.17] (0ms):
ns1dhl.name.com
ns2ckr.name.com
ns3dgj.name.com
ns4cpw.name.com

ns4cpw.name.com [163.114.217.49] (4ms):
ns1dhl.name.com
ns2ckr.name.com
ns3dgj.name.com
ns4cpw.name.com

ns1dhl.name.com [163.114.216.17] (144ms):
ns1dhl.name.com
ns2ckr.name.com
ns3dgj.name.com
ns4cpw.name.com

ns2ckr.name.com [163.114.216.49] (138ms):
ns1dhl.name.com
ns2ckr.name.com
ns3dgj.name.com
ns4cpw.name.com

ns3dgj.name.com [163.114.217.17] (0ms):
ns1dhl.name.com
ns2ckr.name.com
ns3dgj.name.com
ns4cpw.name.com

ns4cpw.name.com [163.114.217.49] (1ms):
ns1dhl.name.com
ns2ckr.name.com
ns3dgj.name.com
ns4cpw.name.com

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

Frankfurt, DE

ns1dhl.name.com [163.114.216.17] (1ms):
ns1.name.com. hostmaster.nsone.net. 1749408158 43200 7200 1209600 3600

ns2ckr.name.com [163.114.216.49] (1ms):
ns1.name.com. hostmaster.nsone.net. 1749408158 43200 7200 1209600 3600

ns3dgj.name.com [163.114.217.17] (1ms):
ns1.name.com. hostmaster.nsone.net. 1749408158 43200 7200 1209600 3600

ns4cpw.name.com [163.114.217.49] (0ms):
ns1.name.com. hostmaster.nsone.net. 1749408158 43200 7200 1209600 3600

San Francisco, US

ns1dhl.name.com [163.114.216.17] (1ms):
ns1.name.com. hostmaster.nsone.net. 1749408158 43200 7200 1209600 3600

ns2ckr.name.com [163.114.216.49] (1ms):
ns1.name.com. hostmaster.nsone.net. 1749408158 43200 7200 1209600 3600

ns3dgj.name.com [163.114.217.17] (1ms):
ns1.name.com. hostmaster.nsone.net. 1749408158 43200 7200 1209600 3600

ns4cpw.name.com [163.114.217.49] (1ms):
ns1.name.com. hostmaster.nsone.net. 1749408158 43200 7200 1209600 3600

Sydney, AU

ns1dhl.name.com [163.114.216.17] (1ms):
ns1.name.com. hostmaster.nsone.net. 1749408158 43200 7200 1209600 3600

ns2ckr.name.com [163.114.216.49] (0ms):
ns1.name.com. hostmaster.nsone.net. 1749408158 43200 7200 1209600 3600

ns3dgj.name.com [163.114.217.17] (0ms):
ns1.name.com. hostmaster.nsone.net. 1749408158 43200 7200 1209600 3600

ns4cpw.name.com [163.114.217.49] (0ms):
ns1.name.com. hostmaster.nsone.net. 1749408158 43200 7200 1209600 3600

Johannesburg, ZA

ns1dhl.name.com [163.114.216.17] (4ms):
ns1.name.com. hostmaster.nsone.net. 1749408158 43200 7200 1209600 3600

ns2ckr.name.com [163.114.216.49] (0ms):
ns1.name.com. hostmaster.nsone.net. 1749408158 43200 7200 1209600 3600

ns3dgj.name.com [163.114.217.17] (0ms):
ns1.name.com. hostmaster.nsone.net. 1749408158 43200 7200 1209600 3600

ns4cpw.name.com [163.114.217.49] (4ms):
ns1.name.com. hostmaster.nsone.net. 1749408158 43200 7200 1209600 3600

Singapore

ns1dhl.name.com [163.114.216.17] (137ms):
ns1.name.com. hostmaster.nsone.net. 1749408158 43200 7200 1209600 3600

ns2ckr.name.com [163.114.216.49] (137ms):
ns1.name.com. hostmaster.nsone.net. 1749408158 43200 7200 1209600 3600

ns3dgj.name.com [163.114.217.17] (1ms):
ns1.name.com. hostmaster.nsone.net. 1749408158 43200 7200 1209600 3600

ns4cpw.name.com [163.114.217.49] (1ms):
ns1.name.com. hostmaster.nsone.net. 1749408158 43200 7200 1209600 3600

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 apexrouter.com

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

Frankfurt, DE San Francisco, US Sydney, AU Johannesburg, ZA Singapore

ns1dhl.name.com [163.114.216.17] (1ms):
91.195.240.94

ns2ckr.name.com [163.114.216.49] (1ms):
91.195.240.94

ns3dgj.name.com [163.114.217.17] (1ms):
91.195.240.94

ns4cpw.name.com [163.114.217.49] (1ms):
91.195.240.94

ns1dhl.name.com [163.114.216.17] (1ms):
91.195.240.94

ns2ckr.name.com [163.114.216.49] (1ms):
91.195.240.94

ns3dgj.name.com [163.114.217.17] (1ms):
91.195.240.94

ns4cpw.name.com [163.114.217.49] (1ms):
91.195.240.94

ns1dhl.name.com [163.114.216.17] (0ms):
91.195.240.94

ns2ckr.name.com [163.114.216.49] (0ms):
91.195.240.94

ns3dgj.name.com [163.114.217.17] (0ms):
91.195.240.94

ns4cpw.name.com [163.114.217.49] (0ms):
91.195.240.94

ns1dhl.name.com [163.114.216.17] (0ms):
91.195.240.94

ns2ckr.name.com [163.114.216.49] (4ms):
91.195.240.94

ns3dgj.name.com [163.114.217.17] (0ms):
91.195.240.94

ns4cpw.name.com [163.114.217.49] (0ms):
91.195.240.94

ns1dhl.name.com [163.114.216.17] (138ms):
91.195.240.94

ns2ckr.name.com [163.114.216.49] (139ms):
91.195.240.94

ns3dgj.name.com [163.114.217.17] (1ms):
91.195.240.94

ns4cpw.name.com [163.114.217.49] (0ms):
91.195.240.94

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

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

Frankfurt, DE San Francisco, US Sydney, AU Johannesburg, ZA Singapore

ns1dhl.name.com [163.114.216.17] (1ms):
91.195.240.94

ns2ckr.name.com [163.114.216.49] (1ms):
91.195.240.94

ns3dgj.name.com [163.114.217.17] (0ms):
91.195.240.94

ns4cpw.name.com [163.114.217.49] (0ms):
91.195.240.94

ns1dhl.name.com [163.114.216.17] (1ms):
91.195.240.94

ns2ckr.name.com [163.114.216.49] (1ms):
91.195.240.94

ns3dgj.name.com [163.114.217.17] (1ms):
91.195.240.94

ns4cpw.name.com [163.114.217.49] (1ms):
91.195.240.94

ns1dhl.name.com [163.114.216.17] (0ms):
91.195.240.94

ns2ckr.name.com [163.114.216.49] (1ms):
91.195.240.94

ns3dgj.name.com [163.114.217.17] (0ms):
91.195.240.94

ns4cpw.name.com [163.114.217.49] (2ms):
91.195.240.94

ns1dhl.name.com [163.114.216.17] (0ms):
91.195.240.94

ns2ckr.name.com [163.114.216.49] (0ms):
91.195.240.94

ns3dgj.name.com [163.114.217.17] (0ms):
91.195.240.94

ns4cpw.name.com [163.114.217.49] (0ms):
91.195.240.94

ns1dhl.name.com [163.114.216.17] (140ms):
91.195.240.94

ns2ckr.name.com [163.114.216.49] (139ms):
91.195.240.94

ns3dgj.name.com [163.114.217.17] (0ms):
91.195.240.94

ns4cpw.name.com [163.114.217.49] (3ms):
91.195.240.94

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

Blog | Cloud DNS
Sponsored by ClouDNS