DNS audit for tiskan.is created on 2026-05-07 17:16:31
1. Name servers
Name servers listed at the parent server e.nic.is:
ns1.cloudns.netns2.cloudns.net
ns4.cloudns.net
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 tiskan.is.
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.cloudns.net [85.159.233.17] (8ms):
ns2.cloudns.net [5.161.86.199] (91ms):
ns4.cloudns.net [185.206.180.171] (0ms): |
ns1.cloudns.net [85.159.233.17] (139ms):
ns2.cloudns.net [5.161.86.199] (60ms):
ns4.cloudns.net [185.206.180.171] (151ms): |
ns1.cloudns.net [85.159.233.17] (275ms):
ns2.cloudns.net [5.161.86.199] (217ms):
ns4.cloudns.net [185.206.180.171] (244ms): |
ns1.cloudns.net [85.159.233.17] (180ms):
ns2.cloudns.net [5.161.86.199] (216ms):
ns4.cloudns.net [185.206.180.171] (184ms): |
ns1.cloudns.net [85.159.233.17] (164ms):
ns2.cloudns.net [5.161.86.199] (249ms):
ns4.cloudns.net [185.206.180.171] (153ms): |
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.cloudns.net [85.159.233.17] (8ms):
ns2.cloudns.net [5.161.86.199] (91ms):
ns4.cloudns.net [185.206.180.171] (0ms): |
| San Francisco, US |
|---|
|
ns1.cloudns.net [85.159.233.17] (144ms):
ns2.cloudns.net [5.161.86.199] (62ms):
ns4.cloudns.net [185.206.180.171] (148ms): |
| Sydney, AU |
|---|
|
ns1.cloudns.net [85.159.233.17] (266ms):
ns2.cloudns.net [5.161.86.199] (218ms):
ns4.cloudns.net [185.206.180.171] (244ms): |
| Johannesburg, ZA |
|---|
|
ns1.cloudns.net [85.159.233.17] (176ms):
ns2.cloudns.net [5.161.86.199] (212ms):
ns4.cloudns.net [185.206.180.171] (164ms): |
| Singapore |
|---|
|
ns1.cloudns.net [85.159.233.17] (164ms):
ns2.cloudns.net [5.161.86.199] (230ms):
ns4.cloudns.net [185.206.180.171] (162ms): |
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 tiskan.is
Shows how the name servers respond to requests for tiskan.is
| Frankfurt, DE | San Francisco, US | Sydney, AU | Johannesburg, ZA | Singapore |
|---|---|---|---|---|
|
ns1.cloudns.net [85.159.233.17] (8ms):
ns2.cloudns.net [5.161.86.199] (92ms):
ns4.cloudns.net [185.206.180.171] (0ms): |
ns1.cloudns.net [85.159.233.17] (141ms):
ns2.cloudns.net [5.161.86.199] (60ms):
ns4.cloudns.net [185.206.180.171] (145ms): |
ns1.cloudns.net [85.159.233.17] (254ms):
ns2.cloudns.net [5.161.86.199] (217ms):
ns4.cloudns.net [185.206.180.171] (244ms): |
ns1.cloudns.net [85.159.233.17] (176ms):
ns2.cloudns.net [5.161.86.199] (212ms):
ns4.cloudns.net [185.206.180.171] (184ms): |
ns1.cloudns.net [85.159.233.17] (156ms):
ns2.cloudns.net [5.161.86.199] (247ms):
ns4.cloudns.net [185.206.180.171] (152ms): |
5. A record distribution by location for www.tiskan.is
Shows how the name servers respond to requests for www.tiskan.is
| Frankfurt, DE | San Francisco, US | Sydney, AU | Johannesburg, ZA | Singapore |
|---|---|---|---|---|
|
ns1.cloudns.net [85.159.233.17] (8ms):
ns2.cloudns.net [5.161.86.199] (91ms):
ns4.cloudns.net [185.206.180.171] (0ms): |
ns1.cloudns.net [85.159.233.17] (140ms):
ns2.cloudns.net [5.161.86.199] (62ms):
ns4.cloudns.net [185.206.180.171] (150ms): |
ns1.cloudns.net [85.159.233.17] (276ms):
ns2.cloudns.net [5.161.86.199] (217ms):
ns4.cloudns.net [185.206.180.171] (244ms): |
ns1.cloudns.net [85.159.233.17] (176ms):
ns2.cloudns.net [5.161.86.199] (212ms):
ns4.cloudns.net [185.206.180.171] (188ms): |
ns1.cloudns.net [85.159.233.17] (157ms):
ns2.cloudns.net [5.161.86.199] (243ms):
ns4.cloudns.net [185.206.180.171] (154ms): |
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 153.27ms.
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.