DNS response history for ns2.seemanmx.com

ns2.seemanmx.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-30. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 173 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.seemanmx.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

173 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-30 10:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

198.136.62.111

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.seemanmx.com

Showing DNS history for 2026-08-30 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-30 10:44 639236827967386881
128 ms 198.136.62.111
31 2026-08-30 10:26 639236817708615077
5 ms 198.136.62.111
30 2026-08-30 09:33 639236785770651804
255 ms 198.136.62.111
29 2026-08-30 09:17 639236775820686373
257 ms 198.136.62.111
28 2026-08-30 09:00 639236765768339082
7 ms 198.136.62.111
27 2026-08-30 08:43 639236755602384085
254 ms 198.136.62.111
26 2026-08-30 08:26 639236745600094925
253 ms 198.136.62.111
25 2026-08-30 08:09 639236735311262753
239 ms 198.136.62.111
24 2026-08-30 07:52 639236724996745235
3 ms 198.136.62.111
23 2026-08-30 07:35 639236714839899761
255 ms 198.136.62.111
22 2026-08-30 07:18 639236704748431488
7 ms 198.136.62.111
21 2026-08-30 07:01 639236694430128550
258 ms 198.136.62.111
20 2026-08-30 06:44 639236684143292417
3 ms 198.136.62.111
19 2026-08-30 06:27 639236673972499943
254 ms 198.136.62.111
18 2026-08-30 05:34 639236642126522802
4 ms 198.136.62.111
17 2026-08-30 05:17 639236632183518198
252 ms 198.136.62.111
16 2026-08-30 05:01 639236622289312589
262 ms 198.136.62.111
15 2026-08-30 04:44 639236612490676525
134 ms 198.136.62.111
14 2026-08-30 04:28 639236602582494852
11 ms 198.136.62.111
13 2026-08-30 04:11 639236592511706469
255 ms 198.136.62.111
12 2026-08-30 03:54 639236582441006869
252 ms 198.136.62.111
11 2026-08-30 03:38 639236572478785089
254 ms 198.136.62.111
10 2026-08-30 03:21 639236562556749999
136 ms 198.136.62.111
9 2026-08-30 03:04 639236552353482281
254 ms 198.136.62.111
8 2026-08-30 02:47 639236542188881607
7 ms 198.136.62.111
7 2026-08-30 02:30 639236531885440105
256 ms 198.136.62.111
6 2026-08-30 01:37 639236499922985383
262 ms 198.136.62.111
5 2026-08-30 01:20 639236489713594431
125 ms 198.136.62.111
4 2026-08-30 01:03 639236479750443901
254 ms 198.136.62.111
3 2026-08-30 00:46 639236469719936375
132 ms 198.136.62.111
2 2026-08-30 00:30 639236459579244885
258 ms 198.136.62.111
1 2026-08-30 00:13 639236449582837549
253 ms 198.136.62.111