DNS audit for ik2.com created on 2026-03-25 17:36:01

PDF

1. Name servers

Name servers listed at the parent server l.gtld-servers.net:

ns1.ik2.com
ns1.ik6.net
ns1.spamflare.net
ns2.ik6.net
ns3.ik2.com

Result: 5 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 ik2.com.

2. NS records

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

Frankfurt, DE San Francisco, US Johannesburg, ZA Singapore

ns1.ik2.com [64.38.239.82] (153ms):
ns1.ik2.com
ns1.ik6.net
ns1.spamflare.net
ns2.ik6.net
ns3.ik2.com

ns1.ik6.net [45.76.132.113] (15ms):
ns1.ik2.com
ns1.ik6.net
ns1.spamflare.net
ns2.ik6.net
ns3.ik2.com

ns1.spamflare.net [185.136.96.88] (0ms):
ns1.ik2.com
ns1.ik6.net
ns1.spamflare.net
ns2.ik6.net
ns3.ik2.com

ns2.ik6.net [139.180.152.139] (164ms):
ns1.ik2.com
ns1.ik6.net
ns1.spamflare.net
ns2.ik6.net
ns3.ik2.com

ns3.ik2.com [207.81.189.178] (149ms):
ns1.ik2.com
ns1.ik6.net
ns1.spamflare.net
ns2.ik6.net
ns3.ik2.com

ns1.ik2.com [64.38.239.82] (22ms):
ns1.ik2.com
ns1.ik6.net
ns1.spamflare.net
ns2.ik6.net
ns3.ik2.com

ns1.ik6.net [45.76.132.113] (141ms):
ns1.ik2.com
ns1.ik6.net
ns1.spamflare.net
ns2.ik6.net
ns3.ik2.com

ns1.spamflare.net [185.136.96.88] (2ms):
ns1.ik2.com
ns1.ik6.net
ns1.spamflare.net
ns2.ik6.net
ns3.ik2.com

ns2.ik6.net [139.180.152.139] (186ms):
ns1.ik2.com
ns1.ik6.net
ns1.spamflare.net
ns2.ik6.net
ns3.ik2.com

ns3.ik2.com [207.81.189.178] (29ms):
ns1.ik2.com
ns1.ik6.net
ns1.spamflare.net
ns2.ik6.net
ns3.ik2.com

ns1.ik2.com [64.38.239.82] (256ms):
ns1.ik2.com
ns1.ik6.net
ns1.spamflare.net
ns2.ik6.net
ns3.ik2.com

ns1.ik6.net [45.76.132.113] (164ms):
ns1.ik2.com
ns1.ik6.net
ns1.spamflare.net
ns2.ik6.net
ns3.ik2.com

ns1.spamflare.net [185.136.96.88] (0ms):
ns1.ik2.com
ns1.ik6.net
ns1.spamflare.net
ns2.ik6.net
ns3.ik2.com

ns2.ik6.net [139.180.152.139] (308ms):
ns1.ik2.com
ns1.ik6.net
ns1.spamflare.net
ns2.ik6.net
ns3.ik2.com

ns3.ik2.com [207.81.189.178] (292ms):
ns1.ik2.com
ns1.ik6.net
ns1.spamflare.net
ns2.ik6.net
ns3.ik2.com

ns1.ik2.com [64.38.239.82] (177ms):
ns1.ik2.com
ns1.ik6.net
ns1.spamflare.net
ns2.ik6.net
ns3.ik2.com

ns1.ik6.net [45.76.132.113] (171ms):
ns1.ik2.com
ns1.ik6.net
ns1.spamflare.net
ns2.ik6.net
ns3.ik2.com

ns1.spamflare.net [185.136.96.88] (0ms):
ns1.ik2.com
ns1.ik6.net
ns1.spamflare.net
ns2.ik6.net
ns3.ik2.com

ns2.ik6.net [139.180.152.139] (0ms):
ns1.ik2.com
ns1.ik6.net
ns1.spamflare.net
ns2.ik6.net
ns3.ik2.com

ns3.ik2.com [207.81.189.178] (211ms):
ns1.ik2.com
ns1.ik6.net
ns1.spamflare.net
ns2.ik6.net
ns3.ik2.com

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.ik2.com [64.38.239.82] (151ms):
ns1.ik2.com. dns.ik2.com. 2026032409 14400 3600 1209600 86400

ns1.ik6.net [45.76.132.113] (15ms):
ns1.ik2.com. dns.ik2.com. 2026032409 14400 3600 1209600 86400

ns1.spamflare.net [185.136.96.88] (0ms):
ns1.ik2.com. dns.ik2.com. 2026032409 14400 3600 1209600 86400

ns2.ik6.net [139.180.152.139] (164ms):
ns1.ik2.com. dns.ik2.com. 2026032409 14400 3600 1209600 86400

ns3.ik2.com [207.81.189.178] (148ms):
ns1.ik2.com. dns.ik2.com. 2026032409 14400 3600 1209600 86400

San Francisco, US

ns1.ik2.com [64.38.239.82] (24ms):
ns1.ik2.com. dns.ik2.com. 2026032409 14400 3600 1209600 86400

ns1.ik6.net [45.76.132.113] (139ms):
ns1.ik2.com. dns.ik2.com. 2026032409 14400 3600 1209600 86400

ns1.spamflare.net [185.136.96.88] (1ms):
ns1.ik2.com. dns.ik2.com. 2026032409 14400 3600 1209600 86400

ns2.ik6.net [139.180.152.139] (185ms):
ns1.ik2.com. dns.ik2.com. 2026032409 14400 3600 1209600 86400

ns3.ik2.com [207.81.189.178] (28ms):
ns1.ik2.com. dns.ik2.com. 2026032409 14400 3600 1209600 86400

Johannesburg, ZA

ns1.ik2.com [64.38.239.82] (276ms):
ns1.ik2.com. dns.ik2.com. 2026032409 14400 3600 1209600 86400

ns1.ik6.net [45.76.132.113] (164ms):
ns1.ik2.com. dns.ik2.com. 2026032409 14400 3600 1209600 86400

ns1.spamflare.net [185.136.96.88] (0ms):
ns1.ik2.com. dns.ik2.com. 2026032409 14400 3600 1209600 86400

ns2.ik6.net [139.180.152.139] (308ms):
ns1.ik2.com. dns.ik2.com. 2026032409 14400 3600 1209600 86400

ns3.ik2.com [207.81.189.178] (292ms):
ns1.ik2.com. dns.ik2.com. 2026032409 14400 3600 1209600 86400

Singapore

ns1.ik2.com [64.38.239.82] (177ms):
ns1.ik2.com. dns.ik2.com. 2026032409 14400 3600 1209600 86400

ns1.ik6.net [45.76.132.113] (163ms):
ns1.ik2.com. dns.ik2.com. 2026032409 14400 3600 1209600 86400

ns1.spamflare.net [185.136.96.88] (1ms):
ns1.ik2.com. dns.ik2.com. 2026032409 14400 3600 1209600 86400

ns2.ik6.net [139.180.152.139] (0ms):
ns1.ik2.com. dns.ik2.com. 2026032409 14400 3600 1209600 86400

ns3.ik2.com [207.81.189.178] (207ms):
ns1.ik2.com. dns.ik2.com. 2026032409 14400 3600 1209600 86400

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 ik2.com

Shows how the name servers respond to requests for ik2.com

Frankfurt, DE San Francisco, US Johannesburg, ZA Singapore

ns1.ik2.com [64.38.239.82] (152ms):
64.38.239.86

ns1.ik6.net [45.76.132.113] (13ms):
64.38.239.86

ns1.spamflare.net [185.136.96.88] (0ms):
64.38.239.86

ns2.ik6.net [139.180.152.139] (154ms):
64.38.239.86

ns3.ik2.com [207.81.189.178] (144ms):
64.38.239.86

ns1.ik2.com [64.38.239.82] (21ms):
64.38.239.86

ns1.ik6.net [45.76.132.113] (145ms):
64.38.239.86

ns1.spamflare.net [185.136.96.88] (1ms):
64.38.239.86

ns2.ik6.net [139.180.152.139] (185ms):
64.38.239.86

ns3.ik2.com [207.81.189.178] (29ms):
64.38.239.86

ns1.ik2.com [64.38.239.82] (260ms):
64.38.239.86

ns1.ik6.net [45.76.132.113] (164ms):
64.38.239.86

ns1.spamflare.net [185.136.96.88] (0ms):
64.38.239.86

ns2.ik6.net [139.180.152.139] (308ms):
64.38.239.86

ns3.ik2.com [207.81.189.178] (288ms):
64.38.239.86

ns1.ik2.com [64.38.239.82] (176ms):
64.38.239.86

ns1.ik6.net [45.76.132.113] (165ms):
64.38.239.86

ns1.spamflare.net [185.136.96.88] (1ms):
64.38.239.86

ns2.ik6.net [139.180.152.139] (0ms):
64.38.239.86

ns3.ik2.com [207.81.189.178] (211ms):
64.38.239.86

5. A record distribution by location for www.ik2.com

Shows how the name servers respond to requests for www.ik2.com

Frankfurt, DE San Francisco, US Johannesburg, ZA Singapore

ns1.ik2.com [64.38.239.82] (152ms):
64.38.239.86

ns1.ik6.net [45.76.132.113] (15ms):
64.38.239.86

ns1.spamflare.net [185.136.96.88] (0ms):
64.38.239.86

ns2.ik6.net [139.180.152.139] (164ms):
64.38.239.86

ns3.ik2.com [207.81.189.178] (144ms):
64.38.239.86

ns1.ik2.com [64.38.239.82] (22ms):
64.38.239.86

ns1.ik6.net [45.76.132.113] (138ms):
64.38.239.86

ns1.spamflare.net [185.136.96.88] (1ms):
64.38.239.86

ns2.ik6.net [139.180.152.139] (185ms):
64.38.239.86

ns3.ik2.com [207.81.189.178] (29ms):
64.38.239.86

ns1.ik2.com [64.38.239.82] (256ms):
64.38.239.86

ns1.ik6.net [45.76.132.113] (160ms):
64.38.239.86

ns1.spamflare.net [185.136.96.88] (0ms):
64.38.239.86

ns2.ik6.net [139.180.152.139] (316ms):
64.38.239.86

ns3.ik2.com [207.81.189.178] (292ms):
64.38.239.86

ns1.ik2.com [64.38.239.82] (176ms):
64.38.239.86

ns1.ik6.net [45.76.132.113] (188ms):
64.38.239.86

ns1.spamflare.net [185.136.96.88] (1ms):
64.38.239.86

ns2.ik6.net [139.180.152.139] (0ms):
64.38.239.86

ns3.ik2.com [207.81.189.178] (211ms):
64.38.239.86

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

Previous reports for ik2.com: 2026-03-25 04:33:53 , 2026-03-24 04:38:21 , 2026-03-24 03:19:29
Newer reports for ik2.com: 2026-03-29 19:44:30 , 2026-04-09 07:23:37 , 2026-04-09 07:26:43 , 2026-04-11 19:13:45
Blog | Cloud DNS
Sponsored by ClouDNS