DNS response history for ns2.hftapps.com

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

33

Historical checks stored for this nameserver on selected date

Average Latency

213 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:38

All timestamps shown in UTC

Latest Resolved IP on Selected Date

206.206.127.127

Most recently resolved hosting IP on selected date

Successful Responses

33

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.hftapps.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
33 2026-08-26 10:38 639233370841350248
103 ms 206.206.127.127
32 2026-08-26 10:21 639233360361507238
203 ms 206.206.127.127
31 2026-08-26 10:03 639233350067824371
330 ms 206.206.127.127
30 2026-08-26 09:46 639233339545274518
244 ms 206.206.127.127
29 2026-08-26 09:29 639233329214918079
237 ms 206.206.127.127
28 2026-08-26 09:11 639233318749762337
220 ms 206.206.127.127
27 2026-08-26 08:54 639233308387917838
235 ms 206.206.127.127
26 2026-08-26 08:37 639233297961740122
274 ms 206.206.127.127
25 2026-08-26 08:19 639233287487159094
227 ms 206.206.127.127
24 2026-08-26 08:02 639233276995531707
191 ms 206.206.127.127
23 2026-08-26 07:44 639233266521568229
204 ms 206.206.127.127
22 2026-08-26 07:27 639233256081047431
228 ms 206.206.127.127
21 2026-08-26 06:33 639233223620132921
210 ms 206.206.127.127
20 2026-08-26 06:16 639233213287814244
208 ms 206.206.127.127
19 2026-08-26 05:58 639233202925983161
3 ms 206.206.127.127
18 2026-08-26 05:41 639233192644780696
229 ms 206.206.127.127
17 2026-08-26 05:24 639233182401183833
221 ms 206.206.127.127
16 2026-08-26 05:07 639233172074181051
256 ms 206.206.127.127
15 2026-08-26 04:50 639233161808421455
219 ms 206.206.127.127
14 2026-08-26 04:32 639233151357344052
262 ms 206.206.127.127
13 2026-08-26 04:15 639233141034116946
198 ms 206.206.127.127
12 2026-08-26 03:58 639233130828334142
272 ms 206.206.127.127
11 2026-08-26 03:41 639233120373450007
129 ms 206.206.127.127
10 2026-08-26 03:23 639233110066216193
195 ms 206.206.127.127
9 2026-08-26 02:30 639233078065410564
276 ms 206.206.127.127
8 2026-08-26 02:13 639233067787457832
254 ms 206.206.127.127
7 2026-08-26 01:56 639233057501801162
213 ms 206.206.127.127
6 2026-08-26 01:38 639233047089431703
7 ms 206.206.127.127
5 2026-08-26 01:21 639233036754790688
201 ms 206.206.127.127
4 2026-08-26 01:04 639233026412602472
215 ms 206.206.127.127
3 2026-08-26 00:47 639233016064066127
195 ms 206.206.127.127
2 2026-08-26 00:30 639233005922655772
271 ms 206.206.127.127
1 2026-08-26 00:13 639232995672256907
295 ms 206.206.127.127