DNS audit for imoe.blog created on 2026-06-10 10:45:47

1. Name servers

Name servers listed at the parent server a.ns.nic.blog:

ns1.luadns.net
ns2.he.net
ns2.luadns.net
ns3.he.net
ns3.luadns.net
ns4.luadns.net

Result: 6 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 imoe.blog.

2. NS records

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

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

ns1.luadns.net [185.142.218.1] (131ms):
ns1.luadns.net
ns2.he.net
ns2.luadns.net
ns3.he.net
ns3.luadns.net
ns4.luadns.net

ns2.he.net [216.218.131.2] (4ms):

ns2.luadns.net [185.142.218.2] (134ms):
ns1.luadns.net
ns2.he.net
ns2.luadns.net
ns3.he.net
ns3.luadns.net
ns4.luadns.net

ns3.he.net [216.218.132.2] (2ms):

ns3.luadns.net [185.142.218.3] (136ms):
ns1.luadns.net
ns2.he.net
ns2.luadns.net
ns3.he.net
ns3.luadns.net
ns4.luadns.net

ns4.luadns.net [185.142.218.4] (134ms):
ns1.luadns.net
ns2.he.net
ns2.luadns.net
ns3.he.net
ns3.luadns.net
ns4.luadns.net

ns1.luadns.net [185.142.218.1] (1ms):
ns1.luadns.net
ns2.he.net
ns2.luadns.net
ns3.he.net
ns3.luadns.net
ns4.luadns.net

ns2.he.net [216.218.131.2] (91ms):

ns2.luadns.net [185.142.218.2] (1ms):
ns1.luadns.net
ns2.he.net
ns2.luadns.net
ns3.he.net
ns3.luadns.net
ns4.luadns.net

ns3.he.net [216.218.132.2] (92ms):

ns3.luadns.net [185.142.218.3] (0ms):
ns1.luadns.net
ns2.he.net
ns2.luadns.net
ns3.he.net
ns3.luadns.net
ns4.luadns.net

ns4.luadns.net [185.142.218.4] (0ms):
ns1.luadns.net
ns2.he.net
ns2.luadns.net
ns3.he.net
ns3.luadns.net
ns4.luadns.net

ns1.luadns.net [185.142.218.1] (0ms):
ns1.luadns.net
ns2.he.net
ns2.luadns.net
ns3.he.net
ns3.luadns.net
ns4.luadns.net

ns2.he.net [216.218.131.2] (160ms):

ns2.luadns.net [185.142.218.2] (0ms):
ns1.luadns.net
ns2.he.net
ns2.luadns.net
ns3.he.net
ns3.luadns.net
ns4.luadns.net

ns3.he.net [216.218.132.2] (156ms):

ns3.luadns.net [185.142.218.3] (4ms):
ns1.luadns.net
ns2.he.net
ns2.luadns.net
ns3.he.net
ns3.luadns.net
ns4.luadns.net

ns4.luadns.net [185.142.218.4] (0ms):
ns1.luadns.net
ns2.he.net
ns2.luadns.net
ns3.he.net
ns3.luadns.net
ns4.luadns.net

ns1.luadns.net [185.142.218.1] (1ms):
ns1.luadns.net
ns2.he.net
ns2.luadns.net
ns3.he.net
ns3.luadns.net
ns4.luadns.net

ns2.he.net [216.218.131.2] (1ms):

ns2.luadns.net [185.142.218.2] (0ms):
ns1.luadns.net
ns2.he.net
ns2.luadns.net
ns3.he.net
ns3.luadns.net
ns4.luadns.net

ns3.he.net [216.218.132.2] (0ms):

ns3.luadns.net [185.142.218.3] (0ms):
ns1.luadns.net
ns2.he.net
ns2.luadns.net
ns3.he.net
ns3.luadns.net
ns4.luadns.net

ns4.luadns.net [185.142.218.4] (1ms):
ns1.luadns.net
ns2.he.net
ns2.luadns.net
ns3.he.net
ns3.luadns.net
ns4.luadns.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

ns1.luadns.net [185.142.218.1] (138ms):
ns1.luadns.net. hostmaster.luadns.com. 1780807112 1200 120 604800 3600

ns2.he.net [216.218.131.2] (2ms):

ns2.luadns.net [185.142.218.2] (131ms):
ns1.luadns.net. hostmaster.luadns.com. 1780807112 1200 120 604800 3600

ns3.he.net [216.218.132.2] (2ms):

ns3.luadns.net [185.142.218.3] (138ms):
ns1.luadns.net. hostmaster.luadns.com. 1780807112 1200 120 604800 3600

ns4.luadns.net [185.142.218.4] (130ms):
ns1.luadns.net. hostmaster.luadns.com. 1780807112 1200 120 604800 3600

Sydney, AU

ns1.luadns.net [185.142.218.1] (0ms):
ns1.luadns.net. hostmaster.luadns.com. 1780807112 1200 120 604800 3600

ns2.he.net [216.218.131.2] (91ms):

ns2.luadns.net [185.142.218.2] (0ms):
ns1.luadns.net. hostmaster.luadns.com. 1780807112 1200 120 604800 3600

ns3.he.net [216.218.132.2] (92ms):

ns3.luadns.net [185.142.218.3] (0ms):
ns1.luadns.net. hostmaster.luadns.com. 1780807112 1200 120 604800 3600

ns4.luadns.net [185.142.218.4] (0ms):
ns1.luadns.net. hostmaster.luadns.com. 1780807112 1200 120 604800 3600

Johannesburg, ZA

ns1.luadns.net [185.142.218.1] (4ms):
ns1.luadns.net. hostmaster.luadns.com. 1780807112 1200 120 604800 3600

ns2.he.net [216.218.131.2] (156ms):

ns2.luadns.net [185.142.218.2] (0ms):
ns1.luadns.net. hostmaster.luadns.com. 1780807112 1200 120 604800 3600

ns3.he.net [216.218.132.2] (160ms):

ns3.luadns.net [185.142.218.3] (0ms):
ns1.luadns.net. hostmaster.luadns.com. 1780807112 1200 120 604800 3600

ns4.luadns.net [185.142.218.4] (0ms):
ns1.luadns.net. hostmaster.luadns.com. 1780807112 1200 120 604800 3600

Singapore

ns1.luadns.net [185.142.218.1] (1ms):
ns1.luadns.net. hostmaster.luadns.com. 1780807112 1200 120 604800 3600

ns2.he.net [216.218.131.2] (0ms):

ns2.luadns.net [185.142.218.2] (0ms):
ns1.luadns.net. hostmaster.luadns.com. 1780807112 1200 120 604800 3600

ns3.he.net [216.218.132.2] (33ms):

ns3.luadns.net [185.142.218.3] (0ms):
ns1.luadns.net. hostmaster.luadns.com. 1780807112 1200 120 604800 3600

ns4.luadns.net [185.142.218.4] (0ms):
ns1.luadns.net. hostmaster.luadns.com. 1780807112 1200 120 604800 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 imoe.blog

Shows how the name servers respond to requests for imoe.blog

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

ns1.luadns.net [185.142.218.1] (134ms):
5.161.23.223

ns2.he.net [216.218.131.2] (2ms):

ns2.luadns.net [185.142.218.2] (130ms):
5.161.23.223

ns3.he.net [216.218.132.2] (2ms):

ns3.luadns.net [185.142.218.3] (138ms):
5.161.23.223

ns4.luadns.net [185.142.218.4] (130ms):
5.161.23.223

ns1.luadns.net [185.142.218.1] (0ms):
5.161.23.223

ns2.he.net [216.218.131.2] (92ms):

ns2.luadns.net [185.142.218.2] (0ms):
5.161.23.223

ns3.he.net [216.218.132.2] (93ms):

ns3.luadns.net [185.142.218.3] (0ms):
5.161.23.223

ns4.luadns.net [185.142.218.4] (0ms):
5.161.23.223

ns1.luadns.net [185.142.218.1] (4ms):
5.161.23.223

ns2.he.net [216.218.131.2] (156ms):

ns2.luadns.net [185.142.218.2] (0ms):
5.161.23.223

ns3.he.net [216.218.132.2] (152ms):

ns3.luadns.net [185.142.218.3] (4ms):
5.161.23.223

ns4.luadns.net [185.142.218.4] (0ms):
5.161.23.223

ns1.luadns.net [185.142.218.1] (0ms):
5.161.23.223

ns2.he.net [216.218.131.2] (34ms):

ns2.luadns.net [185.142.218.2] (0ms):
5.161.23.223

ns3.he.net [216.218.132.2] (33ms):

ns3.luadns.net [185.142.218.3] (0ms):
5.161.23.223

ns4.luadns.net [185.142.218.4] (0ms):
5.161.23.223

5. A record distribution by location for www.imoe.blog

Shows how the name servers respond to requests for www.imoe.blog

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

ns1.luadns.net [185.142.218.1] (134ms):
45.77.68.45

ns2.he.net [216.218.131.2] (2ms):

ns2.luadns.net [185.142.218.2] (134ms):
45.77.68.45

ns3.he.net [216.218.132.2] (2ms):

ns3.luadns.net [185.142.218.3] (138ms):
45.77.68.45

ns4.luadns.net [185.142.218.4] (134ms):
45.77.68.45

ns1.luadns.net [185.142.218.1] (1ms):
45.77.68.45

ns2.he.net [216.218.131.2] (92ms):

ns2.luadns.net [185.142.218.2] (0ms):
45.77.68.45

ns3.he.net [216.218.132.2] (92ms):

ns3.luadns.net [185.142.218.3] (0ms):
45.77.68.45

ns4.luadns.net [185.142.218.4] (0ms):
45.77.68.45

ns1.luadns.net [185.142.218.1] (0ms):
45.77.68.45

ns2.he.net [216.218.131.2] (160ms):

ns2.luadns.net [185.142.218.2] (0ms):
45.77.68.45

ns3.he.net [216.218.132.2] (160ms):

ns3.luadns.net [185.142.218.3] (4ms):
45.77.68.45

ns4.luadns.net [185.142.218.4] (0ms):
45.77.68.45

ns1.luadns.net [185.142.218.1] (0ms):
45.77.68.45

ns2.he.net [216.218.131.2] (34ms):

ns2.luadns.net [185.142.218.2] (0ms):
45.77.68.45

ns3.he.net [216.218.132.2] (0ms):

ns3.luadns.net [185.142.218.3] (0ms):
45.77.68.45

ns4.luadns.net [185.142.218.4] (0ms):
45.77.68.45

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