DNS response history for ns3.365auto.co.kr

ns3.365auto.co.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-26. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 1260 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.365auto.co.kr.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

1260 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:46

All timestamps shown in UTC

Latest Resolved IP on Selected Date

116.126.143.225

Most recently resolved hosting IP on selected date

Successful Responses

34

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.365auto.co.kr

Showing DNS history for 2026-08-26 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
34 2026-08-26 10:46 639233370841350248
1306 ms 116.126.143.225
33 2026-08-26 10:29 639233360361507238
1385 ms 116.126.143.225
32 2026-08-26 10:12 639233350067824371
1258 ms 116.126.143.225
31 2026-08-26 09:55 639233339545274518
1403 ms 116.126.143.225
30 2026-08-26 09:37 639233329214918079
1390 ms 116.126.143.225
29 2026-08-26 09:20 639233318749762337
1390 ms 116.126.143.225
28 2026-08-26 09:02 639233308387917838
1637 ms 116.126.143.225
27 2026-08-26 08:45 639233297961740122
1620 ms 116.126.143.225
26 2026-08-26 08:28 639233287487159094
1279 ms 116.126.143.225
25 2026-08-26 08:10 639233276995531707
1254 ms 116.126.143.225
24 2026-08-26 07:53 639233266521568229
1294 ms 116.126.143.225
23 2026-08-26 07:35 639233256081047431
1402 ms 116.126.143.225
22 2026-08-26 06:41 639233223620132921
1283 ms 116.126.143.225
21 2026-08-26 06:24 639233213287814244
1371 ms 116.126.143.225
20 2026-08-26 06:07 639233202925983161
1270 ms 116.126.143.225
19 2026-08-26 05:49 639233192644780696
1146 ms 116.126.143.225
18 2026-08-26 05:32 639233182401183833
1162 ms 116.126.143.225
17 2026-08-26 05:15 639233172074181051
1193 ms 116.126.143.225
16 2026-08-26 04:58 639233161808421455
1376 ms 116.126.143.225
15 2026-08-26 04:41 639233151357344052
1273 ms 116.126.143.225
14 2026-08-26 04:23 639233141034116946
1159 ms 116.126.143.225
13 2026-08-26 04:06 639233130828334142
1160 ms 116.126.143.225
12 2026-08-26 03:49 639233120373450007
1148 ms 116.126.143.225
11 2026-08-26 03:32 639233110066216193
1174 ms 116.126.143.225
10 2026-08-26 02:38 639233078065410564
594 ms 116.126.143.225
9 2026-08-26 02:21 639233067787457832
1278 ms 116.126.143.225
8 2026-08-26 02:04 639233057501801162
1292 ms 116.126.143.225
7 2026-08-26 01:47 639233047089431703
1413 ms 116.126.143.225
6 2026-08-26 01:30 639233036754790688
1189 ms 116.126.143.225
5 2026-08-26 01:12 639233026412602472
1162 ms 116.126.143.225
4 2026-08-26 00:55 639233016064066127
1162 ms 116.126.143.225
3 2026-08-26 00:38 639233005922655772
919 ms 116.126.143.225
2 2026-08-26 00:21 639232995672256907
1164 ms 116.126.143.225
1 2026-08-26 00:04 639232985300872416
1336 ms 116.126.143.225