DNS response history for ns2.safelyremove.com

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

33

Historical checks stored for this nameserver on selected date

Average Latency

586 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:48

All timestamps shown in UTC

Latest Resolved IP on Selected Date

67.222.6.154

Most recently resolved hosting IP on selected date

Successful Responses

33

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.safelyremove.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
33 2026-08-24 13:48 639231755868832964
160 ms 67.222.6.154
32 2026-08-24 13:31 639231745628278877
2111 ms 67.222.6.154
31 2026-08-24 13:14 639231735407682062
217 ms 67.222.6.154
30 2026-08-24 12:21 639231703815441688
142 ms 67.222.6.154
29 2026-08-24 12:05 639231693747052549
2112 ms 67.222.6.154
28 2026-08-24 11:48 639231683712487276
2107 ms 67.222.6.154
27 2026-08-24 11:31 639231673513573868
223 ms 67.222.6.154
26 2026-08-24 10:38 639231641791249939
2135 ms 67.222.6.154
25 2026-08-24 10:22 639231631866211033
242 ms 67.222.6.154
24 2026-08-24 10:05 639231621644955316
108 ms 67.222.6.154
23 2026-08-24 09:48 639231611478799259
222 ms 67.222.6.154
22 2026-08-24 08:55 639231579923718211
7 ms 67.222.6.154
21 2026-08-24 08:38 639231569810702936
218 ms 67.222.6.154
20 2026-08-24 08:21 639231559762411619
228 ms 67.222.6.154
19 2026-08-24 08:05 639231549663595407
222 ms 67.222.6.154
18 2026-08-24 07:12 639231518076817246
159 ms 67.222.6.154
17 2026-08-24 06:56 639231508078650885
230 ms 67.222.6.154
16 2026-08-24 06:39 639231498210697093
220 ms 67.222.6.154
15 2026-08-24 06:22 639231488109699360
2288 ms 67.222.6.154
14 2026-08-24 05:30 639231456772510692
4 ms 67.222.6.154
13 2026-08-24 05:14 639231447084631185
225 ms 67.222.6.154
12 2026-08-24 04:57 639231437208519473
2158 ms 67.222.6.154
11 2026-08-24 04:41 639231427209627490
4 ms 67.222.6.154
10 2026-08-24 03:48 639231395791246644
14 ms 67.222.6.154
9 2026-08-24 03:32 639231386075551458
224 ms 67.222.6.154
8 2026-08-24 03:16 639231376208713791
211 ms 67.222.6.154
7 2026-08-24 02:59 639231366170589276
116 ms 67.222.6.154
6 2026-08-24 02:07 639231334732159368
2044 ms 67.222.6.154
5 2026-08-24 01:50 639231325035670078
214 ms 67.222.6.154
4 2026-08-24 01:34 639231315132253837
220 ms 67.222.6.154
3 2026-08-24 01:17 639231305014280808
223 ms 67.222.6.154
2 2026-08-24 00:25 639231273779380675
125 ms 67.222.6.154
1 2026-08-24 00:09 639231264180839154
219 ms 67.222.6.154