DNS audit for futemax.med created on 2026-10-24 18:03:53

1. Name servers

Name servers listed at the parent server dnsc.nic.med:

ns1.ddos-guard.net
ns2.ddos-guard.net

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 futemax.med.

2. NS records

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

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

ns1.ddos-guard.net [185.129.101.200] (12ms):
ns1.ddos-guard.net
ns2.ddos-guard.net

ns2.ddos-guard.net [185.129.103.200] (8ms):
ns1.ddos-guard.net
ns2.ddos-guard.net

ns1.ddos-guard.net [185.129.101.200] (144ms):
ns1.ddos-guard.net
ns2.ddos-guard.net

ns2.ddos-guard.net [185.129.103.200] (148ms):
ns1.ddos-guard.net
ns2.ddos-guard.net

pns71.cloudns.net [45.83.248.12] (0ms):
pns71.cloudns.net
pns73.cloudns.net

pns73.cloudns.net [45.83.250.12] (0ms):
pns71.cloudns.net
pns73.cloudns.net

pns71.cloudns.net [45.83.248.12] (0ms):
pns71.cloudns.net
pns73.cloudns.net

pns73.cloudns.net [45.83.250.12] (4ms):

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.ddos-guard.net [185.129.101.200] (8ms):
ns1.ddos-guard.net. support.ddos-guard.net. 1791728495 10800 3600 604800 3600

ns2.ddos-guard.net [185.129.103.200] (12ms):
ns1.ddos-guard.net. support.ddos-guard.net. 1791728495 10800 3600 604800 3600

Sydney, AU

ns1.ddos-guard.net [185.129.101.200] (148ms):
ns1.ddos-guard.net. support.ddos-guard.net. 1791728495 10800 3600 604800 3600

ns2.ddos-guard.net [185.129.103.200] (144ms):
ns1.ddos-guard.net. support.ddos-guard.net. 1791728495 10800 3600 604800 3600

Johannesburg, ZA

pns71.cloudns.net [45.83.248.12] (0ms):
pns71.cloudns.net. support.cloudns.net. 2026102405 7200 1800 1209600 3600

pns73.cloudns.net [45.83.250.12] (0ms):
pns71.cloudns.net. support.cloudns.net. 2026102405 7200 1800 1209600 3600

Singapore

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

pns73.cloudns.net [45.83.250.12] (0ms):
pns71.cloudns.net. support.cloudns.net. 2026102405 7200 1800 1209600 3600

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 futemax.med

Shows how the name servers respond to requests for futemax.med

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

ns1.ddos-guard.net [185.129.101.200] (8ms):
186.2.175.234

ns2.ddos-guard.net [185.129.103.200] (16ms):
186.2.175.234

ns1.ddos-guard.net [185.129.101.200] (144ms):
186.2.175.234

ns2.ddos-guard.net [185.129.103.200] (144ms):
186.2.175.234

pns71.cloudns.net [45.83.248.12] (0ms):
186.2.175.234

pns73.cloudns.net [45.83.250.12] (4ms):
186.2.175.234

pns71.cloudns.net [45.83.248.12] (4ms):
186.2.175.234

pns73.cloudns.net [45.83.250.12] (0ms):
186.2.175.234

5. A record distribution by location for www.futemax.med

Shows how the name servers respond to requests for www.futemax.med

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

ns1.ddos-guard.net [185.129.101.200] (8ms):
186.2.175.234

ns2.ddos-guard.net [185.129.103.200] (8ms):
186.2.175.234

ns1.ddos-guard.net [185.129.101.200] (144ms):
186.2.175.234

ns2.ddos-guard.net [185.129.103.200] (152ms):
186.2.175.234

pns71.cloudns.net [45.83.248.12] (0ms):
186.2.175.234

pns73.cloudns.net [45.83.250.12] (0ms):
186.2.175.234

pns71.cloudns.net [45.83.248.12] (0ms):
186.2.175.234

pns73.cloudns.net [45.83.250.12] (0ms):
186.2.175.234

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 39.63ms.
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