DNS response history for ns2.sexualassaultlegal.com

ns2.sexualassaultlegal.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-29. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 408 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.sexualassaultlegal.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

408 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-29 11:41

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

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 ns2.sexualassaultlegal.com

Showing DNS history for 2026-08-29 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-29 11:41 639235997602806960
175 ms 162.240.160.133
32 2026-08-29 11:24 639235987487833458
354 ms 162.240.160.133
31 2026-08-29 11:07 639235977211002296
174 ms 162.240.160.133
30 2026-08-29 10:50 639235966864596836
359 ms 162.240.160.133
29 2026-08-29 10:33 639235956590882003
347 ms 162.240.160.133
28 2026-08-29 09:39 639235924465736791
225 ms 162.240.160.133
27 2026-08-29 09:22 639235914430611197
356 ms 162.240.160.133
26 2026-08-29 09:05 639235904343784853
4 ms 162.240.160.133
25 2026-08-29 08:49 639235894201078068
175 ms 162.240.160.133
24 2026-08-29 08:32 639235884233447452
3 ms 162.240.160.133
23 2026-08-29 08:15 639235874142207309
178 ms 162.240.160.133
22 2026-08-29 07:58 639235863974652466
345 ms 162.240.160.133
21 2026-08-29 07:41 639235853716243436
2008 ms 162.240.160.133
20 2026-08-29 07:24 639235843614494759
4 ms 162.240.160.133
19 2026-08-29 07:07 639235833401459551
360 ms 162.240.160.133
18 2026-08-29 06:50 639235823220464528
364 ms 162.240.160.133
17 2026-08-29 06:33 639235812997510905
374 ms 162.240.160.133
16 2026-08-29 05:40 639235781101962521
3 ms 162.240.160.133
15 2026-08-29 05:23 639235771207673260
356 ms 162.240.160.133
14 2026-08-29 05:07 639235761047429642
184 ms 162.240.160.133
13 2026-08-29 04:50 639235750964347246
181 ms 162.240.160.133
12 2026-08-29 04:33 639235740923490874
11 ms 162.240.160.133
11 2026-08-29 04:16 639235730842894399
176 ms 162.240.160.133
10 2026-08-29 04:00 639235720760084717
348 ms 162.240.160.133
9 2026-08-29 03:43 639235710843666743
2196 ms 162.240.160.133
8 2026-08-29 03:26 639235700733510561
385 ms 162.240.160.133
7 2026-08-29 03:09 639235690509906192
422 ms 162.240.160.133
6 2026-08-29 02:52 639235680156673501
907 ms 162.240.160.133
5 2026-08-29 02:35 639235669720606443
372 ms 162.240.160.133
4 2026-08-29 01:41 639235637451417084
804 ms 162.240.160.133
3 2026-08-29 01:24 639235627307383453
691 ms 162.240.160.133
2 2026-08-29 01:07 639235616906386856
211 ms 162.240.160.133
1 2026-08-29 00:49 639235606582912691
397 ms 162.240.160.133