DNS response history for ns1.secureproxy.tokyo

ns1.secureproxy.tokyo 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 1715 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.secureproxy.tokyo.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

1715 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:55

All timestamps shown in UTC

Latest Resolved IP on Selected Date

61.123.205.43

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 ns1.secureproxy.tokyo

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:55 639231755868832964
2245 ms 61.123.205.43
32 2026-08-24 13:38 639231745628278877
2296 ms 61.123.205.43
31 2026-08-24 13:21 639231735407682062
3774 ms 61.123.205.43
30 2026-08-24 12:28 639231703815441688
209 ms 61.123.205.43
29 2026-08-24 12:12 639231693747052549
2241 ms 61.123.205.43
28 2026-08-24 11:55 639231683712487276
2245 ms 61.123.205.43
27 2026-08-24 11:38 639231673513573868
2242 ms 61.123.205.43
26 2026-08-24 10:45 639231641791249939
4 ms 61.123.205.43
25 2026-08-24 10:28 639231631866211033
3 ms 61.123.205.43
24 2026-08-24 10:12 639231621644955316
2303 ms 61.123.205.43
23 2026-08-24 09:55 639231611478799259
2348 ms 61.123.205.43
22 2026-08-24 09:02 639231579923718211
2247 ms 61.123.205.43
21 2026-08-24 08:45 639231569810702936
2318 ms 61.123.205.43
20 2026-08-24 08:28 639231559762411619
2263 ms 61.123.205.43
19 2026-08-24 08:12 639231549663595407
3 ms 61.123.205.43
18 2026-08-24 07:18 639231518076817246
3811 ms 61.123.205.43
17 2026-08-24 07:02 639231508078650885
2 ms 61.123.205.43
16 2026-08-24 06:45 639231498210697093
4247 ms 61.123.205.43
15 2026-08-24 06:29 639231488109699360
3741 ms 61.123.205.43
14 2026-08-24 05:36 639231456772510692
2009 ms 61.123.205.43
13 2026-08-24 05:20 639231447084631185
256 ms 61.123.205.43
12 2026-08-24 05:04 639231437208519473
3 ms 61.123.205.43
11 2026-08-24 04:47 639231427209627490
3740 ms 61.123.205.43
10 2026-08-24 03:54 639231395791246644
2 ms 61.123.205.43
9 2026-08-24 03:38 639231386075551458
268 ms 61.123.205.43
8 2026-08-24 03:22 639231376208713791
2326 ms 61.123.205.43
7 2026-08-24 03:06 639231366170589276
3860 ms 61.123.205.43
6 2026-08-24 02:13 639231334732159368
1747 ms 61.123.205.43
5 2026-08-24 01:57 639231325035670078
2 ms 61.123.205.43
4 2026-08-24 01:40 639231315132253837
2 ms 61.123.205.43
3 2026-08-24 01:24 639231305014280808
3828 ms 61.123.205.43
2 2026-08-24 00:31 639231273779380675
3 ms 61.123.205.43
1 2026-08-24 00:15 639231264180839154
2 ms 61.123.205.43