DNS response history for ns2.best-houston-lawyer.com

ns2.best-houston-lawyer.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-28. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 357 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.best-houston-lawyer.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

357 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 14:51

All timestamps shown in UTC

Latest Resolved IP on Selected Date

50.87.152.200

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.best-houston-lawyer.com

Showing DNS history for 2026-08-28 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-28 14:51 639235248596087996
179 ms 50.87.152.200
34 2026-08-28 14:33 639235238225955920
4 ms 50.87.152.200
33 2026-08-28 14:16 639235227727862105
340 ms 50.87.152.200
32 2026-08-28 13:22 639235195230848570
3 ms 50.87.152.200
31 2026-08-28 13:05 639235184840503274
164 ms 50.87.152.200
30 2026-08-28 12:47 639235174453894956
3 ms 50.87.152.200
29 2026-08-28 12:30 639235163898672622
346 ms 50.87.152.200
28 2026-08-28 11:37 639235132147470568
337 ms 50.87.152.200
27 2026-08-28 11:20 639235121907744088
166 ms 50.87.152.200
26 2026-08-28 11:02 639235111428014262
2171 ms 50.87.152.200
25 2026-08-28 10:45 639235100921813626
351 ms 50.87.152.200
24 2026-08-28 09:51 639235068670703481
2285 ms 50.87.152.200
23 2026-08-28 09:34 639235058337459445
330 ms 50.87.152.200
22 2026-08-28 09:16 639235047825109146
174 ms 50.87.152.200
21 2026-08-28 08:59 639235037383229033
168 ms 50.87.152.200
20 2026-08-28 08:06 639235005619242711
328 ms 50.87.152.200
19 2026-08-28 07:49 639234995310346584
335 ms 50.87.152.200
18 2026-08-28 07:31 639234984946548933
332 ms 50.87.152.200
17 2026-08-28 07:14 639234974608077290
335 ms 50.87.152.200
16 2026-08-28 06:21 639234942529845595
370 ms 50.87.152.200
15 2026-08-28 06:04 639234932259126627
168 ms 50.87.152.200
14 2026-08-28 05:46 639234921916735988
337 ms 50.87.152.200
13 2026-08-28 05:29 639234911470038027
161 ms 50.87.152.200
12 2026-08-28 04:36 639234879588411654
167 ms 50.87.152.200
11 2026-08-28 04:19 639234869341589104
168 ms 50.87.152.200
10 2026-08-28 04:02 639234859012216675
245 ms 50.87.152.200
9 2026-08-28 03:44 639234848695364934
331 ms 50.87.152.200
8 2026-08-28 02:51 639234816952458162
331 ms 50.87.152.200
7 2026-08-28 02:35 639234806773081598
161 ms 50.87.152.200
6 2026-08-28 02:17 639234796382955255
328 ms 50.87.152.200
5 2026-08-28 02:00 639234786015782563
346 ms 50.87.152.200
4 2026-08-28 01:06 639234753811917646
170 ms 50.87.152.200
3 2026-08-28 00:49 639234743739767811
335 ms 50.87.152.200
2 2026-08-28 00:32 639234733372362811
167 ms 50.87.152.200
1 2026-08-28 00:15 639234723048550337
348 ms 50.87.152.200