DNS response history for ns2.copyrightinfringement.com

ns2.copyrightinfringement.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 35 DNS check records, 35 successful responses, 0 failed responses, and 371 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.copyrightinfringement.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

371 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:21

All timestamps shown in UTC

Latest Resolved IP on Selected Date

166.62.94.116

Most recently resolved hosting IP on selected date

Successful Responses

35

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.copyrightinfringement.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
35 2026-08-25 12:21 639232566381512620
188 ms 166.62.94.116
34 2026-08-25 12:04 639232556111768563
160 ms 166.62.94.116
33 2026-08-25 11:47 639232545839529039
3 ms 166.62.94.116
32 2026-08-25 11:30 639232535349285207
181 ms 166.62.94.116
31 2026-08-25 11:12 639232524938080723
334 ms 166.62.94.116
30 2026-08-25 10:18 639232492740373468
153 ms 166.62.94.116
29 2026-08-25 10:01 639232482235303141
2177 ms 166.62.94.116
28 2026-08-25 09:44 639232471861770303
7 ms 166.62.94.116
27 2026-08-25 09:27 639232461630217327
305 ms 166.62.94.116
26 2026-08-25 09:09 639232451282965990
158 ms 166.62.94.116
25 2026-08-25 08:52 639232440814614938
4 ms 166.62.94.116
24 2026-08-25 08:35 639232430410720425
325 ms 166.62.94.116
23 2026-08-25 08:17 639232420003096185
293 ms 166.62.94.116
22 2026-08-25 08:00 639232409467287444
157 ms 166.62.94.116
21 2026-08-25 07:42 639232399077195997
320 ms 166.62.94.116
20 2026-08-25 07:25 639232388731528337
161 ms 166.62.94.116
19 2026-08-25 07:08 639232378288598612
56 ms 166.62.94.116
18 2026-08-25 06:14 639232346196373643
329 ms 166.62.94.116
17 2026-08-25 05:57 639232336112370741
8 ms 166.62.94.116
16 2026-08-25 05:41 639232326146508970
312 ms 166.62.94.116
15 2026-08-25 05:24 639232316189381720
2185 ms 166.62.94.116
14 2026-08-25 05:07 639232306217998913
317 ms 166.62.94.116
13 2026-08-25 04:51 639232296255744174
7 ms 166.62.94.116
12 2026-08-25 04:34 639232286095760789
309 ms 166.62.94.116
11 2026-08-25 04:17 639232276086186273
303 ms 166.62.94.116
10 2026-08-25 04:00 639232265900986425
316 ms 166.62.94.116
9 2026-08-25 03:43 639232255723518075
174 ms 166.62.94.116
8 2026-08-25 03:26 639232245484452890
159 ms 166.62.94.116
7 2026-08-25 03:09 639232235157175331
2182 ms 166.62.94.116
6 2026-08-25 02:16 639232203197189095
313 ms 166.62.94.116
5 2026-08-25 01:59 639232192844564298
313 ms 166.62.94.116
4 2026-08-25 01:41 639232182496008942
317 ms 166.62.94.116
3 2026-08-25 01:24 639232172197053132
311 ms 166.62.94.116
2 2026-08-25 00:31 639232140250307418
7 ms 166.62.94.116
1 2026-08-25 00:14 639232129927860324
155 ms 166.62.94.116