DNS response history for ns1.seemkt.com

ns1.seemkt.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 331 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.seemkt.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

331 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:06

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.51.158.114

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 ns1.seemkt.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:06 639231693747052549
158 ms 209.51.158.114
28 2026-08-24 11:49 639231683712487276
235 ms 209.51.158.114
27 2026-08-24 11:32 639231673513573868
113 ms 209.51.158.114
26 2026-08-24 10:39 639231641791249939
119 ms 209.51.158.114
25 2026-08-24 10:23 639231631866211033
237 ms 209.51.158.114
24 2026-08-24 10:06 639231621644955316
228 ms 209.51.158.114
23 2026-08-24 09:49 639231611478799259
240 ms 209.51.158.114
22 2026-08-24 08:56 639231579923718211
2112 ms 209.51.158.114
21 2026-08-24 08:39 639231569810702936
224 ms 209.51.158.114
20 2026-08-24 08:22 639231559762411619
226 ms 209.51.158.114
19 2026-08-24 08:06 639231549663595407
235 ms 209.51.158.114
18 2026-08-24 07:13 639231518076817246
120 ms 209.51.158.114
17 2026-08-24 06:57 639231508078650885
113 ms 209.51.158.114
16 2026-08-24 06:40 639231498210697093
233 ms 209.51.158.114
15 2026-08-24 06:23 639231488109699360
236 ms 209.51.158.114
14 2026-08-24 05:31 639231456772510692
147 ms 209.51.158.114
13 2026-08-24 05:15 639231447084631185
2134 ms 209.51.158.114
12 2026-08-24 04:58 639231437208519473
248 ms 209.51.158.114
11 2026-08-24 04:42 639231427209627490
241 ms 209.51.158.114
10 2026-08-24 03:49 639231395791246644
234 ms 209.51.158.114
9 2026-08-24 03:33 639231386075551458
118 ms 209.51.158.114
8 2026-08-24 03:17 639231376208713791
237 ms 209.51.158.114
7 2026-08-24 03:00 639231366170589276
244 ms 209.51.158.114
6 2026-08-24 02:08 639231334732159368
228 ms 209.51.158.114
5 2026-08-24 01:51 639231325035670078
121 ms 209.51.158.114
4 2026-08-24 01:35 639231315132253837
232 ms 209.51.158.114
3 2026-08-24 01:18 639231305014280808
235 ms 209.51.158.114
2 2026-08-24 00:26 639231273779380675
116 ms 209.51.158.114
1 2026-08-24 00:10 639231264180839154
242 ms 209.51.158.114