DNS audit for famkooijman.net created on 2026-07-19 20:13:33
1. Name servers
Name servers listed at the parent server h.gtld-servers.net:
ns31.domainmonger.comns32.domainmonger.com
ns33.domainmonger.com
ns34.domainmonger.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 famkooijman.net.
2. NS records
NS records returned by each name server configured for the domain name
| San Francisco, US | Sydney, AU | Johannesburg, ZA | Singapore |
|---|---|---|---|
|
ns31.domainmonger.com [185.136.96.100] (2ms):
ns32.domainmonger.com [185.136.97.100] (1ms):
ns33.domainmonger.com [185.136.98.100] (1ms):
ns34.domainmonger.com [185.136.99.100] (1ms): |
ns31.domainmonger.com [185.136.96.100] (0ms):
ns32.domainmonger.com [185.136.97.100] (133ms):
ns33.domainmonger.com [185.136.98.100] (0ms):
ns34.domainmonger.com [185.136.99.100] (0ms): |
ns31.domainmonger.com [185.136.96.100] (0ms):
ns32.domainmonger.com [185.136.97.100] (0ms):
ns33.domainmonger.com [185.136.98.100] (4ms):
ns34.domainmonger.com [185.136.99.100] (0ms): |
ns31.domainmonger.com [185.136.96.100] (2ms):
ns32.domainmonger.com [185.136.97.100] (1ms):
ns33.domainmonger.com [185.136.98.100] (1ms):
ns34.domainmonger.com [185.136.99.100] (1ms): |
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 |
|---|
|
ns31.domainmonger.com [185.136.96.100] (1ms):
ns32.domainmonger.com [185.136.97.100] (1ms):
ns33.domainmonger.com [185.136.98.100] (1ms):
ns34.domainmonger.com [185.136.99.100] (1ms): |
| Sydney, AU |
|---|
|
ns31.domainmonger.com [185.136.96.100] (0ms):
ns32.domainmonger.com [185.136.97.100] (135ms):
ns33.domainmonger.com [185.136.98.100] (0ms):
ns34.domainmonger.com [185.136.99.100] (1ms): |
| Johannesburg, ZA |
|---|
|
ns31.domainmonger.com [185.136.96.100] (4ms):
ns32.domainmonger.com [185.136.97.100] (0ms):
ns33.domainmonger.com [185.136.98.100] (0ms):
ns34.domainmonger.com [185.136.99.100] (4ms): |
| Singapore |
|---|
|
ns31.domainmonger.com [185.136.96.100] (1ms):
ns32.domainmonger.com [185.136.97.100] (1ms):
ns33.domainmonger.com [185.136.98.100] (1ms):
ns34.domainmonger.com [185.136.99.100] (1ms): |
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 famkooijman.net
Shows how the name servers respond to requests for famkooijman.net
| San Francisco, US | Sydney, AU | Johannesburg, ZA | Singapore |
|---|---|---|---|
|
ns31.domainmonger.com [185.136.96.100] (1ms):
ns32.domainmonger.com [185.136.97.100] (1ms):
ns33.domainmonger.com [185.136.98.100] (1ms):
ns34.domainmonger.com [185.136.99.100] (1ms): |
ns31.domainmonger.com [185.136.96.100] (0ms):
ns32.domainmonger.com [185.136.97.100] (92ms):
ns33.domainmonger.com [185.136.98.100] (0ms):
ns34.domainmonger.com [185.136.99.100] (0ms): |
ns31.domainmonger.com [185.136.96.100] (0ms):
ns32.domainmonger.com [185.136.97.100] (0ms):
ns33.domainmonger.com [185.136.98.100] (4ms):
ns34.domainmonger.com [185.136.99.100] (0ms): |
ns31.domainmonger.com [185.136.96.100] (1ms):
ns32.domainmonger.com [185.136.97.100] (1ms):
ns33.domainmonger.com [185.136.98.100] (1ms):
ns34.domainmonger.com [185.136.99.100] (1ms): |
5. A record distribution by location for www.famkooijman.net
Shows how the name servers respond to requests for www.famkooijman.net
| San Francisco, US | Sydney, AU | Johannesburg, ZA | Singapore |
|---|---|---|---|
|
ns31.domainmonger.com [185.136.96.100] (1ms):
ns32.domainmonger.com [185.136.97.100] (1ms):
ns33.domainmonger.com [185.136.98.100] (1ms):
ns34.domainmonger.com [185.136.99.100] (1ms): |
ns31.domainmonger.com [185.136.96.100] (1ms):
ns32.domainmonger.com [185.136.97.100] (133ms):
ns33.domainmonger.com [185.136.98.100] (0ms):
ns34.domainmonger.com [185.136.99.100] (0ms): |
ns31.domainmonger.com [185.136.96.100] (0ms):
ns32.domainmonger.com [185.136.97.100] (0ms):
ns33.domainmonger.com [185.136.98.100] (4ms):
ns34.domainmonger.com [185.136.99.100] (4ms): |
ns31.domainmonger.com [185.136.96.100] (2ms):
ns32.domainmonger.com [185.136.97.100] (1ms):
ns33.domainmonger.com [185.136.98.100] (1ms):
ns34.domainmonger.com [185.136.99.100] (2ms): |
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 7.92ms.
Recommendation: The name servers have good response time.