DNS audit for shinkao.com.my created on 2026-10-15 15:48:11

PDF

1. Name servers

Name servers listed at the parent server g.nic.my:

pns1.cloud.sg
pns2.cloud.sg
pns3.cloud.sg
pns4.cloud.sg

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 shinkao.com.my.

2. NS records

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

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

pns1.cloud.sg [185.136.96.96] (4ms):
pns1.cloud.sg
pns2.cloud.sg
pns3.cloud.sg
pns4.cloud.sg

pns2.cloud.sg [185.136.97.96] (4ms):
pns1.cloud.sg
pns2.cloud.sg
pns3.cloud.sg
pns4.cloud.sg

pns3.cloud.sg [185.136.98.96] (0ms):
pns1.cloud.sg
pns2.cloud.sg
pns3.cloud.sg
pns4.cloud.sg

pns4.cloud.sg [185.136.99.96] (0ms):
pns1.cloud.sg
pns2.cloud.sg
pns3.cloud.sg
pns4.cloud.sg

pns1.cloud.sg [185.136.96.96] (0ms):
pns1.cloud.sg
pns2.cloud.sg
pns3.cloud.sg
pns4.cloud.sg

pns2.cloud.sg [185.136.97.96] (112ms):
pns1.cloud.sg
pns2.cloud.sg
pns3.cloud.sg
pns4.cloud.sg

pns3.cloud.sg [185.136.98.96] (0ms):
pns1.cloud.sg
pns2.cloud.sg
pns3.cloud.sg
pns4.cloud.sg

pns4.cloud.sg [185.136.99.96] (4ms):
pns1.cloud.sg
pns2.cloud.sg
pns3.cloud.sg
pns4.cloud.sg

pns1.cloud.sg [185.136.96.96] (8ms):
pns1.cloud.sg
pns2.cloud.sg
pns3.cloud.sg
pns4.cloud.sg

pns2.cloud.sg [185.136.97.96] (0ms):
pns1.cloud.sg
pns2.cloud.sg
pns3.cloud.sg
pns4.cloud.sg

pns3.cloud.sg [185.136.98.96] (0ms):
pns1.cloud.sg
pns2.cloud.sg
pns3.cloud.sg
pns4.cloud.sg

pns4.cloud.sg [185.136.99.96] (0ms):
pns1.cloud.sg
pns2.cloud.sg
pns3.cloud.sg
pns4.cloud.sg

pns1.cloud.sg [185.136.96.96] (0ms):
pns1.cloud.sg
pns2.cloud.sg
pns3.cloud.sg
pns4.cloud.sg

pns2.cloud.sg [185.136.97.96] (0ms):
pns1.cloud.sg
pns2.cloud.sg
pns3.cloud.sg
pns4.cloud.sg

pns3.cloud.sg [185.136.98.96] (0ms):
pns1.cloud.sg
pns2.cloud.sg
pns3.cloud.sg
pns4.cloud.sg

pns4.cloud.sg [185.136.99.96] (0ms):
pns1.cloud.sg
pns2.cloud.sg
pns3.cloud.sg
pns4.cloud.sg

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

pns1.cloud.sg [185.136.96.96] (4ms):
pns1.cloud.sg. dnsadmin.cloud.sg. 2026101510 7200 1800 1209600 3600

pns2.cloud.sg [185.136.97.96] (0ms):
pns1.cloud.sg. dnsadmin.cloud.sg. 2026101510 7200 1800 1209600 3600

pns3.cloud.sg [185.136.98.96] (4ms):
pns1.cloud.sg. dnsadmin.cloud.sg. 2026101510 7200 1800 1209600 3600

pns4.cloud.sg [185.136.99.96] (4ms):
pns1.cloud.sg. dnsadmin.cloud.sg. 2026101510 7200 1800 1209600 3600

Sydney, AU

pns1.cloud.sg [185.136.96.96] (4ms):
pns1.cloud.sg. dnsadmin.cloud.sg. 2026101510 7200 1800 1209600 3600

pns2.cloud.sg [185.136.97.96] (136ms):
pns1.cloud.sg. dnsadmin.cloud.sg. 2026101510 7200 1800 1209600 3600

pns3.cloud.sg [185.136.98.96] (0ms):
pns1.cloud.sg. dnsadmin.cloud.sg. 2026101510 7200 1800 1209600 3600

pns4.cloud.sg [185.136.99.96] (0ms):
pns1.cloud.sg. dnsadmin.cloud.sg. 2026101510 7200 1800 1209600 3600

Johannesburg, ZA

pns1.cloud.sg [185.136.96.96] (0ms):
pns1.cloud.sg. dnsadmin.cloud.sg. 2026101510 7200 1800 1209600 3600

pns2.cloud.sg [185.136.97.96] (8ms):
pns1.cloud.sg. dnsadmin.cloud.sg. 2026101510 7200 1800 1209600 3600

pns3.cloud.sg [185.136.98.96] (0ms):
pns1.cloud.sg. dnsadmin.cloud.sg. 2026101510 7200 1800 1209600 3600

pns4.cloud.sg [185.136.99.96] (8ms):
pns1.cloud.sg. dnsadmin.cloud.sg. 2026101510 7200 1800 1209600 3600

Singapore

pns1.cloud.sg [185.136.96.96] (4ms):
pns1.cloud.sg. dnsadmin.cloud.sg. 2026101510 7200 1800 1209600 3600

pns2.cloud.sg [185.136.97.96] (4ms):
pns1.cloud.sg. dnsadmin.cloud.sg. 2026101510 7200 1800 1209600 3600

pns3.cloud.sg [185.136.98.96] (0ms):
pns1.cloud.sg. dnsadmin.cloud.sg. 2026101510 7200 1800 1209600 3600

pns4.cloud.sg [185.136.99.96] (0ms):
pns1.cloud.sg. dnsadmin.cloud.sg. 2026101510 7200 1800 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 shinkao.com.my

Shows how the name servers respond to requests for shinkao.com.my

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

pns1.cloud.sg [185.136.96.96] (4ms):

pns2.cloud.sg [185.136.97.96] (0ms):

pns3.cloud.sg [185.136.98.96] (0ms):

pns4.cloud.sg [185.136.99.96] (4ms):

pns1.cloud.sg [185.136.96.96] (0ms):

pns2.cloud.sg [185.136.97.96] (116ms):

pns3.cloud.sg [185.136.98.96] (0ms):

pns4.cloud.sg [185.136.99.96] (0ms):

pns1.cloud.sg [185.136.96.96] (0ms):

pns2.cloud.sg [185.136.97.96] (4ms):

pns3.cloud.sg [185.136.98.96] (0ms):

pns4.cloud.sg [185.136.99.96] (0ms):

pns1.cloud.sg [185.136.96.96] (4ms):

pns2.cloud.sg [185.136.97.96] (0ms):

pns3.cloud.sg [185.136.98.96] (0ms):

pns4.cloud.sg [185.136.99.96] (0ms):

5. A record distribution by location for www.shinkao.com.my

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

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

pns1.cloud.sg [185.136.96.96] (0ms):

pns2.cloud.sg [185.136.97.96] (4ms):

pns3.cloud.sg [185.136.98.96] (0ms):

pns4.cloud.sg [185.136.99.96] (4ms):

pns1.cloud.sg [185.136.96.96] (0ms):

pns2.cloud.sg [185.136.97.96] (140ms):

pns3.cloud.sg [185.136.98.96] (0ms):

pns4.cloud.sg [185.136.99.96] (0ms):

pns1.cloud.sg [185.136.96.96] (0ms):

pns2.cloud.sg [185.136.97.96] (0ms):

pns3.cloud.sg [185.136.98.96] (0ms):

pns4.cloud.sg [185.136.99.96] (0ms):

pns1.cloud.sg [185.136.96.96] (0ms):

pns2.cloud.sg [185.136.97.96] (4ms):

pns3.cloud.sg [185.136.98.96] (4ms):

pns4.cloud.sg [185.136.99.96] (0ms):

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

Blog | Cloud DNS
Sponsored by ClouDNS