DNS response history for ns2.divorceandbaillawyer.com

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

28

Historical checks stored for this nameserver on selected date

Average Latency

465 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 11:49

All timestamps shown in UTC

Latest Resolved IP on Selected Date

38.45.94.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.divorceandbaillawyer.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
28 2026-08-24 11:49 639231683712487276
303 ms 38.45.94.139
27 2026-08-24 11:32 639231673513573868
302 ms 38.45.94.139
26 2026-08-24 10:39 639231641791249939
291 ms 38.45.94.139
25 2026-08-24 10:23 639231631866211033
295 ms 38.45.94.139
24 2026-08-24 10:06 639231621644955316
32 ms 38.45.94.139
23 2026-08-24 09:49 639231611478799259
288 ms 38.45.94.139
22 2026-08-24 08:56 639231579923718211
386 ms 38.45.94.139
21 2026-08-24 08:40 639231569810702936
7 ms 38.45.94.139
20 2026-08-24 08:23 639231559762411619
285 ms 38.45.94.139
19 2026-08-24 08:06 639231549663595407
2171 ms 38.45.94.139
18 2026-08-24 07:13 639231518076817246
182 ms 38.45.94.139
17 2026-08-24 06:57 639231508078650885
4296 ms 38.45.94.139
16 2026-08-24 06:40 639231498210697093
354 ms 38.45.94.139
15 2026-08-24 06:24 639231488109699360
4 ms 38.45.94.139
14 2026-08-24 05:31 639231456772510692
7 ms 38.45.94.139
13 2026-08-24 05:15 639231447084631185
3 ms 38.45.94.139
12 2026-08-24 04:58 639231437208519473
314 ms 38.45.94.139
11 2026-08-24 04:42 639231427209627490
3 ms 38.45.94.139
10 2026-08-24 03:49 639231395791246644
3 ms 38.45.94.139
9 2026-08-24 03:33 639231386075551458
293 ms 38.45.94.139
8 2026-08-24 03:17 639231376208713791
285 ms 38.45.94.139
7 2026-08-24 03:00 639231366170589276
302 ms 38.45.94.139
6 2026-08-24 02:08 639231334732159368
3 ms 38.45.94.139
5 2026-08-24 01:51 639231325035670078
4 ms 38.45.94.139
4 2026-08-24 01:35 639231315132253837
2007 ms 38.45.94.139
3 2026-08-24 01:18 639231305014280808
283 ms 38.45.94.139
2 2026-08-24 00:26 639231273779380675
4 ms 38.45.94.139
1 2026-08-24 00:10 639231264180839154
304 ms 38.45.94.139