DNS response history for ns1.sexual-violation.com

ns1.sexual-violation.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-24. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 433 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.sexual-violation.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

433 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:25

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.240.160.133

Most recently resolved hosting IP on selected date

Successful Responses

30

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.sexual-violation.com

Showing DNS history for 2026-08-24 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
30 2026-08-24 12:25 639231703815441688
338 ms 162.240.160.133
29 2026-08-24 12:09 639231693747052549
343 ms 162.240.160.133
28 2026-08-24 11:52 639231683712487276
344 ms 162.240.160.133
27 2026-08-24 11:35 639231673513573868
339 ms 162.240.160.133
26 2026-08-24 10:42 639231641791249939
341 ms 162.240.160.133
25 2026-08-24 10:25 639231631866211033
334 ms 162.240.160.133
24 2026-08-24 10:09 639231621644955316
343 ms 162.240.160.133
23 2026-08-24 09:52 639231611478799259
6 ms 162.240.160.133
22 2026-08-24 08:59 639231579923718211
343 ms 162.240.160.133
21 2026-08-24 08:42 639231569810702936
209 ms 162.240.160.133
20 2026-08-24 08:25 639231559762411619
332 ms 162.240.160.133
19 2026-08-24 08:08 639231549663595407
336 ms 162.240.160.133
18 2026-08-24 07:16 639231518076817246
348 ms 162.240.160.133
17 2026-08-24 06:59 639231508078650885
343 ms 162.240.160.133
16 2026-08-24 06:43 639231498210697093
2360 ms 162.240.160.133
15 2026-08-24 06:26 639231488109699360
4 ms 162.240.160.133
14 2026-08-24 05:34 639231456772510692
3 ms 162.240.160.133
13 2026-08-24 05:17 639231447084631185
206 ms 162.240.160.133
12 2026-08-24 05:01 639231437208519473
4 ms 162.240.160.133
11 2026-08-24 04:44 639231427209627490
3 ms 162.240.160.133
10 2026-08-24 03:52 639231395791246644
3 ms 162.240.160.133
9 2026-08-24 03:36 639231386075551458
343 ms 162.240.160.133
8 2026-08-24 03:19 639231376208713791
340 ms 162.240.160.133
7 2026-08-24 03:03 639231366170589276
338 ms 162.240.160.133
6 2026-08-24 02:10 639231334732159368
349 ms 162.240.160.133
5 2026-08-24 01:54 639231325035670078
3 ms 162.240.160.133
4 2026-08-24 01:37 639231315132253837
169 ms 162.240.160.133
3 2026-08-24 01:21 639231305014280808
203 ms 162.240.160.133
2 2026-08-24 00:28 639231273779380675
200 ms 162.240.160.133
1 2026-08-24 00:12 639231264180839154
4169 ms 162.240.160.133