DNS response history for ns3.in-depth.com

ns3.in-depth.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 396 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 ns3.in-depth.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

396 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

65.49.9.95

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 ns3.in-depth.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
317 ms 65.49.9.95
33 2026-08-25 11:47 639232545839529039
314 ms 65.49.9.95
32 2026-08-25 11:30 639232535349285207
165 ms 65.49.9.95
31 2026-08-25 11:12 639232524938080723
316 ms 65.49.9.95
30 2026-08-25 10:18 639232492740373468
313 ms 65.49.9.95
29 2026-08-25 10:01 639232482235303141
318 ms 65.49.9.95
28 2026-08-25 09:44 639232471861770303
314 ms 65.49.9.95
27 2026-08-25 09:27 639232461630217327
2210 ms 65.49.9.95
26 2026-08-25 09:09 639232451282965990
2203 ms 65.49.9.95
25 2026-08-25 08:52 639232440814614938
321 ms 65.49.9.95
24 2026-08-25 08:35 639232430410720425
318 ms 65.49.9.95
23 2026-08-25 08:17 639232420003096185
160 ms 65.49.9.95
22 2026-08-25 08:00 639232409467287444
319 ms 65.49.9.95
21 2026-08-25 07:42 639232399077195997
319 ms 65.49.9.95
20 2026-08-25 07:25 639232388731528337
171 ms 65.49.9.95
19 2026-08-25 07:08 639232378288598612
172 ms 65.49.9.95
18 2026-08-25 06:14 639232346196373643
308 ms 65.49.9.95
17 2026-08-25 05:57 639232336112370741
309 ms 65.49.9.95
16 2026-08-25 05:41 639232326146508970
307 ms 65.49.9.95
15 2026-08-25 05:24 639232316189381720
304 ms 65.49.9.95
14 2026-08-25 05:07 639232306217998913
303 ms 65.49.9.95
13 2026-08-25 04:51 639232296255744174
161 ms 65.49.9.95
12 2026-08-25 04:34 639232286095760789
306 ms 65.49.9.95
11 2026-08-25 04:17 639232276086186273
308 ms 65.49.9.95
10 2026-08-25 04:00 639232265900986425
305 ms 65.49.9.95
9 2026-08-25 03:43 639232255723518075
166 ms 65.49.9.95
8 2026-08-25 03:26 639232245484452890
304 ms 65.49.9.95
7 2026-08-25 03:09 639232235157175331
303 ms 65.49.9.95
6 2026-08-25 02:16 639232203197189095
310 ms 65.49.9.95
5 2026-08-25 01:59 639232192844564298
301 ms 65.49.9.95
4 2026-08-25 01:41 639232182496008942
301 ms 65.49.9.95
3 2026-08-25 01:24 639232172197053132
306 ms 65.49.9.95
2 2026-08-25 00:31 639232140250307418
305 ms 65.49.9.95
1 2026-08-25 00:14 639232129927860324
305 ms 65.49.9.95