DNS response history for ns1.minally.com

ns1.minally.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-25. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 425 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.minally.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

425 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:15

All timestamps shown in UTC

Latest Resolved IP on Selected Date

94.102.9.110

Most recently resolved hosting IP on selected date

Successful Responses

30

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.minally.com

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
30 2026-08-25 10:15 639232492740373468
211 ms 94.102.9.110
29 2026-08-25 09:57 639232482235303141
138 ms 94.102.9.110
28 2026-08-25 09:40 639232471861770303
256 ms 94.102.9.110
27 2026-08-25 09:23 639232461630217327
207 ms 94.102.9.110
26 2026-08-25 09:06 639232451282965990
189 ms 94.102.9.110
25 2026-08-25 08:48 639232440814614938
193 ms 94.102.9.110
24 2026-08-25 08:31 639232430410720425
182 ms 94.102.9.110
23 2026-08-25 08:13 639232420003096185
208 ms 94.102.9.110
22 2026-08-25 07:56 639232409467287444
863 ms 94.102.9.110
21 2026-08-25 07:39 639232399077195997
441 ms 94.102.9.110
20 2026-08-25 07:21 639232388731528337
378 ms 94.102.9.110
19 2026-08-25 07:04 639232378288598612
420 ms 94.102.9.110
18 2026-08-25 06:10 639232346196373643
9 ms 94.102.9.110
17 2026-08-25 05:54 639232336112370741
618 ms 94.102.9.110
16 2026-08-25 05:37 639232326146508970
253 ms 94.102.9.110
15 2026-08-25 05:20 639232316189381720
442 ms 94.102.9.110
14 2026-08-25 05:04 639232306217998913
375 ms 94.102.9.110
13 2026-08-25 04:47 639232296255744174
238 ms 94.102.9.110
12 2026-08-25 04:30 639232286095760789
307 ms 94.102.9.110
11 2026-08-25 04:13 639232276086186273
40 ms 94.102.9.110
10 2026-08-25 03:57 639232265900986425
763 ms 94.102.9.110
9 2026-08-25 03:40 639232255723518075
7 ms 94.102.9.110
8 2026-08-25 03:23 639232245484452890
2305 ms 94.102.9.110
7 2026-08-25 03:05 639232235157175331
625 ms 94.102.9.110
6 2026-08-25 02:12 639232203197189095
282 ms 94.102.9.110
5 2026-08-25 01:55 639232192844564298
340 ms 94.102.9.110
4 2026-08-25 01:38 639232182496008942
137 ms 94.102.9.110
3 2026-08-25 01:20 639232172197053132
119 ms 94.102.9.110
2 2026-08-25 00:27 639232140250307418
33 ms 94.102.9.110
1 2026-08-25 00:10 639232129927860324
2182 ms 94.102.9.110