DNS response history for ns2.dominiospy.com

ns2.dominiospy.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-26. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 290 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.dominiospy.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

290 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:14

All timestamps shown in UTC

Latest Resolved IP on Selected Date

149.56.185.130

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.dominiospy.com

Showing DNS history for 2026-08-26 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-26 09:14 639233318749762337
447 ms 149.56.185.130
27 2026-08-26 08:57 639233308387917838
213 ms 149.56.185.130
26 2026-08-26 08:39 639233297961740122
128 ms 149.56.185.130
25 2026-08-26 08:22 639233287487159094
214 ms 149.56.185.130
24 2026-08-26 08:05 639233276995531707
214 ms 149.56.185.130
23 2026-08-26 07:47 639233266521568229
214 ms 149.56.185.130
22 2026-08-26 07:30 639233256081047431
221 ms 149.56.185.130
21 2026-08-26 06:36 639233223620132921
321 ms 149.56.185.130
20 2026-08-26 06:18 639233213287814244
214 ms 149.56.185.130
19 2026-08-26 06:01 639233202925983161
222 ms 149.56.185.130
18 2026-08-26 05:44 639233192644780696
226 ms 149.56.185.130
17 2026-08-26 05:27 639233182401183833
214 ms 149.56.185.130
16 2026-08-26 05:10 639233172074181051
218 ms 149.56.185.130
15 2026-08-26 04:52 639233161808421455
216 ms 149.56.185.130
14 2026-08-26 04:35 639233151357344052
227 ms 149.56.185.130
13 2026-08-26 04:18 639233141034116946
220 ms 149.56.185.130
12 2026-08-26 04:01 639233130828334142
236 ms 149.56.185.130
11 2026-08-26 03:44 639233120373450007
349 ms 149.56.185.130
10 2026-08-26 03:26 639233110066216193
108 ms 149.56.185.130
9 2026-08-26 02:33 639233078065410564
216 ms 149.56.185.130
8 2026-08-26 02:16 639233067787457832
125 ms 149.56.185.130
7 2026-08-26 01:59 639233057501801162
213 ms 149.56.185.130
6 2026-08-26 01:41 639233047089431703
109 ms 149.56.185.130
5 2026-08-26 01:24 639233036754790688
220 ms 149.56.185.130
4 2026-08-26 01:07 639233026412602472
111 ms 149.56.185.130
3 2026-08-26 00:49 639233016064066127
217 ms 149.56.185.130
2 2026-08-26 00:32 639233005922655772
2119 ms 149.56.185.130
1 2026-08-26 00:15 639232995672256907
359 ms 149.56.185.130