DNS audit for meritbet739.com created on 2026-06-20 21:51:49

1. Name servers

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

dns41.cloudns.net
dns42.cloudns.net
dns43.cloudns.net
dns44.cloudns.net

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

2. NS records

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

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

dns41.cloudns.net [185.136.96.200] (2ms):

dns42.cloudns.net [185.136.97.200] (1ms):

dns43.cloudns.net [185.136.98.200] (1ms):

dns44.cloudns.net [185.136.99.200] (1ms):

dns41.cloudns.net [185.136.96.200] (0ms):

dns42.cloudns.net [185.136.97.200] (135ms):
dns41.cloudns.net
dns42.cloudns.net
dns43.cloudns.net
dns44.cloudns.net

dns43.cloudns.net [185.136.98.200] (0ms):

dns44.cloudns.net [185.136.99.200] (1ms):

dns41.cloudns.net [185.136.96.200] (0ms):

dns42.cloudns.net [185.136.97.200] (0ms):
dns41.cloudns.net
dns42.cloudns.net
dns43.cloudns.net
dns44.cloudns.net

dns43.cloudns.net [185.136.98.200] (0ms):

dns44.cloudns.net [185.136.99.200] (4ms):

dns41.cloudns.net [185.136.96.200] (1ms):
dns41.cloudns.net
dns42.cloudns.net
dns43.cloudns.net
dns44.cloudns.net

dns42.cloudns.net [185.136.97.200] (1ms):

dns43.cloudns.net [185.136.98.200] (1ms):
dns41.cloudns.net
dns42.cloudns.net
dns43.cloudns.net
dns44.cloudns.net

dns44.cloudns.net [185.136.99.200] (1ms):
dns41.cloudns.net
dns42.cloudns.net
dns43.cloudns.net
dns44.cloudns.net

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

dns41.cloudns.net [185.136.96.200] (1ms):
undefined.localhost. support.localhost. 2020053101 7200 3600 1209600 120

dns42.cloudns.net [185.136.97.200] (1ms):
undefined.localhost. support.localhost. 2020053101 7200 3600 1209600 120

dns43.cloudns.net [185.136.98.200] (1ms):
undefined.localhost. support.localhost. 2020053101 7200 3600 1209600 120

dns44.cloudns.net [185.136.99.200] (1ms):
undefined.localhost. support.localhost. 2020053101 7200 3600 1209600 120

Sydney, AU

dns41.cloudns.net [185.136.96.200] (0ms):
undefined.localhost. support.localhost. 2020053101 7200 3600 1209600 120

dns42.cloudns.net [185.136.97.200] (92ms):
undefined.localhost. support.localhost. 2020053101 7200 3600 1209600 120

dns43.cloudns.net [185.136.98.200] (0ms):
undefined.localhost. support.localhost. 2020053101 7200 3600 1209600 120

dns44.cloudns.net [185.136.99.200] (1ms):
undefined.localhost. support.localhost. 2020053101 7200 3600 1209600 120

Johannesburg, ZA

dns41.cloudns.net [185.136.96.200] (0ms):
undefined.localhost. support.localhost. 2020053101 7200 3600 1209600 120

dns42.cloudns.net [185.136.97.200] (0ms):
dns41.cloudns.net. support.cloudns.net. 2026062023 7200 1800 1209600 3600

dns43.cloudns.net [185.136.98.200] (0ms):
undefined.localhost. support.localhost. 2020053101 7200 3600 1209600 120

dns44.cloudns.net [185.136.99.200] (0ms):
undefined.localhost. support.localhost. 2020053101 7200 3600 1209600 120

Singapore

dns41.cloudns.net [185.136.96.200] (1ms):
dns41.cloudns.net. support.cloudns.net. 2026062023 7200 1800 1209600 3600

dns42.cloudns.net [185.136.97.200] (1ms):
undefined.localhost. support.localhost. 2020053101 7200 3600 1209600 120

dns43.cloudns.net [185.136.98.200] (1ms):
dns41.cloudns.net. support.cloudns.net. 2026062023 7200 1800 1209600 3600

dns44.cloudns.net [185.136.99.200] (1ms):
undefined.localhost. support.localhost. 2020053101 7200 3600 1209600 120

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

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

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

dns41.cloudns.net [185.136.96.200] (1ms):
127.0.0.1

dns42.cloudns.net [185.136.97.200] (1ms):
127.0.0.1

dns43.cloudns.net [185.136.98.200] (1ms):
127.0.0.1

dns44.cloudns.net [185.136.99.200] (1ms):
127.0.0.1

dns41.cloudns.net [185.136.96.200] (0ms):
127.0.0.1

dns42.cloudns.net [185.136.97.200] (135ms):
131.222.213.74

dns43.cloudns.net [185.136.98.200] (0ms):
127.0.0.1

dns44.cloudns.net [185.136.99.200] (1ms):
127.0.0.1

dns41.cloudns.net [185.136.96.200] (0ms):
127.0.0.1

dns42.cloudns.net [185.136.97.200] (0ms):
131.222.213.74

dns43.cloudns.net [185.136.98.200] (0ms):
127.0.0.1

dns44.cloudns.net [185.136.99.200] (4ms):
127.0.0.1

dns41.cloudns.net [185.136.96.200] (1ms):
131.222.213.74

dns42.cloudns.net [185.136.97.200] (2ms):
127.0.0.1

dns43.cloudns.net [185.136.98.200] (1ms):
127.0.0.1

dns44.cloudns.net [185.136.99.200] (1ms):
127.0.0.1

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

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

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

dns41.cloudns.net [185.136.96.200] (1ms):
127.0.0.1

dns42.cloudns.net [185.136.97.200] (1ms):
127.0.0.1

dns43.cloudns.net [185.136.98.200] (1ms):
127.0.0.1

dns44.cloudns.net [185.136.99.200] (1ms):
127.0.0.1

dns41.cloudns.net [185.136.96.200] (0ms):
127.0.0.1

dns42.cloudns.net [185.136.97.200] (135ms):
131.222.213.74

dns43.cloudns.net [185.136.98.200] (0ms):
127.0.0.1

dns44.cloudns.net [185.136.99.200] (1ms):
127.0.0.1

dns41.cloudns.net [185.136.96.200] (0ms):
127.0.0.1

dns42.cloudns.net [185.136.97.200] (4ms):
131.222.213.74

dns43.cloudns.net [185.136.98.200] (0ms):
127.0.0.1

dns44.cloudns.net [185.136.99.200] (4ms):
127.0.0.1

dns41.cloudns.net [185.136.96.200] (1ms):
131.222.213.74

dns42.cloudns.net [185.136.97.200] (1ms):
127.0.0.1

dns43.cloudns.net [185.136.98.200] (1ms):
131.222.213.74

dns44.cloudns.net [185.136.99.200] (1ms):
127.0.0.1

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


Blog | Cloud DNS
Sponsored by ClouDNS