DNS response history for ns4.dmaxwebs.com

ns4.dmaxwebs.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 29 DNS check records, 29 successful responses, 0 failed responses, and 502 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 ns4.dmaxwebs.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

502 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:02

All timestamps shown in UTC

Latest Resolved IP on Selected Date

49.12.105.164

Most recently resolved hosting IP on selected date

Successful Responses

29

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 ns4.dmaxwebs.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
29 2026-08-24 12:02 639231693747052549
2036 ms 49.12.105.164
28 2026-08-24 11:45 639231683712487276
13 ms 49.12.105.164
27 2026-08-24 11:28 639231673513573868
16 ms 49.12.105.164
26 2026-08-24 10:35 639231641791249939
11 ms 49.12.105.164
25 2026-08-24 10:19 639231631866211033
68 ms 49.12.105.164
24 2026-08-24 10:02 639231621644955316
2034 ms 49.12.105.164
23 2026-08-24 09:45 639231611478799259
11 ms 49.12.105.164
22 2026-08-24 08:53 639231579923718211
44 ms 49.12.105.164
21 2026-08-24 08:36 639231569810702936
10 ms 49.12.105.164
20 2026-08-24 08:19 639231559762411619
2043 ms 49.12.105.164
19 2026-08-24 08:02 639231549663595407
13 ms 49.12.105.164
18 2026-08-24 07:09 639231518076817246
10 ms 49.12.105.164
17 2026-08-24 06:53 639231508078650885
8 ms 49.12.105.164
16 2026-08-24 06:36 639231498210697093
12 ms 49.12.105.164
15 2026-08-24 06:20 639231488109699360
14 ms 49.12.105.164
14 2026-08-24 05:27 639231456772510692
47 ms 49.12.105.164
13 2026-08-24 05:11 639231447084631185
5 ms 49.12.105.164
12 2026-08-24 04:55 639231437208519473
5 ms 49.12.105.164
11 2026-08-24 04:38 639231427209627490
2031 ms 49.12.105.164
10 2026-08-24 03:46 639231395791246644
4 ms 49.12.105.164
9 2026-08-24 03:29 639231386075551458
12 ms 49.12.105.164
8 2026-08-24 03:13 639231376208713791
7 ms 49.12.105.164
7 2026-08-24 02:56 639231366170589276
2017 ms 49.12.105.164
6 2026-08-24 02:04 639231334732159368
6 ms 49.12.105.164
5 2026-08-24 01:48 639231325035670078
7 ms 49.12.105.164
4 2026-08-24 01:31 639231315132253837
2019 ms 49.12.105.164
3 2026-08-24 01:14 639231305014280808
2016 ms 49.12.105.164
2 2026-08-24 00:22 639231273779380675
16 ms 49.12.105.164
1 2026-08-24 00:06 639231264180839154
26 ms 49.12.105.164