DNS response history for ns2.allhunt.com

ns2.allhunt.com 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 29 DNS check records, 29 successful responses, 0 failed responses, and 281 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 ns2.allhunt.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

281 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:31

All timestamps shown in UTC

Latest Resolved IP on Selected Date

64.22.104.138

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 ns2.allhunt.com

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
29 2026-08-26 09:31 639233329214918079
152 ms 64.22.104.138
28 2026-08-26 09:13 639233318749762337
253 ms 64.22.104.138
27 2026-08-26 08:56 639233308387917838
253 ms 64.22.104.138
26 2026-08-26 08:39 639233297961740122
246 ms 64.22.104.138
25 2026-08-26 08:21 639233287487159094
152 ms 64.22.104.138
24 2026-08-26 08:04 639233276995531707
164 ms 64.22.104.138
23 2026-08-26 07:46 639233266521568229
131 ms 64.22.104.138
22 2026-08-26 07:29 639233256081047431
2202 ms 64.22.104.138
21 2026-08-26 06:35 639233223620132921
254 ms 64.22.104.138
20 2026-08-26 06:18 639233213287814244
245 ms 64.22.104.138
19 2026-08-26 06:00 639233202925983161
242 ms 64.22.104.138
18 2026-08-26 05:43 639233192644780696
239 ms 64.22.104.138
17 2026-08-26 05:26 639233182401183833
277 ms 64.22.104.138
16 2026-08-26 05:09 639233172074181051
17 ms 64.22.104.138
15 2026-08-26 04:52 639233161808421455
248 ms 64.22.104.138
14 2026-08-26 04:34 639233151357344052
241 ms 64.22.104.138
13 2026-08-26 04:17 639233141034116946
9 ms 64.22.104.138
12 2026-08-26 04:00 639233130828334142
152 ms 64.22.104.138
11 2026-08-26 03:43 639233120373450007
154 ms 64.22.104.138
10 2026-08-26 03:25 639233110066216193
253 ms 64.22.104.138
9 2026-08-26 02:32 639233078065410564
246 ms 64.22.104.138
8 2026-08-26 02:15 639233067787457832
282 ms 64.22.104.138
7 2026-08-26 01:58 639233057501801162
243 ms 64.22.104.138
6 2026-08-26 01:41 639233047089431703
245 ms 64.22.104.138
5 2026-08-26 01:23 639233036754790688
238 ms 64.22.104.138
4 2026-08-26 01:06 639233026412602472
238 ms 64.22.104.138
3 2026-08-26 00:49 639233016064066127
264 ms 64.22.104.138
2 2026-08-26 00:32 639233005922655772
251 ms 64.22.104.138
1 2026-08-26 00:15 639232995672256907
249 ms 64.22.104.138