DNS response history for ns1.laviladomus.com

ns1.laviladomus.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 30 DNS check records, 30 successful responses, 0 failed responses, and 293 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.laviladomus.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

293 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:14

All timestamps shown in UTC

Latest Resolved IP on Selected Date

213.165.93.251

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.laviladomus.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
30 2026-08-25 10:14 639232492740373468
89 ms 213.165.93.251
29 2026-08-25 09:57 639232482235303141
11 ms 213.165.93.251
28 2026-08-25 09:39 639232471861770303
94 ms 213.165.93.251
27 2026-08-25 09:22 639232461630217327
105 ms 213.165.93.251
26 2026-08-25 09:05 639232451282965990
103 ms 213.165.93.251
25 2026-08-25 08:48 639232440814614938
18 ms 213.165.93.251
24 2026-08-25 08:30 639232430410720425
194 ms 213.165.93.251
23 2026-08-25 08:13 639232420003096185
40 ms 213.165.93.251
22 2026-08-25 07:56 639232409467287444
2045 ms 213.165.93.251
21 2026-08-25 07:38 639232399077195997
96 ms 213.165.93.251
20 2026-08-25 07:21 639232388731528337
86 ms 213.165.93.251
19 2026-08-25 07:03 639232378288598612
2079 ms 213.165.93.251
18 2026-08-25 06:10 639232346196373643
27 ms 213.165.93.251
17 2026-08-25 05:53 639232336112370741
195 ms 213.165.93.251
16 2026-08-25 05:37 639232326146508970
125 ms 213.165.93.251
15 2026-08-25 05:20 639232316189381720
92 ms 213.165.93.251
14 2026-08-25 05:03 639232306217998913
2 ms 213.165.93.251
13 2026-08-25 04:47 639232296255744174
93 ms 213.165.93.251
12 2026-08-25 04:30 639232286095760789
88 ms 213.165.93.251
11 2026-08-25 04:13 639232276086186273
158 ms 213.165.93.251
10 2026-08-25 03:56 639232265900986425
113 ms 213.165.93.251
9 2026-08-25 03:39 639232255723518075
77 ms 213.165.93.251
8 2026-08-25 03:22 639232245484452890
104 ms 213.165.93.251
7 2026-08-25 03:05 639232235157175331
91 ms 213.165.93.251
6 2026-08-25 02:12 639232203197189095
176 ms 213.165.93.251
5 2026-08-25 01:54 639232192844564298
2075 ms 213.165.93.251
4 2026-08-25 01:37 639232182496008942
103 ms 213.165.93.251
3 2026-08-25 01:20 639232172197053132
96 ms 213.165.93.251
2 2026-08-25 00:27 639232140250307418
77 ms 213.165.93.251
1 2026-08-25 00:10 639232129927860324
152 ms 213.165.93.251