DNS response history for ns2.miraizenlegal.com

ns2.miraizenlegal.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-24. For this date, NameServerHistory found 35 DNS check records, 34 successful responses, 1 failed responses, and 759 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.miraizenlegal.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

759 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:56

All timestamps shown in UTC

Latest Resolved IP on Selected Date

5.56.59.125

Most recently resolved hosting IP on selected date

Successful Responses

34

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.miraizenlegal.com

Showing DNS history for 2026-08-24 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
35 2026-08-24 14:56 639231797631669865
2028 ms 5.56.59.125
34 2026-08-24 14:03 639231765923559455
51 ms 5.56.59.125
33 2026-08-24 13:46 639231755868832964
80 ms 5.56.59.125
32 2026-08-24 13:30 639231745628278877
2045 ms 5.56.59.125
31 2026-08-24 13:12 639231735407682062
95 ms 5.56.59.125
30 2026-08-24 12:20 639231703815441688
108 ms 5.56.59.125
29 2026-08-24 12:03 639231693747052549
2009 ms 5.56.59.125
28 2026-08-24 11:46 639231683712487276
2104 ms 5.56.59.125
27 2026-08-24 11:29 639231673513573868
65 ms 5.56.59.125
26 2026-08-24 10:36 639231641791249939
80 ms 5.56.59.125
25 2026-08-24 10:20 639231631866211033
106 ms 5.56.59.125
24 2026-08-24 10:03 639231621644955316
72 ms 5.56.59.125
23 2026-08-24 09:46 639231611478799259
14 ms 5.56.59.125
22 2026-08-24 08:53 639231579923718211
2009 ms 5.56.59.125
21 2026-08-24 08:36 639231569810702936
32 ms 5.56.59.125
20 2026-08-24 08:19 639231559762411619
83 ms 5.56.59.125
19 2026-08-24 08:03 639231549663595407
52 ms 5.56.59.125
18 2026-08-24 07:10 639231518076817246
107 ms 5.56.59.125
17 2026-08-24 06:54 639231508078650885
17 ms 5.56.59.125
16 2026-08-24 06:37 639231498210697093
2017 ms 5.56.59.125
15 2026-08-24 06:20 639231488109699360
24 ms 5.56.59.125
14 2026-08-24 05:28 639231456772510692
4 ms 5.56.59.125
13 2026-08-24 05:12 639231447084631185
2026 ms 5.56.59.125
12 2026-08-24 04:55 639231437208519473
2053 ms 5.56.59.125
11 2026-08-24 04:39 639231427209627490
70 ms 5.56.59.125
10 2026-08-24 03:46 639231395791246644
2052 ms 5.56.59.125
9 2026-08-24 03:30 639231386075551458
82 ms 5.56.59.125
8 2026-08-24 03:14 639231376208713791
9 ms 5.56.59.125
7 2026-08-24 02:57 639231366170589276
2039 ms 5.56.59.125
6 2026-08-24 02:05 639231334732159368
-
5 2026-08-24 01:48 639231325035670078
66 ms 5.56.59.125
4 2026-08-24 01:32 639231315132253837
2065 ms 5.56.59.125
3 2026-08-24 01:15 639231305014280808
7 ms 5.56.59.125
2 2026-08-24 00:23 639231273779380675
2056 ms 5.56.59.125
1 2026-08-24 00:07 639231264180839154
92 ms 5.56.59.125