DNS response history for ns1.planhnd.org

ns1.planhnd.org 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 27 DNS check records, 27 successful responses, 0 failed responses, and 303 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 ns1.planhnd.org.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

303 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:56

All timestamps shown in UTC

Latest Resolved IP on Selected Date

50.116.107.132

Most recently resolved hosting IP on selected date

Successful Responses

27

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 ns1.planhnd.org

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
27 2026-08-26 08:56 639233308387917838
121 ms 50.116.107.132
26 2026-08-26 08:38 639233297961740122
255 ms 50.116.107.132
25 2026-08-26 08:21 639233287487159094
9 ms 50.116.107.132
24 2026-08-26 08:04 639233276995531707
33 ms 50.116.107.132
23 2026-08-26 07:46 639233266521568229
502 ms 50.116.107.132
22 2026-08-26 07:29 639233256081047431
192 ms 50.116.107.132
21 2026-08-26 06:35 639233223620132921
372 ms 50.116.107.132
20 2026-08-26 06:17 639233213287814244
2124 ms 50.116.107.132
19 2026-08-26 06:00 639233202925983161
113 ms 50.116.107.132
18 2026-08-26 05:43 639233192644780696
361 ms 50.116.107.132
17 2026-08-26 05:26 639233182401183833
375 ms 50.116.107.132
16 2026-08-26 05:09 639233172074181051
150 ms 50.116.107.132
15 2026-08-26 04:51 639233161808421455
243 ms 50.116.107.132
14 2026-08-26 04:34 639233151357344052
604 ms 50.116.107.132
13 2026-08-26 04:17 639233141034116946
374 ms 50.116.107.132
12 2026-08-26 04:00 639233130828334142
119 ms 50.116.107.132
11 2026-08-26 03:43 639233120373450007
362 ms 50.116.107.132
10 2026-08-26 03:25 639233110066216193
378 ms 50.116.107.132
9 2026-08-26 02:32 639233078065410564
135 ms 50.116.107.132
8 2026-08-26 02:15 639233067787457832
118 ms 50.116.107.132
7 2026-08-26 01:58 639233057501801162
246 ms 50.116.107.132
6 2026-08-26 01:40 639233047089431703
120 ms 50.116.107.132
5 2026-08-26 01:23 639233036754790688
129 ms 50.116.107.132
4 2026-08-26 01:06 639233026412602472
252 ms 50.116.107.132
3 2026-08-26 00:49 639233016064066127
253 ms 50.116.107.132
2 2026-08-26 00:32 639233005922655772
127 ms 50.116.107.132
1 2026-08-26 00:15 639232995672256907
121 ms 50.116.107.132