DNS response history for ns2.milfsone.top

ns2.milfsone.top 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 30 DNS check records, 30 successful responses, 0 failed responses, and 219 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.milfsone.top.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

219 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:18

All timestamps shown in UTC

Latest Resolved IP on Selected Date

212.32.236.83

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 ns2.milfsone.top

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
30 2026-08-24 12:18 639231703815441688
146 ms 212.32.236.83
29 2026-08-24 12:01 639231693747052549
58 ms 212.32.236.83
28 2026-08-24 11:44 639231683712487276
44 ms 212.32.236.83
27 2026-08-24 11:27 639231673513573868
140 ms 212.32.236.83
26 2026-08-24 10:34 639231641791249939
86 ms 212.32.236.83
25 2026-08-24 10:18 639231631866211033
23 ms 212.32.236.83
24 2026-08-24 10:01 639231621644955316
63 ms 212.32.236.83
23 2026-08-24 09:44 639231611478799259
383 ms 212.32.236.83
22 2026-08-24 08:51 639231579923718211
24 ms 212.32.236.83
21 2026-08-24 08:34 639231569810702936
22 ms 212.32.236.83
20 2026-08-24 08:17 639231559762411619
112 ms 212.32.236.83
19 2026-08-24 08:01 639231549663595407
61 ms 212.32.236.83
18 2026-08-24 07:08 639231518076817246
31 ms 212.32.236.83
17 2026-08-24 06:52 639231508078650885
122 ms 212.32.236.83
16 2026-08-24 06:35 639231498210697093
66 ms 212.32.236.83
15 2026-08-24 06:18 639231488109699360
72 ms 212.32.236.83
14 2026-08-24 05:26 639231456772510692
3 ms 212.32.236.83
13 2026-08-24 05:10 639231447084631185
4 ms 212.32.236.83
12 2026-08-24 04:53 639231437208519473
121 ms 212.32.236.83
11 2026-08-24 04:37 639231427209627490
50 ms 212.32.236.83
10 2026-08-24 03:44 639231395791246644
60 ms 212.32.236.83
9 2026-08-24 03:28 639231386075551458
50 ms 212.32.236.83
8 2026-08-24 03:12 639231376208713791
18 ms 212.32.236.83
7 2026-08-24 02:55 639231366170589276
53 ms 212.32.236.83
6 2026-08-24 02:03 639231334732159368
2056 ms 212.32.236.83
5 2026-08-24 01:46 639231325035670078
4 ms 212.32.236.83
4 2026-08-24 01:30 639231315132253837
576 ms 212.32.236.83
3 2026-08-24 01:13 639231305014280808
2032 ms 212.32.236.83
2 2026-08-24 00:21 639231273779380675
62 ms 212.32.236.83
1 2026-08-24 00:05 639231264180839154
30 ms 212.32.236.83