DNS audit for top10.com.br created on 2026-07-28 03:56:30
1. Name servers
Name servers listed at the parent server e.dns.br:
ns31.cloudns.netns33.cloudns.net
pns31.cloudns.net
pns32.cloudns.net
pns33.cloudns.net
Result: 5 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 top10.com.br.
2. NS records
NS records returned by each name server configured for the domain name
| San Francisco, US | Sydney, AU | Johannesburg, ZA | Singapore |
|---|---|---|---|
|
ns31.cloudns.net [109.201.133.111] (139ms):
ns33.cloudns.net [54.36.26.145] (141ms):
pns31.cloudns.net [185.136.96.66] (1ms):
pns32.cloudns.net [185.136.97.66] (1ms):
pns33.cloudns.net [185.136.98.66] (1ms): |
ns31.cloudns.net [109.201.133.111] (time out 2000ms) ns33.cloudns.net [54.36.26.145] (time out 2000ms)
pns31.cloudns.net [185.136.96.66] (1ms):
pns32.cloudns.net [185.136.97.66] (135ms):
pns33.cloudns.net [185.136.98.66] (1ms): |
ns31.cloudns.net [109.201.133.111] (time out 2000ms) ns33.cloudns.net [54.36.26.145] (time out 2000ms) pns31.cloudns.net [185.136.96.66] (time out 2000ms) pns32.cloudns.net [185.136.97.66] (time out 2000ms) pns33.cloudns.net [185.136.98.66] (time out 2000ms) |
ns31.cloudns.net [109.201.133.111] (157ms): ns32.cloudns.net [209.58.140.85] (time out 2000ms) ns33.cloudns.net [54.36.26.145] (time out 2000ms)
pns31.cloudns.net [185.136.96.66] (3ms):
pns32.cloudns.net [185.136.97.66] (0ms):
pns33.cloudns.net [185.136.98.66] (0ms): |
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 |
|---|
|
ns31.cloudns.net [109.201.133.111] (140ms):
ns33.cloudns.net [54.36.26.145] (143ms):
pns31.cloudns.net [185.136.96.66] (1ms):
pns32.cloudns.net [185.136.97.66] (1ms):
pns33.cloudns.net [185.136.98.66] (1ms): |
| Sydney, AU |
|---|
|
ns31.cloudns.net [109.201.133.111] (time out 2000ms) ns33.cloudns.net [54.36.26.145] (time out 2000ms)
pns31.cloudns.net [185.136.96.66] (1ms):
pns32.cloudns.net [185.136.97.66] (135ms):
pns33.cloudns.net [185.136.98.66] (0ms): |
| Johannesburg, ZA |
|---|
|
ns31.cloudns.net [109.201.133.111] (time out 2000ms)
ns33.cloudns.net [54.36.26.145] (160ms): pns31.cloudns.net [185.136.96.66] (time out 2000ms) pns32.cloudns.net [185.136.97.66] (time out 2000ms) pns33.cloudns.net [185.136.98.66] (time out 2000ms) |
| Singapore |
|---|
|
ns31.cloudns.net [109.201.133.111] (time out 2000ms) ns32.cloudns.net [209.58.140.85] (time out 2000ms) ns33.cloudns.net [54.36.26.145] (time out 2000ms)
pns31.cloudns.net [185.136.96.66] (6ms):
pns32.cloudns.net [185.136.97.66] (1ms):
pns33.cloudns.net [185.136.98.66] (3ms): |
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 top10.com.br
Shows how the name servers respond to requests for top10.com.br
| San Francisco, US | Sydney, AU | Johannesburg, ZA | Singapore |
|---|---|---|---|
|
ns31.cloudns.net [109.201.133.111] (135ms):
ns33.cloudns.net [54.36.26.145] (143ms):
pns31.cloudns.net [185.136.96.66] (1ms):
pns32.cloudns.net [185.136.97.66] (1ms):
pns33.cloudns.net [185.136.98.66] (1ms): |
ns31.cloudns.net [109.201.133.111] (time out 2000ms)
ns33.cloudns.net [54.36.26.145] (265ms):
pns31.cloudns.net [185.136.96.66] (1ms):
pns32.cloudns.net [185.136.97.66] (135ms):
pns33.cloudns.net [185.136.98.66] (1ms): |
ns31.cloudns.net [109.201.133.111] (164ms): ns33.cloudns.net [54.36.26.145] (time out 2000ms) pns31.cloudns.net [185.136.96.66] (time out 2000ms) pns32.cloudns.net [185.136.97.66] (time out 2000ms)
pns33.cloudns.net [185.136.98.66] (4ms): |
ns31.cloudns.net [109.201.133.111] (time out 2000ms) ns32.cloudns.net [209.58.140.85] (time out 2000ms) ns33.cloudns.net [54.36.26.145] (time out 2000ms)
pns31.cloudns.net [185.136.96.66] (0ms):
pns32.cloudns.net [185.136.97.66] (1ms):
pns33.cloudns.net [185.136.98.66] (1ms): |
5. A record distribution by location for www.top10.com.br
Shows how the name servers respond to requests for www.top10.com.br
| San Francisco, US | Sydney, AU | Johannesburg, ZA | Singapore |
|---|---|---|---|
|
ns31.cloudns.net [109.201.133.111] (135ms):
ns33.cloudns.net [54.36.26.145] (144ms):
pns31.cloudns.net [185.136.96.66] (1ms):
pns32.cloudns.net [185.136.97.66] (1ms):
pns33.cloudns.net [185.136.98.66] (1ms): |
ns31.cloudns.net [109.201.133.111] (time out 2000ms)
ns33.cloudns.net [54.36.26.145] (326ms):
pns31.cloudns.net [185.136.96.66] (0ms):
pns32.cloudns.net [185.136.97.66] (135ms):
pns33.cloudns.net [185.136.98.66] (0ms): |
ns31.cloudns.net [109.201.133.111] (164ms): ns33.cloudns.net [54.36.26.145] (time out 2000ms) pns31.cloudns.net [185.136.96.66] (time out 2000ms) pns32.cloudns.net [185.136.97.66] (time out 2000ms)
pns33.cloudns.net [185.136.98.66] (0ms): |
ns31.cloudns.net [109.201.133.111] (time out 2000ms) ns32.cloudns.net [209.58.140.85] (time out 2000ms) ns33.cloudns.net [54.36.26.145] (time out 2000ms)
pns31.cloudns.net [185.136.96.66] (0ms):
pns32.cloudns.net [185.136.97.66] (1ms): pns33.cloudns.net [185.136.98.66] (time out 2000ms) |
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 796.17ms.
Recommendation: The name servers have good response time.
Previous reports for top10.com.br: 2019-12-03 16:44:42
Newer reports for top10.com.br: 2026-07-28 03:57:45