DNS response history for ns2.maxberendsohnoficial.com

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

32

Historical checks stored for this nameserver on selected date

Average Latency

493 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:22

All timestamps shown in UTC

Latest Resolved IP on Selected Date

76.13.173.161

Most recently resolved hosting IP on selected date

Successful Responses

32

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.maxberendsohnoficial.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
32 2026-08-27 10:22 639234222943951923
364 ms 76.13.173.161
31 2026-08-27 10:05 639234212558002823
174 ms 76.13.173.161
30 2026-08-27 09:47 639234202117531850
219 ms 76.13.173.161
29 2026-08-27 09:30 639234191649612722
252 ms 76.13.173.161
28 2026-08-27 09:12 639234181105879568
358 ms 76.13.173.161
27 2026-08-27 08:55 639234170713214496
355 ms 76.13.173.161
26 2026-08-27 08:37 639234160341037652
359 ms 76.13.173.161
25 2026-08-27 08:20 639234149799404224
354 ms 76.13.173.161
24 2026-08-27 08:02 639234139553286469
355 ms 76.13.173.161
23 2026-08-27 07:09 639234107183588293
2300 ms 76.13.173.161
22 2026-08-27 06:52 639234096905435724
8 ms 76.13.173.161
21 2026-08-27 06:35 639234086579410775
3 ms 76.13.173.161
20 2026-08-27 06:17 639234076291157956
345 ms 76.13.173.161
19 2026-08-27 06:00 639234065981939454
353 ms 76.13.173.161
18 2026-08-27 05:43 639234055548642997
346 ms 76.13.173.161
17 2026-08-27 05:26 639234045267979603
351 ms 76.13.173.161
16 2026-08-27 05:09 639234034999717463
8 ms 76.13.173.161
15 2026-08-27 04:51 639234024739225358
2 ms 76.13.173.161
14 2026-08-27 04:34 639234014311170162
352 ms 76.13.173.161
13 2026-08-27 04:17 639234003806017640
347 ms 76.13.173.161
12 2026-08-27 03:59 639233993356203030
176 ms 76.13.173.161
11 2026-08-27 03:06 639233961301716608
2242 ms 76.13.173.161
10 2026-08-27 02:49 639233950834200647
3 ms 76.13.173.161
9 2026-08-27 02:31 639233940431849026
349 ms 76.13.173.161
8 2026-08-27 02:14 639233930110596398
349 ms 76.13.173.161
7 2026-08-27 01:57 639233919705434540
349 ms 76.13.173.161
6 2026-08-27 01:39 639233909452807845
8 ms 76.13.173.161
5 2026-08-27 01:22 639233899096420820
358 ms 76.13.173.161
4 2026-08-27 01:05 639233888707824939
2240 ms 76.13.173.161
3 2026-08-27 00:48 639233878461203802
32 ms 76.13.173.161
2 2026-08-27 00:30 639233868060868209
223 ms 76.13.173.161
1 2026-08-27 00:13 639233857450922991
2251 ms 76.13.173.161