DNS response history for ns2.aminalborz.com

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

29

Historical checks stored for this nameserver on selected date

Average Latency

199 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:02

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.116.161.126

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.aminalborz.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
29 2026-08-24 12:02 639231693747052549
194 ms 185.116.161.126
28 2026-08-24 11:46 639231683712487276
20 ms 185.116.161.126
27 2026-08-24 11:29 639231673513573868
182 ms 185.116.161.126
26 2026-08-24 10:36 639231641791249939
116 ms 185.116.161.126
25 2026-08-24 10:19 639231631866211033
79 ms 185.116.161.126
24 2026-08-24 10:02 639231621644955316
173 ms 185.116.161.126
23 2026-08-24 09:45 639231611478799259
22 ms 185.116.161.126
22 2026-08-24 08:53 639231579923718211
83 ms 185.116.161.126
21 2026-08-24 08:36 639231569810702936
132 ms 185.116.161.126
20 2026-08-24 08:19 639231559762411619
197 ms 185.116.161.126
19 2026-08-24 08:02 639231549663595407
168 ms 185.116.161.126
18 2026-08-24 07:10 639231518076817246
2012 ms 185.116.161.126
17 2026-08-24 06:53 639231508078650885
180 ms 185.116.161.126
16 2026-08-24 06:36 639231498210697093
181 ms 185.116.161.126
15 2026-08-24 06:20 639231488109699360
159 ms 185.116.161.126
14 2026-08-24 05:28 639231456772510692
131 ms 185.116.161.126
13 2026-08-24 05:11 639231447084631185
3 ms 185.116.161.126
12 2026-08-24 04:55 639231437208519473
352 ms 185.116.161.126
11 2026-08-24 04:38 639231427209627490
192 ms 185.116.161.126
10 2026-08-24 03:46 639231395791246644
180 ms 185.116.161.126
9 2026-08-24 03:30 639231386075551458
191 ms 185.116.161.126
8 2026-08-24 03:13 639231376208713791
105 ms 185.116.161.126
7 2026-08-24 02:57 639231366170589276
201 ms 185.116.161.126
6 2026-08-24 02:04 639231334732159368
21 ms 185.116.161.126
5 2026-08-24 01:48 639231325035670078
205 ms 185.116.161.126
4 2026-08-24 01:31 639231315132253837
19 ms 185.116.161.126
3 2026-08-24 01:15 639231305014280808
99 ms 185.116.161.126
2 2026-08-24 00:23 639231273779380675
174 ms 185.116.161.126
1 2026-08-24 00:07 639231264180839154
3 ms 185.116.161.126