DNS response history for ns2.courtdocs.co

ns2.courtdocs.co 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 28 DNS check records, 28 successful responses, 0 failed responses, and 377 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.courtdocs.co.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

377 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

50.6.171.139

Most recently resolved hosting IP on selected date

Successful Responses

28

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.courtdocs.co

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
28 2026-08-25 09:43 639232471861770303
2098 ms 50.6.171.139
27 2026-08-25 09:26 639232461630217327
143 ms 50.6.171.139
26 2026-08-25 09:09 639232451282965990
201 ms 50.6.171.139
25 2026-08-25 08:52 639232440814614938
762 ms 50.6.171.139
24 2026-08-25 08:34 639232430410720425
199 ms 50.6.171.139
23 2026-08-25 08:17 639232420003096185
199 ms 50.6.171.139
22 2026-08-25 08:00 639232409467287444
204 ms 50.6.171.139
21 2026-08-25 07:42 639232399077195997
193 ms 50.6.171.139
20 2026-08-25 07:25 639232388731528337
199 ms 50.6.171.139
19 2026-08-25 07:07 639232378288598612
209 ms 50.6.171.139
18 2026-08-25 06:14 639232346196373643
33 ms 50.6.171.139
17 2026-08-25 05:57 639232336112370741
199 ms 50.6.171.139
16 2026-08-25 05:40 639232326146508970
159 ms 50.6.171.139
15 2026-08-25 05:24 639232316189381720
32 ms 50.6.171.139
14 2026-08-25 05:07 639232306217998913
7 ms 50.6.171.139
13 2026-08-25 04:51 639232296255744174
126 ms 50.6.171.139
12 2026-08-25 04:34 639232286095760789
7 ms 50.6.171.139
11 2026-08-25 04:17 639232276086186273
2009 ms 50.6.171.139
10 2026-08-25 04:00 639232265900986425
32 ms 50.6.171.139
9 2026-08-25 03:43 639232255723518075
315 ms 50.6.171.139
8 2026-08-25 03:26 639232245484452890
105 ms 50.6.171.139
7 2026-08-25 03:09 639232235157175331
199 ms 50.6.171.139
6 2026-08-25 02:16 639232203197189095
199 ms 50.6.171.139
5 2026-08-25 01:58 639232192844564298
166 ms 50.6.171.139
4 2026-08-25 01:41 639232182496008942
204 ms 50.6.171.139
3 2026-08-25 01:24 639232172197053132
198 ms 50.6.171.139
2 2026-08-25 00:31 639232140250307418
2153 ms 50.6.171.139
1 2026-08-25 00:14 639232129927860324
3 ms 50.6.171.139