DNS response history for ns2.iniguezabogados.com

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

29

Historical checks stored for this nameserver on selected date

Average Latency

405 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:51

All timestamps shown in UTC

Latest Resolved IP on Selected Date

5.56.59.125

Most recently resolved hosting IP on selected date

Successful Responses

29

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.iniguezabogados.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
29 2026-08-25 09:51 639232482235303141
2049 ms 5.56.59.125
28 2026-08-25 09:33 639232471861770303
31 ms 5.56.59.125
27 2026-08-25 09:16 639232461630217327
90 ms 5.56.59.125
26 2026-08-25 08:59 639232451282965990
76 ms 5.56.59.125
25 2026-08-25 08:42 639232440814614938
105 ms 5.56.59.125
24 2026-08-25 08:24 639232430410720425
2011 ms 5.56.59.125
23 2026-08-25 08:07 639232420003096185
51 ms 5.56.59.125
22 2026-08-25 07:49 639232409467287444
71 ms 5.56.59.125
21 2026-08-25 07:32 639232399077195997
79 ms 5.56.59.125
20 2026-08-25 07:15 639232388731528337
66 ms 5.56.59.125
19 2026-08-25 06:57 639232378288598612
108 ms 5.56.59.125
18 2026-08-25 06:04 639232346196373643
86 ms 5.56.59.125
17 2026-08-25 05:47 639232336112370741
2039 ms 5.56.59.125
16 2026-08-25 05:30 639232326146508970
81 ms 5.56.59.125
15 2026-08-25 05:14 639232316189381720
101 ms 5.56.59.125
14 2026-08-25 04:57 639232306217998913
38 ms 5.56.59.125
13 2026-08-25 04:41 639232296255744174
2014 ms 5.56.59.125
12 2026-08-25 04:24 639232286095760789
79 ms 5.56.59.125
11 2026-08-25 04:07 639232276086186273
87 ms 5.56.59.125
10 2026-08-25 03:50 639232265900986425
42 ms 5.56.59.125
9 2026-08-25 03:33 639232255723518075
30 ms 5.56.59.125
8 2026-08-25 03:16 639232245484452890
40 ms 5.56.59.125
7 2026-08-25 02:59 639232235157175331
69 ms 5.56.59.125
6 2026-08-25 02:06 639232203197189095
86 ms 5.56.59.125
5 2026-08-25 01:48 639232192844564298
67 ms 5.56.59.125
4 2026-08-25 01:31 639232182496008942
97 ms 5.56.59.125
3 2026-08-25 01:14 639232172197053132
2007 ms 5.56.59.125
2 2026-08-25 00:21 639232140250307418
7 ms 5.56.59.125
1 2026-08-25 00:03 639232129927860324
37 ms 5.56.59.125