DNS response history for ns2.wdnottm.com

ns2.wdnottm.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-25. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 298 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.wdnottm.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

298 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:04

All timestamps shown in UTC

Latest Resolved IP on Selected Date

108.179.225.129

Most recently resolved hosting IP on selected date

Successful Responses

34

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

Showing DNS history for 2026-08-25 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
34 2026-08-25 12:04 639232556111768563
119 ms 108.179.225.129
33 2026-08-25 11:47 639232545839529039
120 ms 108.179.225.129
32 2026-08-25 11:30 639232535349285207
232 ms 108.179.225.129
31 2026-08-25 11:13 639232524938080723
5 ms 108.179.225.129
30 2026-08-25 10:19 639232492740373468
240 ms 108.179.225.129
29 2026-08-25 10:02 639232482235303141
247 ms 108.179.225.129
28 2026-08-25 09:44 639232471861770303
118 ms 108.179.225.129
27 2026-08-25 09:27 639232461630217327
118 ms 108.179.225.129
26 2026-08-25 09:10 639232451282965990
241 ms 108.179.225.129
25 2026-08-25 08:52 639232440814614938
116 ms 108.179.225.129
24 2026-08-25 08:35 639232430410720425
117 ms 108.179.225.129
23 2026-08-25 08:18 639232420003096185
235 ms 108.179.225.129
22 2026-08-25 08:00 639232409467287444
37 ms 108.179.225.129
21 2026-08-25 07:43 639232399077195997
253 ms 108.179.225.129
20 2026-08-25 07:26 639232388731528337
239 ms 108.179.225.129
19 2026-08-25 07:08 639232378288598612
246 ms 108.179.225.129
18 2026-08-25 06:14 639232346196373643
237 ms 108.179.225.129
17 2026-08-25 05:58 639232336112370741
240 ms 108.179.225.129
16 2026-08-25 05:41 639232326146508970
237 ms 108.179.225.129
15 2026-08-25 05:24 639232316189381720
119 ms 108.179.225.129
14 2026-08-25 05:08 639232306217998913
2236 ms 108.179.225.129
13 2026-08-25 04:51 639232296255744174
2210 ms 108.179.225.129
12 2026-08-25 04:34 639232286095760789
237 ms 108.179.225.129
11 2026-08-25 04:17 639232276086186273
120 ms 108.179.225.129
10 2026-08-25 04:01 639232265900986425
239 ms 108.179.225.129
9 2026-08-25 03:44 639232255723518075
121 ms 108.179.225.129
8 2026-08-25 03:27 639232245484452890
236 ms 108.179.225.129
7 2026-08-25 03:10 639232235157175331
233 ms 108.179.225.129
6 2026-08-25 02:16 639232203197189095
241 ms 108.179.225.129
5 2026-08-25 01:59 639232192844564298
236 ms 108.179.225.129
4 2026-08-25 01:42 639232182496008942
237 ms 108.179.225.129
3 2026-08-25 01:25 639232172197053132
9 ms 108.179.225.129
2 2026-08-25 00:31 639232140250307418
115 ms 108.179.225.129
1 2026-08-25 00:14 639232129927860324
135 ms 108.179.225.129