DNS audit for markdarland.com created on 2026-03-20 14:26:20

PDF

1. Name servers

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

dns31.cloudns.net
dns32.cloudns.net
dns33.cloudns.net
dns34.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 markdarland.com.

2. NS records

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

Frankfurt, DE San Francisco, US Sydney, AU Johannesburg, ZA Singapore

dns31.cloudns.net [185.136.96.100] (0ms):
dns31.cloudns.net
dns32.cloudns.net
dns33.cloudns.net
dns34.cloudns.net
ns5.markdarland.com
ns6.markdarland.com

dns32.cloudns.net [185.136.97.100] (0ms):
dns31.cloudns.net
dns32.cloudns.net
dns33.cloudns.net
dns34.cloudns.net
ns5.markdarland.com
ns6.markdarland.com

dns33.cloudns.net [185.136.98.100] (0ms):
dns31.cloudns.net
dns32.cloudns.net
dns33.cloudns.net
dns34.cloudns.net
ns5.markdarland.com
ns6.markdarland.com

dns34.cloudns.net [185.136.99.100] (0ms):
dns31.cloudns.net
dns32.cloudns.net
dns33.cloudns.net
dns34.cloudns.net
ns5.markdarland.com
ns6.markdarland.com

dns31.cloudns.net [185.136.96.100] (1ms):
dns31.cloudns.net
dns32.cloudns.net
dns33.cloudns.net
dns34.cloudns.net
ns5.markdarland.com
ns6.markdarland.com

dns32.cloudns.net [185.136.97.100] (1ms):
dns31.cloudns.net
dns32.cloudns.net
dns33.cloudns.net
dns34.cloudns.net
ns5.markdarland.com
ns6.markdarland.com

dns33.cloudns.net [185.136.98.100] (3ms):
dns31.cloudns.net
dns32.cloudns.net
dns33.cloudns.net
dns34.cloudns.net
ns5.markdarland.com
ns6.markdarland.com

dns34.cloudns.net [185.136.99.100] (1ms):
dns31.cloudns.net
dns32.cloudns.net
dns33.cloudns.net
dns34.cloudns.net
ns5.markdarland.com
ns6.markdarland.com

dns31.cloudns.net [185.136.96.100] (0ms):
dns31.cloudns.net
dns32.cloudns.net
dns33.cloudns.net
dns34.cloudns.net
ns5.markdarland.com
ns6.markdarland.com

dns32.cloudns.net [185.136.97.100] (92ms):
dns31.cloudns.net
dns32.cloudns.net
dns33.cloudns.net
dns34.cloudns.net
ns5.markdarland.com
ns6.markdarland.com

dns33.cloudns.net [185.136.98.100] (0ms):
dns31.cloudns.net
dns32.cloudns.net
dns33.cloudns.net
dns34.cloudns.net
ns5.markdarland.com
ns6.markdarland.com

dns34.cloudns.net [185.136.99.100] (0ms):
dns31.cloudns.net
dns32.cloudns.net
dns33.cloudns.net
dns34.cloudns.net
ns5.markdarland.com
ns6.markdarland.com

dns31.cloudns.net [185.136.96.100] (0ms):
dns31.cloudns.net
dns32.cloudns.net
dns33.cloudns.net
dns34.cloudns.net
ns5.markdarland.com
ns6.markdarland.com

dns32.cloudns.net [185.136.97.100] (4ms):
dns31.cloudns.net
dns32.cloudns.net
dns33.cloudns.net
dns34.cloudns.net
ns5.markdarland.com
ns6.markdarland.com

dns33.cloudns.net [185.136.98.100] (0ms):
dns31.cloudns.net
dns32.cloudns.net
dns33.cloudns.net
dns34.cloudns.net
ns5.markdarland.com
ns6.markdarland.com

dns34.cloudns.net [185.136.99.100] (0ms):
dns31.cloudns.net
dns32.cloudns.net
dns33.cloudns.net
dns34.cloudns.net
ns5.markdarland.com
ns6.markdarland.com

dns31.cloudns.net [185.136.96.100] (1ms):
dns31.cloudns.net
dns32.cloudns.net
dns33.cloudns.net
dns34.cloudns.net
ns5.markdarland.com
ns6.markdarland.com

dns32.cloudns.net [185.136.97.100] (1ms):
dns31.cloudns.net
dns32.cloudns.net
dns33.cloudns.net
dns34.cloudns.net
ns5.markdarland.com
ns6.markdarland.com

dns33.cloudns.net [185.136.98.100] (1ms):
dns31.cloudns.net
dns32.cloudns.net
dns33.cloudns.net
dns34.cloudns.net
ns5.markdarland.com
ns6.markdarland.com

dns34.cloudns.net [185.136.99.100] (1ms):
dns31.cloudns.net
dns32.cloudns.net
dns33.cloudns.net
dns34.cloudns.net
ns5.markdarland.com
ns6.markdarland.com

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

Frankfurt, DE

dns31.cloudns.net [185.136.96.100] (0ms):
dns31.cloudns.net. support.cloudns.net. 2026032016 7200 1800 1209600 3600

dns32.cloudns.net [185.136.97.100] (0ms):
dns31.cloudns.net. support.cloudns.net. 2026032016 7200 1800 1209600 3600

dns33.cloudns.net [185.136.98.100] (0ms):
dns31.cloudns.net. support.cloudns.net. 2026032016 7200 1800 1209600 3600

dns34.cloudns.net [185.136.99.100] (0ms):
dns31.cloudns.net. support.cloudns.net. 2026032016 7200 1800 1209600 3600

San Francisco, US

dns31.cloudns.net [185.136.96.100] (1ms):
dns31.cloudns.net. support.cloudns.net. 2026032016 7200 1800 1209600 3600

dns32.cloudns.net [185.136.97.100] (1ms):
dns31.cloudns.net. support.cloudns.net. 2026032016 7200 1800 1209600 3600

dns33.cloudns.net [185.136.98.100] (1ms):
dns31.cloudns.net. support.cloudns.net. 2026032016 7200 1800 1209600 3600

dns34.cloudns.net [185.136.99.100] (1ms):
dns31.cloudns.net. support.cloudns.net. 2026032016 7200 1800 1209600 3600

Sydney, AU

dns31.cloudns.net [185.136.96.100] (0ms):
dns31.cloudns.net. support.cloudns.net. 2026032016 7200 1800 1209600 3600

dns32.cloudns.net [185.136.97.100] (135ms):
dns31.cloudns.net. support.cloudns.net. 2026032016 7200 1800 1209600 3600

dns33.cloudns.net [185.136.98.100] (0ms):
dns31.cloudns.net. support.cloudns.net. 2026032016 7200 1800 1209600 3600

dns34.cloudns.net [185.136.99.100] (0ms):
dns31.cloudns.net. support.cloudns.net. 2026032016 7200 1800 1209600 3600

Johannesburg, ZA

dns31.cloudns.net [185.136.96.100] (0ms):
dns31.cloudns.net. support.cloudns.net. 2026032016 7200 1800 1209600 3600

dns32.cloudns.net [185.136.97.100] (0ms):
dns31.cloudns.net. support.cloudns.net. 2026032016 7200 1800 1209600 3600

dns33.cloudns.net [185.136.98.100] (4ms):
dns31.cloudns.net. support.cloudns.net. 2026032016 7200 1800 1209600 3600

dns34.cloudns.net [185.136.99.100] (0ms):
dns31.cloudns.net. support.cloudns.net. 2026032016 7200 1800 1209600 3600

Singapore

dns31.cloudns.net [185.136.96.100] (1ms):
dns31.cloudns.net. support.cloudns.net. 2026032016 7200 1800 1209600 3600

dns32.cloudns.net [185.136.97.100] (1ms):
dns31.cloudns.net. support.cloudns.net. 2026032016 7200 1800 1209600 3600

dns33.cloudns.net [185.136.98.100] (1ms):
dns31.cloudns.net. support.cloudns.net. 2026032016 7200 1800 1209600 3600

dns34.cloudns.net [185.136.99.100] (1ms):
dns31.cloudns.net. support.cloudns.net. 2026032016 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 markdarland.com

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

Frankfurt, DE San Francisco, US Sydney, AU Johannesburg, ZA Singapore

dns31.cloudns.net [185.136.96.100] (0ms):
216.150.1.1

dns32.cloudns.net [185.136.97.100] (0ms):
216.150.1.1

dns33.cloudns.net [185.136.98.100] (0ms):
216.150.1.1

dns34.cloudns.net [185.136.99.100] (0ms):
216.150.1.1

dns31.cloudns.net [185.136.96.100] (1ms):
216.150.1.1

dns32.cloudns.net [185.136.97.100] (1ms):
216.150.1.1

dns33.cloudns.net [185.136.98.100] (1ms):
216.150.1.1

dns34.cloudns.net [185.136.99.100] (1ms):
216.150.1.1

dns31.cloudns.net [185.136.96.100] (0ms):
216.150.1.1

dns32.cloudns.net [185.136.97.100] (135ms):
216.150.1.1

dns33.cloudns.net [185.136.98.100] (0ms):
216.150.1.1

dns34.cloudns.net [185.136.99.100] (0ms):
216.150.1.1

dns31.cloudns.net [185.136.96.100] (4ms):
216.150.1.1

dns32.cloudns.net [185.136.97.100] (0ms):
216.150.1.1

dns33.cloudns.net [185.136.98.100] (0ms):
216.150.1.1

dns34.cloudns.net [185.136.99.100] (0ms):
216.150.1.1

dns31.cloudns.net [185.136.96.100] (1ms):
216.150.1.1

dns32.cloudns.net [185.136.97.100] (1ms):
216.150.1.1

dns33.cloudns.net [185.136.98.100] (1ms):
216.150.1.1

dns34.cloudns.net [185.136.99.100] (1ms):
216.150.1.1

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

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

Frankfurt, DE San Francisco, US Sydney, AU Johannesburg, ZA Singapore

dns31.cloudns.net [185.136.96.100] (0ms):
216.150.1.1

dns32.cloudns.net [185.136.97.100] (0ms):
216.150.1.1

dns33.cloudns.net [185.136.98.100] (0ms):
216.150.1.1

dns34.cloudns.net [185.136.99.100] (0ms):
216.150.1.1

dns31.cloudns.net [185.136.96.100] (1ms):
216.150.1.1

dns32.cloudns.net [185.136.97.100] (1ms):
216.150.1.1

dns33.cloudns.net [185.136.98.100] (2ms):
216.150.1.1

dns34.cloudns.net [185.136.99.100] (1ms):
216.150.1.1

dns31.cloudns.net [185.136.96.100] (0ms):
216.150.1.1

dns32.cloudns.net [185.136.97.100] (135ms):
216.150.1.1

dns33.cloudns.net [185.136.98.100] (1ms):
216.150.1.1

dns34.cloudns.net [185.136.99.100] (0ms):
216.150.1.1

dns31.cloudns.net [185.136.96.100] (0ms):
216.150.1.1

dns32.cloudns.net [185.136.97.100] (4ms):
216.150.1.1

dns33.cloudns.net [185.136.98.100] (4ms):
216.150.1.1

dns34.cloudns.net [185.136.99.100] (0ms):
216.150.1.1

dns31.cloudns.net [185.136.96.100] (1ms):
216.150.1.1

dns32.cloudns.net [185.136.97.100] (1ms):
216.150.1.1

dns33.cloudns.net [185.136.98.100] (1ms):
216.150.1.1

dns34.cloudns.net [185.136.99.100] (1ms):
216.150.1.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 6.84ms.
Recommendation: The name servers have good response time.

Previous reports for markdarland.com: 2026-03-20 14:22:48 , 2026-03-20 14:16:40 , 2026-03-20 14:06:40 , 2026-03-20 14:02:07
Newer reports for markdarland.com: 2026-03-20 14:27:18 , 2026-03-20 14:30:05 , 2026-03-20 14:35:21 , 2026-03-20 14:42:42
Blog | Cloud DNS
Sponsored by ClouDNS