DNS audit for leaksense.cloud created on 2026-10-02 12:41:39

1. Name servers

Name servers listed at the parent server ns10.trs-dns.info:

carl.ns.cloudflare.com
kristin.ns.cloudflare.com

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 leaksense.cloud.

2. NS records

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

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

carl.ns.cloudflare.com [172.64.33.106] (4ms):

carl.ns.cloudflare.com [173.245.59.106] (4ms):

carl.ns.cloudflare.com [108.162.193.106] (4ms):

kristin.ns.cloudflare.com [173.245.58.181] (0ms):

kristin.ns.cloudflare.com [172.64.32.181] (4ms):

kristin.ns.cloudflare.com [108.162.192.181] (0ms):

carl.ns.cloudflare.com [172.64.33.106] (20ms):

carl.ns.cloudflare.com [108.162.193.106] (20ms):

carl.ns.cloudflare.com [173.245.59.106] (20ms):

kristin.ns.cloudflare.com [108.162.192.181] (24ms):

kristin.ns.cloudflare.com [173.245.58.181] (24ms):

kristin.ns.cloudflare.com [172.64.32.181] (24ms):

carl.ns.cloudflare.com [173.245.59.106] (0ms):

carl.ns.cloudflare.com [108.162.193.106] (4ms):

carl.ns.cloudflare.com [172.64.33.106] (0ms):

kristin.ns.cloudflare.com [173.245.58.181] (4ms):

kristin.ns.cloudflare.com [108.162.192.181] (4ms):

kristin.ns.cloudflare.com [172.64.32.181] (0ms):

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

carl.ns.cloudflare.com [172.64.33.106] (0ms):

carl.ns.cloudflare.com [173.245.59.106] (0ms):

carl.ns.cloudflare.com [108.162.193.106] (4ms):

kristin.ns.cloudflare.com [108.162.192.181] (0ms):

kristin.ns.cloudflare.com [172.64.32.181] (0ms):

kristin.ns.cloudflare.com [173.245.58.181] (0ms):

Sydney, AU
Johannesburg, ZA

carl.ns.cloudflare.com [108.162.193.106] (24ms):

carl.ns.cloudflare.com [172.64.33.106] (20ms):

carl.ns.cloudflare.com [173.245.59.106] (20ms):

kristin.ns.cloudflare.com [108.162.192.181] (20ms):

kristin.ns.cloudflare.com [173.245.58.181] (20ms):

kristin.ns.cloudflare.com [172.64.32.181] (20ms):

Singapore

carl.ns.cloudflare.com [172.64.33.106] (4ms):

carl.ns.cloudflare.com [173.245.59.106] (0ms):

carl.ns.cloudflare.com [108.162.193.106] (4ms):

kristin.ns.cloudflare.com [172.64.32.181] (4ms):

kristin.ns.cloudflare.com [173.245.58.181] (4ms):

kristin.ns.cloudflare.com [108.162.192.181] (4ms):

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 leaksense.cloud

Shows how the name servers respond to requests for leaksense.cloud

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

carl.ns.cloudflare.com [172.64.33.106] (0ms):

carl.ns.cloudflare.com [173.245.59.106] (0ms):

carl.ns.cloudflare.com [108.162.193.106] (0ms):

kristin.ns.cloudflare.com [172.64.32.181] (0ms):

kristin.ns.cloudflare.com [108.162.192.181] (4ms):

kristin.ns.cloudflare.com [173.245.58.181] (0ms):

carl.ns.cloudflare.com [108.162.193.106] (16ms):

carl.ns.cloudflare.com [173.245.59.106] (24ms):

carl.ns.cloudflare.com [172.64.33.106] (20ms):

kristin.ns.cloudflare.com [173.245.58.181] (20ms):

kristin.ns.cloudflare.com [108.162.192.181] (20ms):

kristin.ns.cloudflare.com [172.64.32.181] (20ms):

carl.ns.cloudflare.com [173.245.59.106] (0ms):

carl.ns.cloudflare.com [108.162.193.106] (0ms):

carl.ns.cloudflare.com [172.64.33.106] (0ms):

kristin.ns.cloudflare.com [172.64.32.181] (4ms):

kristin.ns.cloudflare.com [173.245.58.181] (4ms):

kristin.ns.cloudflare.com [108.162.192.181] (0ms):

5. A record distribution by location for www.leaksense.cloud

Shows how the name servers respond to requests for www.leaksense.cloud

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

carl.ns.cloudflare.com [173.245.59.106] (4ms):

carl.ns.cloudflare.com [108.162.193.106] (0ms):

carl.ns.cloudflare.com [172.64.33.106] (4ms):

kristin.ns.cloudflare.com [108.162.192.181] (0ms):

kristin.ns.cloudflare.com [172.64.32.181] (4ms):

kristin.ns.cloudflare.com [173.245.58.181] (0ms):

carl.ns.cloudflare.com [173.245.59.106] (20ms):

carl.ns.cloudflare.com [172.64.33.106] (20ms):

carl.ns.cloudflare.com [108.162.193.106] (20ms):

kristin.ns.cloudflare.com [172.64.32.181] (20ms):

kristin.ns.cloudflare.com [173.245.58.181] (24ms):

kristin.ns.cloudflare.com [108.162.192.181] (24ms):

carl.ns.cloudflare.com [108.162.193.106] (0ms):

carl.ns.cloudflare.com [172.64.33.106] (4ms):

carl.ns.cloudflare.com [173.245.59.106] (4ms):

kristin.ns.cloudflare.com [172.64.32.181] (4ms):

kristin.ns.cloudflare.com [173.245.58.181] (4ms):

kristin.ns.cloudflare.com [108.162.192.181] (4ms):

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


Newer reports for leaksense.cloud: 2026-10-02 14:43:21
Blog | Cloud DNS
Sponsored by ClouDNS