DNS audit for pj.top created on 2026-09-28 16:43:52

PDF

1. Name servers

Name servers listed at the parent server c.zdnscloud.com:

ns1.exp.4cun.com
ns2.exp.4cun.com

Result: 2 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 pj.top.

2. NS records

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

San Francisco, US Johannesburg, ZA Singapore

ns1.exp.4cun.com [43.165.183.246] (112ms):

ns2.exp.4cun.com [43.165.183.246] (116ms):

ns1.exp.4cun.com [43.165.183.246] (404ms):

ns2.exp.4cun.com [43.165.183.246] (376ms):

ns1.exp.4cun.com [43.165.183.246] (72ms):

ns2.exp.4cun.com [43.165.183.246] (68ms):

Result: The NS records returned by the DNS servers are not the same as the name servers set at the parent server.
Recommendation: Check the synchronization between the DNS servers. Returned NS records must be exactly the same as these returned by the parent server.

3. SOA record

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

San Francisco, US

ns1.exp.4cun.com [43.165.183.246] (112ms):
. root. 201112052 10800 900 604800 86400

ns2.exp.4cun.com [43.165.183.246] (112ms):
. root. 201112052 10800 900 604800 86400

Johannesburg, ZA

ns1.exp.4cun.com [43.165.183.246] (404ms):
. root. 201112052 10800 900 604800 86400

ns2.exp.4cun.com [43.165.183.246] (376ms):
. root. 201112052 10800 900 604800 86400

Singapore

ns1.exp.4cun.com [43.165.183.246] (72ms):
. root. 201112052 10800 900 604800 86400

ns2.exp.4cun.com [43.165.183.246] (72ms):
. root. 201112052 10800 900 604800 86400

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 pj.top

Shows how the name servers respond to requests for pj.top

San Francisco, US Johannesburg, ZA Singapore

ns1.exp.4cun.com [43.165.183.246] (108ms):
116.206.178.124

ns2.exp.4cun.com [43.165.183.246] (112ms):
116.206.178.124

ns1.exp.4cun.com [43.165.183.246] (404ms):
116.206.178.124

ns2.exp.4cun.com [43.165.183.246] (408ms):
116.206.178.124

ns1.exp.4cun.com [43.165.183.246] (96ms):
116.206.178.124

ns2.exp.4cun.com [43.165.183.246] (72ms):
116.206.178.124

5. A record distribution by location for www.pj.top

Shows how the name servers respond to requests for www.pj.top

San Francisco, US Johannesburg, ZA Singapore

ns1.exp.4cun.com [43.165.183.246] (112ms):
116.206.178.124

ns2.exp.4cun.com [43.165.183.246] (108ms):
116.206.178.124

ns1.exp.4cun.com [43.165.183.246] (400ms):
116.206.178.124

ns2.exp.4cun.com [43.165.183.246] (412ms):
116.206.178.124

ns1.exp.4cun.com [43.165.183.246] (72ms):
116.206.178.124

ns2.exp.4cun.com [43.165.183.246] (72ms):
116.206.178.124

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 195.67ms.
Recommendation: The name servers respond slow. Try moving to an Anycast DNS service in order to speed up the resolution of the domain name and first page load of the web site.

Blog | Cloud DNS
Sponsored by ClouDNS