DNS response history for ns1.mo3dy.com

ns1.mo3dy.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 33 DNS check records, 33 successful responses, 0 failed responses, and 289 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.mo3dy.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

289 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.0.233.73

Most recently resolved hosting IP on selected date

Successful Responses

33

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.mo3dy.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
33 2026-08-25 11:34 639232535349285207
173 ms 162.0.233.73
32 2026-08-25 11:16 639232524938080723
325 ms 162.0.233.73
31 2026-08-25 10:22 639232492740373468
314 ms 162.0.233.73
30 2026-08-25 10:05 639232482235303141
318 ms 162.0.233.73
29 2026-08-25 09:48 639232471861770303
298 ms 162.0.233.73
28 2026-08-25 09:30 639232461630217327
291 ms 162.0.233.73
27 2026-08-25 09:13 639232451282965990
285 ms 162.0.233.73
26 2026-08-25 08:56 639232440814614938
301 ms 162.0.233.73
25 2026-08-25 08:39 639232430410720425
322 ms 162.0.233.73
24 2026-08-25 08:21 639232420003096185
320 ms 162.0.233.73
23 2026-08-25 08:04 639232409467287444
288 ms 162.0.233.73
22 2026-08-25 07:46 639232399077195997
295 ms 162.0.233.73
21 2026-08-25 07:29 639232388731528337
311 ms 162.0.233.73
20 2026-08-25 07:12 639232378288598612
321 ms 162.0.233.73
19 2026-08-25 06:18 639232346196373643
309 ms 162.0.233.73
18 2026-08-25 06:01 639232336112370741
148 ms 162.0.233.73
17 2026-08-25 05:44 639232326146508970
294 ms 162.0.233.73
16 2026-08-25 05:28 639232316189381720
319 ms 162.0.233.73
15 2026-08-25 05:11 639232306217998913
302 ms 162.0.233.73
14 2026-08-25 04:54 639232296255744174
320 ms 162.0.233.73
13 2026-08-25 04:38 639232286095760789
170 ms 162.0.233.73
12 2026-08-25 04:21 639232276086186273
308 ms 162.0.233.73
11 2026-08-25 04:04 639232265900986425
312 ms 162.0.233.73
10 2026-08-25 03:47 639232255723518075
301 ms 162.0.233.73
9 2026-08-25 03:30 639232245484452890
300 ms 162.0.233.73
8 2026-08-25 03:13 639232235157175331
303 ms 162.0.233.73
7 2026-08-25 02:20 639232203197189095
308 ms 162.0.233.73
6 2026-08-25 02:03 639232192844564298
314 ms 162.0.233.73
5 2026-08-25 01:45 639232182496008942
301 ms 162.0.233.73
4 2026-08-25 01:28 639232172197053132
307 ms 162.0.233.73
3 2026-08-25 00:34 639232140250307418
150 ms 162.0.233.73
2 2026-08-25 00:18 639232129927860324
307 ms 162.0.233.73
1 2026-08-25 00:00 639232119551972438
304 ms 162.0.233.73