DNS response history for ns3.futuresplans.com

ns3.futuresplans.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-27. For this date, NameServerHistory found 31 DNS check records, 31 successful responses, 0 failed responses, and 126 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 ns3.futuresplans.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

126 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 09:59

All timestamps shown in UTC

Latest Resolved IP on Selected Date

46.225.51.149

Most recently resolved hosting IP on selected date

Successful Responses

31

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 ns3.futuresplans.com

Showing DNS history for 2026-08-27 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
31 2026-08-27 09:59 639234212558002823
50 ms 46.225.51.149
30 2026-08-27 09:42 639234202117531850
27 ms 46.225.51.149
29 2026-08-27 09:25 639234191649612722
35 ms 46.225.51.149
28 2026-08-27 09:07 639234181105879568
45 ms 46.225.51.149
27 2026-08-27 08:50 639234170713214496
49 ms 46.225.51.149
26 2026-08-27 08:32 639234160341037652
2058 ms 46.225.51.149
25 2026-08-27 08:15 639234149799404224
54 ms 46.225.51.149
24 2026-08-27 07:58 639234139553286469
72 ms 46.225.51.149
23 2026-08-27 07:04 639234107183588293
188 ms 46.225.51.149
22 2026-08-27 06:47 639234096905435724
22 ms 46.225.51.149
21 2026-08-27 06:30 639234086579410775
42 ms 46.225.51.149
20 2026-08-27 06:12 639234076291157956
4 ms 46.225.51.149
19 2026-08-27 05:55 639234065981939454
82 ms 46.225.51.149
18 2026-08-27 05:38 639234055548642997
42 ms 46.225.51.149
17 2026-08-27 05:21 639234045267979603
25 ms 46.225.51.149
16 2026-08-27 05:04 639234034999717463
50 ms 46.225.51.149
15 2026-08-27 04:46 639234024739225358
41 ms 46.225.51.149
14 2026-08-27 04:29 639234014311170162
35 ms 46.225.51.149
13 2026-08-27 04:12 639234003806017640
50 ms 46.225.51.149
12 2026-08-27 03:54 639233993356203030
42 ms 46.225.51.149
11 2026-08-27 03:01 639233961301716608
40 ms 46.225.51.149
10 2026-08-27 02:44 639233950834200647
72 ms 46.225.51.149
9 2026-08-27 02:26 639233940431849026
45 ms 46.225.51.149
8 2026-08-27 02:09 639233930110596398
330 ms 46.225.51.149
7 2026-08-27 01:51 639233919705434540
21 ms 46.225.51.149
6 2026-08-27 01:34 639233909452807845
43 ms 46.225.51.149
5 2026-08-27 01:17 639233899096420820
25 ms 46.225.51.149
4 2026-08-27 01:00 639233888707824939
117 ms 46.225.51.149
3 2026-08-27 00:43 639233878461203802
32 ms 46.225.51.149
2 2026-08-27 00:25 639233868060868209
42 ms 46.225.51.149
1 2026-08-27 00:08 639233857450922991
138 ms 46.225.51.149