DNS response history for ns3.junsoft.kr

ns3.junsoft.kr is a DNS nameserver monitored by NameServerHistory. This page provides historical DNS response-time data, nameserver uptime signals, DNS latency observations, resolved IP history, successful response counts, failed response counts, and reliability indicators for this nameserver.

The selected UTC date is 2026-08-24. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 1165 ms average response time. Current selected-date status: At least one successful DNS response was recorded for the selected date.

  • Use this report to investigate historical DNS uptime and nameserver reliability.
  • Compare DNS latency changes, failed DNS checks, and response behavior over time.
  • Review the latest resolved IP address and raw DNS check history for ns3.junsoft.kr.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

1165 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

211.37.178.53

Most recently resolved hosting IP on selected date

Successful Responses

29

Checks that returned a measurable response

Failed Responses

0

Checks with no response or no returned latency

Failure Rate

0%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns3.junsoft.kr

Showing DNS history for 2026-08-24 UTC. Newest records appear first.

Latency bars are scaled to a maximum of 5000 ms for quick visual comparison.

# Query Time (UTC) Correlation ID Latency Response IP Address
29 2026-08-24 12:11 639231693747052549
1741 ms 211.37.178.53
28 2026-08-24 11:54 639231683712487276
2284 ms 211.37.178.53
27 2026-08-24 11:38 639231673513573868
1688 ms 211.37.178.53
26 2026-08-24 10:44 639231641791249939
5 ms 211.37.178.53
25 2026-08-24 10:28 639231631866211033
1687 ms 211.37.178.53
24 2026-08-24 10:11 639231621644955316
1750 ms 211.37.178.53
23 2026-08-24 09:54 639231611478799259
1740 ms 211.37.178.53
22 2026-08-24 09:01 639231579923718211
8 ms 211.37.178.53
21 2026-08-24 08:45 639231569810702936
4 ms 211.37.178.53
20 2026-08-24 08:28 639231559762411619
1674 ms 211.37.178.53
19 2026-08-24 08:11 639231549663595407
1741 ms 211.37.178.53
18 2026-08-24 07:18 639231518076817246
4 ms 211.37.178.53
17 2026-08-24 07:02 639231508078650885
1757 ms 211.37.178.53
16 2026-08-24 06:45 639231498210697093
1704 ms 211.37.178.53
15 2026-08-24 06:28 639231488109699360
1145 ms 211.37.178.53
14 2026-08-24 05:36 639231456772510692
1148 ms 211.37.178.53
13 2026-08-24 05:20 639231447084631185
1791 ms 211.37.178.53
12 2026-08-24 05:03 639231437208519473
3 ms 211.37.178.53
11 2026-08-24 04:47 639231427209627490
1749 ms 211.37.178.53
10 2026-08-24 03:54 639231395791246644
2 ms 211.37.178.53
9 2026-08-24 03:38 639231386075551458
1744 ms 211.37.178.53
8 2026-08-24 03:22 639231376208713791
1731 ms 211.37.178.53
7 2026-08-24 03:05 639231366170589276
1727 ms 211.37.178.53
6 2026-08-24 02:13 639231334732159368
3 ms 211.37.178.53
5 2026-08-24 01:56 639231325035670078
3 ms 211.37.178.53
4 2026-08-24 01:40 639231315132253837
9 ms 211.37.178.53
3 2026-08-24 01:23 639231305014280808
1369 ms 211.37.178.53
2 2026-08-24 00:31 639231273779380675
1793 ms 211.37.178.53
1 2026-08-24 00:15 639231264180839154
1782 ms 211.37.178.53