DNS response history for ns.100hp.kr

ns.100hp.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-25. For this date, NameServerHistory found 39 DNS check records, 39 successful responses, 0 failed responses, and 515 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 ns.100hp.kr.
Records on Selected Date

39

Historical checks stored for this nameserver on selected date

Average Latency

515 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

49.247.9.158

Most recently resolved hosting IP on selected date

Successful Responses

39

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 ns.100hp.kr

Showing DNS history for 2026-08-25 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
39 2026-08-25 13:17 639232597643611557
511 ms 49.247.9.158
38 2026-08-25 12:59 639232587225721862
514 ms 49.247.9.158
37 2026-08-25 12:42 639232576780683689
496 ms 49.247.9.158
36 2026-08-25 12:25 639232566381512620
525 ms 49.247.9.158
35 2026-08-25 12:07 639232556111768563
535 ms 49.247.9.158
34 2026-08-25 11:50 639232545839529039
773 ms 49.247.9.158
33 2026-08-25 11:33 639232535349285207
490 ms 49.247.9.158
32 2026-08-25 11:15 639232524938080723
544 ms 49.247.9.158
31 2026-08-25 10:22 639232492740373468
507 ms 49.247.9.158
30 2026-08-25 10:05 639232482235303141
553 ms 49.247.9.158
29 2026-08-25 09:47 639232471861770303
517 ms 49.247.9.158
28 2026-08-25 09:30 639232461630217327
504 ms 49.247.9.158
27 2026-08-25 09:13 639232451282965990
506 ms 49.247.9.158
26 2026-08-25 08:55 639232440814614938
544 ms 49.247.9.158
25 2026-08-25 08:38 639232430410720425
484 ms 49.247.9.158
24 2026-08-25 08:21 639232420003096185
512 ms 49.247.9.158
23 2026-08-25 08:03 639232409467287444
514 ms 49.247.9.158
22 2026-08-25 07:46 639232399077195997
511 ms 49.247.9.158
21 2026-08-25 07:28 639232388731528337
530 ms 49.247.9.158
20 2026-08-25 07:11 639232378288598612
538 ms 49.247.9.158
19 2026-08-25 06:17 639232346196373643
542 ms 49.247.9.158
18 2026-08-25 06:00 639232336112370741
502 ms 49.247.9.158
17 2026-08-25 05:44 639232326146508970
533 ms 49.247.9.158
16 2026-08-25 05:27 639232316189381720
522 ms 49.247.9.158
15 2026-08-25 05:11 639232306217998913
502 ms 49.247.9.158
14 2026-08-25 04:54 639232296255744174
525 ms 49.247.9.158
13 2026-08-25 04:37 639232286095760789
228 ms 49.247.9.158
12 2026-08-25 04:20 639232276086186273
503 ms 49.247.9.158
11 2026-08-25 04:04 639232265900986425
511 ms 49.247.9.158
10 2026-08-25 03:47 639232255723518075
528 ms 49.247.9.158
9 2026-08-25 03:30 639232245484452890
496 ms 49.247.9.158
8 2026-08-25 03:13 639232235157175331
526 ms 49.247.9.158
7 2026-08-25 02:19 639232203197189095
508 ms 49.247.9.158
6 2026-08-25 02:02 639232192844564298
520 ms 49.247.9.158
5 2026-08-25 01:45 639232182496008942
526 ms 49.247.9.158
4 2026-08-25 01:27 639232172197053132
525 ms 49.247.9.158
3 2026-08-25 00:34 639232140250307418
535 ms 49.247.9.158
2 2026-08-25 00:17 639232129927860324
451 ms 49.247.9.158
1 2026-08-25 00:00 639232119551972438
503 ms 49.247.9.158