DNS audit for palala.dev created on 2026-03-24 05:00:13

PDF

1. Name servers

Name servers listed at the parent server ns-tld3.charlestonroadregistry.com:

ns1.digitalocean.com
ns2.digitalocean.com
ns3.digitalocean.com

Result: 3 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 palala.dev.

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

ns1.digitalocean.com [172.64.52.210] (11ms):
ns1.digitalocean.com
ns2.digitalocean.com
ns3.digitalocean.com

ns2.digitalocean.com [172.64.53.21] (17ms):
ns1.digitalocean.com
ns2.digitalocean.com
ns3.digitalocean.com

ns3.digitalocean.com [172.64.49.209] (10ms):
ns1.digitalocean.com
ns2.digitalocean.com
ns3.digitalocean.com

ns1.digitalocean.com [172.64.52.210] (7ms):
ns1.digitalocean.com
ns2.digitalocean.com
ns3.digitalocean.com

ns2.digitalocean.com [172.64.53.21] (5ms):
ns1.digitalocean.com
ns2.digitalocean.com
ns3.digitalocean.com

ns3.digitalocean.com [172.64.49.209] (3ms):
ns1.digitalocean.com
ns2.digitalocean.com
ns3.digitalocean.com

ns1.digitalocean.com [172.64.52.210] (98ms):
ns1.digitalocean.com
ns2.digitalocean.com
ns3.digitalocean.com

ns2.digitalocean.com [172.64.53.21] (99ms):
ns1.digitalocean.com
ns2.digitalocean.com
ns3.digitalocean.com

ns3.digitalocean.com [172.64.49.209] (4ms):
ns1.digitalocean.com
ns2.digitalocean.com
ns3.digitalocean.com

ns1.digitalocean.com [172.64.52.210] (188ms):
ns1.digitalocean.com
ns2.digitalocean.com
ns3.digitalocean.com

ns2.digitalocean.com [172.64.53.21] (188ms):
ns1.digitalocean.com
ns2.digitalocean.com
ns3.digitalocean.com

ns3.digitalocean.com [172.64.49.209] (188ms):
ns1.digitalocean.com
ns2.digitalocean.com
ns3.digitalocean.com

ns1.digitalocean.com [172.64.52.210] (5ms):
ns1.digitalocean.com
ns2.digitalocean.com
ns3.digitalocean.com

ns2.digitalocean.com [172.64.53.21] (164ms):
ns1.digitalocean.com
ns2.digitalocean.com
ns3.digitalocean.com

ns3.digitalocean.com [172.64.49.209] (5ms):
ns1.digitalocean.com
ns2.digitalocean.com
ns3.digitalocean.com

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

Frankfurt, DE

ns1.digitalocean.com [172.64.52.210] (11ms):
ns1.digitalocean.com. hostmaster.palala.dev. 1757042417 10800 3600 604800 1800

ns2.digitalocean.com [172.64.53.21] (27ms):
ns1.digitalocean.com. hostmaster.palala.dev. 1757042417 10800 3600 604800 1800

ns3.digitalocean.com [172.64.49.209] (19ms):
ns1.digitalocean.com. hostmaster.palala.dev. 1757042417 10800 3600 604800 1800

San Francisco, US

ns1.digitalocean.com [172.64.52.210] (6ms):
ns1.digitalocean.com. hostmaster.palala.dev. 1757042417 10800 3600 604800 1800

ns2.digitalocean.com [172.64.53.21] (6ms):
ns1.digitalocean.com. hostmaster.palala.dev. 1757042417 10800 3600 604800 1800

ns3.digitalocean.com [172.64.49.209] (6ms):
ns1.digitalocean.com. hostmaster.palala.dev. 1757042417 10800 3600 604800 1800

Sydney, AU

ns1.digitalocean.com [172.64.52.210] (99ms):
ns1.digitalocean.com. hostmaster.palala.dev. 1757042417 10800 3600 604800 1800

ns2.digitalocean.com [172.64.53.21] (99ms):
ns1.digitalocean.com. hostmaster.palala.dev. 1757042417 10800 3600 604800 1800

ns3.digitalocean.com [172.64.49.209] (5ms):
ns1.digitalocean.com. hostmaster.palala.dev. 1757042417 10800 3600 604800 1800

Johannesburg, ZA

ns1.digitalocean.com [172.64.52.210] (192ms):
ns1.digitalocean.com. hostmaster.palala.dev. 1757042417 10800 3600 604800 1800

ns2.digitalocean.com [172.64.53.21] (0ms):
ns1.digitalocean.com. hostmaster.palala.dev. 1757042417 10800 3600 604800 1800

ns3.digitalocean.com [172.64.49.209] (184ms):
ns1.digitalocean.com. hostmaster.palala.dev. 1757042417 10800 3600 604800 1800

Singapore

ns1.digitalocean.com [172.64.52.210] (4ms):
ns1.digitalocean.com. hostmaster.palala.dev. 1757042417 10800 3600 604800 1800

ns2.digitalocean.com [172.64.53.21] (163ms):
ns1.digitalocean.com. hostmaster.palala.dev. 1757042417 10800 3600 604800 1800

ns3.digitalocean.com [172.64.49.209] (5ms):
ns1.digitalocean.com. hostmaster.palala.dev. 1757042417 10800 3600 604800 1800

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 palala.dev

Shows how the name servers respond to requests for palala.dev

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

ns1.digitalocean.com [172.64.52.210] (22ms):
104.248.183.160

ns2.digitalocean.com [172.64.53.21] (16ms):
104.248.183.160

ns3.digitalocean.com [172.64.49.209] (18ms):
104.248.183.160

ns1.digitalocean.com [172.64.52.210] (5ms):
104.248.183.160

ns2.digitalocean.com [172.64.53.21] (7ms):
104.248.183.160

ns3.digitalocean.com [172.64.49.209] (6ms):
104.248.183.160

ns1.digitalocean.com [172.64.52.210] (99ms):
104.248.183.160

ns2.digitalocean.com [172.64.53.21] (102ms):
104.248.183.160

ns3.digitalocean.com [172.64.49.209] (3ms):
104.248.183.160

ns1.digitalocean.com [172.64.52.210] (188ms):
104.248.183.160

ns2.digitalocean.com [172.64.53.21] (188ms):
104.248.183.160

ns3.digitalocean.com [172.64.49.209] (4ms):
104.248.183.160

ns1.digitalocean.com [172.64.52.210] (165ms):
104.248.183.160

ns2.digitalocean.com [172.64.53.21] (6ms):
104.248.183.160

ns3.digitalocean.com [172.64.49.209] (5ms):
104.248.183.160

5. A record distribution by location for www.palala.dev

Shows how the name servers respond to requests for www.palala.dev

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

ns1.digitalocean.com [172.64.52.210] (12ms):
104.248.183.160

ns2.digitalocean.com [172.64.53.21] (20ms):
104.248.183.160

ns3.digitalocean.com [172.64.49.209] (44ms):
104.248.183.160

ns1.digitalocean.com [172.64.52.210] (7ms):
104.248.183.160

ns2.digitalocean.com [172.64.53.21] (4ms):
104.248.183.160

ns3.digitalocean.com [172.64.49.209] (6ms):
104.248.183.160

ns1.digitalocean.com [172.64.52.210] (99ms):
104.248.183.160

ns2.digitalocean.com [172.64.53.21] (100ms):
104.248.183.160

ns3.digitalocean.com [172.64.49.209] (4ms):
104.248.183.160

ns1.digitalocean.com [172.64.52.210] (188ms):
104.248.183.160

ns2.digitalocean.com [172.64.53.21] (0ms):
104.248.183.160

ns3.digitalocean.com [172.64.49.209] (0ms):
104.248.183.160

ns1.digitalocean.com [172.64.52.210] (171ms):
104.248.183.160

ns2.digitalocean.com [172.64.53.21] (159ms):
104.248.183.160

ns3.digitalocean.com [172.64.49.209] (4ms):
104.248.183.160

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