DNS audit for remo.to created on 2026-03-13 21:28:01

PDF

1. Name servers

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

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 remo.to.

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

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] (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] (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] (92ms):
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] (0ms):
pns31.cloudns.net
pns32.cloudns.net
pns33.cloudns.net
pns34.cloudns.net

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

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

pns31.cloudns.net [185.136.96.66] (1ms):
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] (0ms):
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

Frankfurt, DE

pns31.cloudns.net [185.136.96.66] (0ms):
pns31.cloudns.net. dns.remo.to. 2026030801 7200 1800 1209600 300

pns32.cloudns.net [185.136.97.66] (0ms):
pns31.cloudns.net. dns.remo.to. 2026030801 7200 1800 1209600 300

pns33.cloudns.net [185.136.98.66] (0ms):
pns31.cloudns.net. dns.remo.to. 2026030801 7200 1800 1209600 300

pns34.cloudns.net [185.136.99.66] (0ms):
pns31.cloudns.net. dns.remo.to. 2026030801 7200 1800 1209600 300

San Francisco, US

pns31.cloudns.net [185.136.96.66] (1ms):
pns31.cloudns.net. dns.remo.to. 2026030801 7200 1800 1209600 300

pns32.cloudns.net [185.136.97.66] (1ms):
pns31.cloudns.net. dns.remo.to. 2026030801 7200 1800 1209600 300

pns33.cloudns.net [185.136.98.66] (1ms):
pns31.cloudns.net. dns.remo.to. 2026030801 7200 1800 1209600 300

pns34.cloudns.net [185.136.99.66] (1ms):
pns31.cloudns.net. dns.remo.to. 2026030801 7200 1800 1209600 300

Sydney, AU

pns31.cloudns.net [185.136.96.66] (0ms):
pns31.cloudns.net. dns.remo.to. 2026030801 7200 1800 1209600 300

pns32.cloudns.net [185.136.97.66] (93ms):
pns31.cloudns.net. dns.remo.to. 2026030801 7200 1800 1209600 300

pns33.cloudns.net [185.136.98.66] (1ms):
pns31.cloudns.net. dns.remo.to. 2026030801 7200 1800 1209600 300

pns34.cloudns.net [185.136.99.66] (1ms):
pns31.cloudns.net. dns.remo.to. 2026030801 7200 1800 1209600 300

Johannesburg, ZA

pns31.cloudns.net [185.136.96.66] (0ms):
pns31.cloudns.net. dns.remo.to. 2026030801 7200 1800 1209600 300

pns32.cloudns.net [185.136.97.66] (0ms):
pns31.cloudns.net. dns.remo.to. 2026030801 7200 1800 1209600 300

pns33.cloudns.net [185.136.98.66] (0ms):
pns31.cloudns.net. dns.remo.to. 2026030801 7200 1800 1209600 300

pns34.cloudns.net [185.136.99.66] (0ms):
pns31.cloudns.net. dns.remo.to. 2026030801 7200 1800 1209600 300

Singapore

pns31.cloudns.net [185.136.96.66] (1ms):
pns31.cloudns.net. dns.remo.to. 2026030801 7200 1800 1209600 300

pns32.cloudns.net [185.136.97.66] (0ms):
pns31.cloudns.net. dns.remo.to. 2026030801 7200 1800 1209600 300

pns33.cloudns.net [185.136.98.66] (1ms):
pns31.cloudns.net. dns.remo.to. 2026030801 7200 1800 1209600 300

pns34.cloudns.net [185.136.99.66] (1ms):
pns31.cloudns.net. dns.remo.to. 2026030801 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 remo.to

Shows how the name servers respond to requests for remo.to

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

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

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

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

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

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

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

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

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

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

pns32.cloudns.net [185.136.97.66] (92ms):
185.206.180.130
185.206.180.178

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

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

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

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

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

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

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

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

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

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

5. A record distribution by location for www.remo.to

Shows how the name servers respond to requests for www.remo.to

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

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

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

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

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

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

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

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

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

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

pns32.cloudns.net [185.136.97.66] (92ms):
185.206.180.130
185.206.180.178

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

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

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

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

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

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

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

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

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

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

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

Previous reports for remo.to: 2022-03-23 00:11:32 , 2022-03-22 23:20:55 , 2020-03-25 22:57:45 , 2020-03-25 22:42:52
Blog | Cloud DNS
Sponsored by ClouDNS