DNS audit for hautamaki.info created on 2026-09-10 14:09:33

PDF

1. Name servers

Name servers listed at the parent server d0.info.afilias-nst.org:

pns31.cloudns.net
pns32.cloudns.net
pns33.cloudns.net
pns34.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 hautamaki.info.

2. NS records

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

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

pns31.cloudns.net [185.136.96.66] (2ms):
pns31.cloudns.net
pns32.cloudns.net
pns33.cloudns.net
pns34.cloudns.net

pns32.cloudns.net [185.136.97.66] (1ms):
pns31.cloudns.net
pns32.cloudns.net
pns33.cloudns.net
pns34.cloudns.net

pns33.cloudns.net [185.136.98.66] (1ms):
pns31.cloudns.net
pns32.cloudns.net
pns33.cloudns.net
pns34.cloudns.net

pns34.cloudns.net [185.136.99.66] (1ms):
pns31.cloudns.net
pns32.cloudns.net
pns33.cloudns.net
pns34.cloudns.net

pns31.cloudns.net [185.136.96.66] (0ms):
pns31.cloudns.net
pns32.cloudns.net
pns33.cloudns.net
pns34.cloudns.net

pns32.cloudns.net [185.136.97.66] (142ms):
pns31.cloudns.net
pns32.cloudns.net
pns33.cloudns.net
pns34.cloudns.net

pns33.cloudns.net [185.136.98.66] (0ms):
pns31.cloudns.net
pns32.cloudns.net
pns33.cloudns.net
pns34.cloudns.net

pns34.cloudns.net [185.136.99.66] (0ms):
pns31.cloudns.net
pns32.cloudns.net
pns33.cloudns.net
pns34.cloudns.net

pns31.cloudns.net [185.136.96.66] (4ms):
pns31.cloudns.net
pns32.cloudns.net
pns33.cloudns.net
pns34.cloudns.net

pns32.cloudns.net [185.136.97.66] (0ms):
pns31.cloudns.net
pns32.cloudns.net
pns33.cloudns.net
pns34.cloudns.net

pns33.cloudns.net [185.136.98.66] (0ms):
pns31.cloudns.net
pns32.cloudns.net
pns33.cloudns.net
pns34.cloudns.net

pns34.cloudns.net [185.136.99.66] (0ms):
pns31.cloudns.net
pns32.cloudns.net
pns33.cloudns.net
pns34.cloudns.net

pns31.cloudns.net [185.136.96.66] (0ms):
pns31.cloudns.net
pns32.cloudns.net
pns33.cloudns.net
pns34.cloudns.net

pns32.cloudns.net [185.136.97.66] (1ms):
pns31.cloudns.net
pns32.cloudns.net
pns33.cloudns.net
pns34.cloudns.net

pns33.cloudns.net [185.136.98.66] (0ms):
pns31.cloudns.net
pns32.cloudns.net
pns33.cloudns.net
pns34.cloudns.net

pns34.cloudns.net [185.136.99.66] (1ms):
pns31.cloudns.net
pns32.cloudns.net
pns33.cloudns.net
pns34.cloudns.net

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

pns31.cloudns.net [185.136.96.66] (1ms):
pns31.cloudns.net. support.cloudns.net. 2026090302 7200 1800 1209600 3600

pns32.cloudns.net [185.136.97.66] (1ms):
pns31.cloudns.net. support.cloudns.net. 2026090302 7200 1800 1209600 3600

pns33.cloudns.net [185.136.98.66] (1ms):
pns31.cloudns.net. support.cloudns.net. 2026090302 7200 1800 1209600 3600

pns34.cloudns.net [185.136.99.66] (1ms):
pns31.cloudns.net. support.cloudns.net. 2026090302 7200 1800 1209600 3600

Sydney, AU

pns31.cloudns.net [185.136.96.66] (0ms):
pns31.cloudns.net. support.cloudns.net. 2026090302 7200 1800 1209600 3600

pns32.cloudns.net [185.136.97.66] (145ms):
pns31.cloudns.net. support.cloudns.net. 2026090302 7200 1800 1209600 3600

pns33.cloudns.net [185.136.98.66] (0ms):
pns31.cloudns.net. support.cloudns.net. 2026090302 7200 1800 1209600 3600

pns34.cloudns.net [185.136.99.66] (0ms):
pns31.cloudns.net. support.cloudns.net. 2026090302 7200 1800 1209600 3600

Johannesburg, ZA

pns31.cloudns.net [185.136.96.66] (0ms):
pns31.cloudns.net. support.cloudns.net. 2026090302 7200 1800 1209600 3600

pns32.cloudns.net [185.136.97.66] (0ms):
pns31.cloudns.net. support.cloudns.net. 2026090302 7200 1800 1209600 3600

pns33.cloudns.net [185.136.98.66] (4ms):
pns31.cloudns.net. support.cloudns.net. 2026090302 7200 1800 1209600 3600

pns34.cloudns.net [185.136.99.66] (0ms):
pns31.cloudns.net. support.cloudns.net. 2026090302 7200 1800 1209600 3600

Singapore

pns31.cloudns.net [185.136.96.66] (0ms):
pns31.cloudns.net. support.cloudns.net. 2026090302 7200 1800 1209600 3600

pns32.cloudns.net [185.136.97.66] (1ms):
pns31.cloudns.net. support.cloudns.net. 2026090302 7200 1800 1209600 3600

pns33.cloudns.net [185.136.98.66] (0ms):
pns31.cloudns.net. support.cloudns.net. 2026090302 7200 1800 1209600 3600

pns34.cloudns.net [185.136.99.66] (1ms):
pns31.cloudns.net. support.cloudns.net. 2026090302 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 hautamaki.info

Shows how the name servers respond to requests for hautamaki.info

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

pns31.cloudns.net [185.136.96.66] (1ms):
88.148.211.117

pns32.cloudns.net [185.136.97.66] (1ms):
88.148.211.117

pns33.cloudns.net [185.136.98.66] (1ms):
88.148.211.117

pns34.cloudns.net [185.136.99.66] (1ms):
88.148.211.117

pns31.cloudns.net [185.136.96.66] (0ms):
88.148.211.117

pns32.cloudns.net [185.136.97.66] (145ms):
88.148.211.117

pns33.cloudns.net [185.136.98.66] (0ms):
88.148.211.117

pns34.cloudns.net [185.136.99.66] (0ms):
88.148.211.117

pns31.cloudns.net [185.136.96.66] (4ms):
88.148.211.117

pns32.cloudns.net [185.136.97.66] (0ms):
88.148.211.117

pns33.cloudns.net [185.136.98.66] (0ms):
88.148.211.117

pns34.cloudns.net [185.136.99.66] (0ms):
88.148.211.117

pns31.cloudns.net [185.136.96.66] (1ms):
88.148.211.117

pns32.cloudns.net [185.136.97.66] (1ms):
88.148.211.117

pns33.cloudns.net [185.136.98.66] (0ms):
88.148.211.117

pns34.cloudns.net [185.136.99.66] (1ms):
88.148.211.117

5. A record distribution by location for www.hautamaki.info

Shows how the name servers respond to requests for www.hautamaki.info

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

pns31.cloudns.net [185.136.96.66] (1ms):
88.148.211.117

pns32.cloudns.net [185.136.97.66] (1ms):
88.148.211.117

pns33.cloudns.net [185.136.98.66] (1ms):
88.148.211.117

pns34.cloudns.net [185.136.99.66] (1ms):
88.148.211.117

pns31.cloudns.net [185.136.96.66] (0ms):
88.148.211.117

pns32.cloudns.net [185.136.97.66] (141ms):
88.148.211.117

pns33.cloudns.net [185.136.98.66] (1ms):
88.148.211.117

pns34.cloudns.net [185.136.99.66] (0ms):
88.148.211.117

pns31.cloudns.net [185.136.96.66] (0ms):
88.148.211.117

pns32.cloudns.net [185.136.97.66] (0ms):
88.148.211.117

pns33.cloudns.net [185.136.98.66] (4ms):
88.148.211.117

pns34.cloudns.net [185.136.99.66] (4ms):
88.148.211.117

pns31.cloudns.net [185.136.96.66] (0ms):
88.148.211.117

pns32.cloudns.net [185.136.97.66] (1ms):
88.148.211.117

pns33.cloudns.net [185.136.98.66] (0ms):
88.148.211.117

pns34.cloudns.net [185.136.99.66] (1ms):
88.148.211.117

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

Blog | Cloud DNS
Sponsored by ClouDNS