DNS response history for ns1.futuring.digital

ns1.futuring.digital 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-30. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 206 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.futuring.digital.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

206 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-30 11:52

All timestamps shown in UTC

Latest Resolved IP on Selected Date

177.93.111.32

Most recently resolved hosting IP on selected date

Successful Responses

36

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.futuring.digital

Showing DNS history for 2026-08-30 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
36 2026-08-30 11:52 639236867916029489
7 ms 177.93.111.32
35 2026-08-30 11:35 639236858088772005
229 ms 177.93.111.32
34 2026-08-30 11:19 639236848158742395
402 ms 177.93.111.32
33 2026-08-30 11:02 639236838137395574
460 ms 177.93.111.32
32 2026-08-30 10:45 639236827967386881
232 ms 177.93.111.32
31 2026-08-30 10:28 639236817708615077
441 ms 177.93.111.32
30 2026-08-30 09:35 639236785770651804
573 ms 177.93.111.32
29 2026-08-30 09:18 639236775820686373
5 ms 177.93.111.32
28 2026-08-30 09:02 639236765768339082
7 ms 177.93.111.32
27 2026-08-30 08:45 639236755602384085
193 ms 177.93.111.32
26 2026-08-30 08:28 639236745600094925
5 ms 177.93.111.32
25 2026-08-30 08:11 639236735311262753
15 ms 177.93.111.32
24 2026-08-30 07:54 639236724996745235
20 ms 177.93.111.32
23 2026-08-30 07:37 639236714839899761
3 ms 177.93.111.32
22 2026-08-30 07:20 639236704748431488
313 ms 177.93.111.32
21 2026-08-30 07:03 639236694430128550
403 ms 177.93.111.32
20 2026-08-30 06:46 639236684143292417
4 ms 177.93.111.32
19 2026-08-30 06:29 639236673972499943
546 ms 177.93.111.32
18 2026-08-30 05:35 639236642126522802
408 ms 177.93.111.32
17 2026-08-30 05:19 639236632183518198
418 ms 177.93.111.32
16 2026-08-30 05:02 639236622289312589
19 ms 177.93.111.32
15 2026-08-30 04:46 639236612490676525
214 ms 177.93.111.32
14 2026-08-30 04:30 639236602582494852
415 ms 177.93.111.32
13 2026-08-30 04:13 639236592511706469
6 ms 177.93.111.32
12 2026-08-30 03:56 639236582441006869
647 ms 177.93.111.32
11 2026-08-30 03:40 639236572478785089
25 ms 177.93.111.32
10 2026-08-30 03:23 639236562556749999
198 ms 177.93.111.32
9 2026-08-30 03:06 639236552353482281
220 ms 177.93.111.32
8 2026-08-30 02:49 639236542188881607
197 ms 177.93.111.32
7 2026-08-30 02:32 639236531885440105
2 ms 177.93.111.32
6 2026-08-30 01:39 639236499922985383
3 ms 177.93.111.32
5 2026-08-30 01:22 639236489713594431
194 ms 177.93.111.32
4 2026-08-30 01:05 639236479750443901
199 ms 177.93.111.32
3 2026-08-30 00:48 639236469719936375
3 ms 177.93.111.32
2 2026-08-30 00:32 639236459579244885
192 ms 177.93.111.32
1 2026-08-30 00:15 639236449582837549
215 ms 177.93.111.32