DNS audit for devault.cloud created on 2026-11-07 16:26:02

PDF

1. Name servers

Name servers listed at the parent server ns01.trs-dns.net:

ns1.securedns.network
ns2.securedns.network
ns3.securedns.network
ns4.securedns.network

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

2. NS records

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

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

ns1.securedns.network [185.136.96.192] (4ms):
ns1.securedns.network
ns2.securedns.network
ns3.securedns.network
ns4.securedns.network

ns2.securedns.network [185.136.97.192] (4ms):
ns1.securedns.network
ns2.securedns.network
ns3.securedns.network
ns4.securedns.network

ns3.securedns.network [185.136.98.192] (4ms):
ns1.securedns.network
ns2.securedns.network
ns3.securedns.network
ns4.securedns.network

ns4.securedns.network [185.136.99.192] (4ms):
ns1.securedns.network
ns2.securedns.network
ns3.securedns.network
ns4.securedns.network

ns1.securedns.network [185.136.96.192] (0ms):
ns1.securedns.network
ns2.securedns.network
ns3.securedns.network
ns4.securedns.network

ns2.securedns.network [185.136.97.192] (136ms):
ns1.securedns.network
ns2.securedns.network
ns3.securedns.network
ns4.securedns.network

ns3.securedns.network [185.136.98.192] (0ms):
ns1.securedns.network
ns2.securedns.network
ns3.securedns.network
ns4.securedns.network

ns4.securedns.network [185.136.99.192] (0ms):
ns1.securedns.network
ns2.securedns.network
ns3.securedns.network
ns4.securedns.network

ns1.securedns.network [185.136.96.192] (0ms):
ns1.securedns.network
ns2.securedns.network
ns3.securedns.network
ns4.securedns.network

ns2.securedns.network [185.136.97.192] (0ms):
ns1.securedns.network
ns2.securedns.network
ns3.securedns.network
ns4.securedns.network

ns3.securedns.network [185.136.98.192] (0ms):
ns1.securedns.network
ns2.securedns.network
ns3.securedns.network
ns4.securedns.network

ns4.securedns.network [185.136.99.192] (0ms):
ns1.securedns.network
ns2.securedns.network
ns3.securedns.network
ns4.securedns.network

ns1.securedns.network [185.136.96.192] (0ms):
ns1.securedns.network
ns2.securedns.network
ns3.securedns.network
ns4.securedns.network

ns2.securedns.network [185.136.97.192] (0ms):
ns1.securedns.network
ns2.securedns.network
ns3.securedns.network
ns4.securedns.network

ns3.securedns.network [185.136.98.192] (0ms):
ns1.securedns.network
ns2.securedns.network
ns3.securedns.network
ns4.securedns.network

ns4.securedns.network [185.136.99.192] (4ms):
ns1.securedns.network
ns2.securedns.network
ns3.securedns.network
ns4.securedns.network

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

ns1.securedns.network [185.136.96.192] (0ms):
ns1.securedns.network. hostmaster.devault.ch. 2026101503 7200 1800 1209600 300

ns2.securedns.network [185.136.97.192] (0ms):
ns1.securedns.network. hostmaster.devault.ch. 2026101503 7200 1800 1209600 300

ns3.securedns.network [185.136.98.192] (0ms):
ns1.securedns.network. hostmaster.devault.ch. 2026101503 7200 1800 1209600 300

ns4.securedns.network [185.136.99.192] (0ms):
ns1.securedns.network. hostmaster.devault.ch. 2026101503 7200 1800 1209600 300

Sydney, AU

ns1.securedns.network [185.136.96.192] (4ms):
ns1.securedns.network. hostmaster.devault.ch. 2026101503 7200 1800 1209600 300

ns2.securedns.network [185.136.97.192] (136ms):
ns1.securedns.network. hostmaster.devault.ch. 2026101503 7200 1800 1209600 300

ns3.securedns.network [185.136.98.192] (0ms):
ns1.securedns.network. hostmaster.devault.ch. 2026101503 7200 1800 1209600 300

ns4.securedns.network [185.136.99.192] (0ms):
ns1.securedns.network. hostmaster.devault.ch. 2026101503 7200 1800 1209600 300

Johannesburg, ZA

ns1.securedns.network [185.136.96.192] (0ms):
ns1.securedns.network. hostmaster.devault.ch. 2026101503 7200 1800 1209600 300

ns2.securedns.network [185.136.97.192] (0ms):
ns1.securedns.network. hostmaster.devault.ch. 2026101503 7200 1800 1209600 300

ns3.securedns.network [185.136.98.192] (0ms):
ns1.securedns.network. hostmaster.devault.ch. 2026101503 7200 1800 1209600 300

ns4.securedns.network [185.136.99.192] (0ms):
ns1.securedns.network. hostmaster.devault.ch. 2026101503 7200 1800 1209600 300

Singapore

ns1.securedns.network [185.136.96.192] (0ms):
ns1.securedns.network. hostmaster.devault.ch. 2026101503 7200 1800 1209600 300

ns2.securedns.network [185.136.97.192] (0ms):
ns1.securedns.network. hostmaster.devault.ch. 2026101503 7200 1800 1209600 300

ns3.securedns.network [185.136.98.192] (4ms):
ns1.securedns.network. hostmaster.devault.ch. 2026101503 7200 1800 1209600 300

ns4.securedns.network [185.136.99.192] (0ms):
ns1.securedns.network. hostmaster.devault.ch. 2026101503 7200 1800 1209600 300

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

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

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

ns1.securedns.network [185.136.96.192] (0ms):
195.154.228.249

ns2.securedns.network [185.136.97.192] (0ms):
195.154.228.249

ns3.securedns.network [185.136.98.192] (4ms):
195.154.228.249

ns4.securedns.network [185.136.99.192] (4ms):
195.154.228.249

ns1.securedns.network [185.136.96.192] (4ms):
195.154.228.249

ns2.securedns.network [185.136.97.192] (136ms):
195.154.228.249

ns3.securedns.network [185.136.98.192] (0ms):
195.154.228.249

ns4.securedns.network [185.136.99.192] (0ms):
195.154.228.249

ns1.securedns.network [185.136.96.192] (0ms):
195.154.228.249

ns2.securedns.network [185.136.97.192] (4ms):
195.154.228.249

ns3.securedns.network [185.136.98.192] (0ms):
195.154.228.249

ns4.securedns.network [185.136.99.192] (0ms):
195.154.228.249

ns1.securedns.network [185.136.96.192] (0ms):
195.154.228.249

ns2.securedns.network [185.136.97.192] (4ms):
195.154.228.249

ns3.securedns.network [185.136.98.192] (0ms):
195.154.228.249

ns4.securedns.network [185.136.99.192] (0ms):
195.154.228.249

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

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

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

ns1.securedns.network [185.136.96.192] (0ms):

ns2.securedns.network [185.136.97.192] (4ms):

ns3.securedns.network [185.136.98.192] (0ms):

ns4.securedns.network [185.136.99.192] (0ms):

ns1.securedns.network [185.136.96.192] (0ms):

ns2.securedns.network [185.136.97.192] (136ms):

ns3.securedns.network [185.136.98.192] (4ms):

ns4.securedns.network [185.136.99.192] (0ms):

ns1.securedns.network [185.136.96.192] (0ms):

ns2.securedns.network [185.136.97.192] (0ms):

ns3.securedns.network [185.136.98.192] (0ms):

ns4.securedns.network [185.136.99.192] (0ms):

ns1.securedns.network [185.136.96.192] (0ms):

ns2.securedns.network [185.136.97.192] (0ms):

ns3.securedns.network [185.136.98.192] (4ms):

ns4.securedns.network [185.136.99.192] (0ms):

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

Previous reports for devault.cloud: 2024-05-21 18:08:46 , 2024-05-21 18:07:07 , 2024-05-21 18:04:54 , 2024-05-03 10:45:00
Blog | Cloud DNS
Sponsored by ClouDNS