DNS response history for nm2.verinomidns.com

nm2.verinomidns.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-27. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 198 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 nm2.verinomidns.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

198 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:15

All timestamps shown in UTC

Latest Resolved IP on Selected Date

94.102.12.60

Most recently resolved hosting IP on selected date

Successful Responses

32

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 nm2.verinomidns.com

Showing DNS history for 2026-08-27 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
32 2026-08-27 10:15 639234222943951923
2092 ms 94.102.12.60
31 2026-08-27 09:57 639234212558002823
78 ms 94.102.12.60
30 2026-08-27 09:40 639234202117531850
99 ms 94.102.12.60
29 2026-08-27 09:22 639234191649612722
241 ms 94.102.12.60
28 2026-08-27 09:05 639234181105879568
60 ms 94.102.12.60
27 2026-08-27 08:47 639234170713214496
76 ms 94.102.12.60
26 2026-08-27 08:30 639234160341037652
62 ms 94.102.12.60
25 2026-08-27 08:13 639234149799404224
59 ms 94.102.12.60
24 2026-08-27 07:56 639234139553286469
60 ms 94.102.12.60
23 2026-08-27 07:02 639234107183588293
77 ms 94.102.12.60
22 2026-08-27 06:44 639234096905435724
60 ms 94.102.12.60
21 2026-08-27 06:27 639234086579410775
65 ms 94.102.12.60
20 2026-08-27 06:10 639234076291157956
80 ms 94.102.12.60
19 2026-08-27 05:53 639234065981939454
80 ms 94.102.12.60
18 2026-08-27 05:36 639234055548642997
7 ms 94.102.12.60
17 2026-08-27 05:18 639234045267979603
69 ms 94.102.12.60
16 2026-08-27 05:01 639234034999717463
64 ms 94.102.12.60
15 2026-08-27 04:44 639234024739225358
61 ms 94.102.12.60
14 2026-08-27 04:27 639234014311170162
65 ms 94.102.12.60
13 2026-08-27 04:09 639234003806017640
2059 ms 94.102.12.60
12 2026-08-27 03:52 639233993356203030
60 ms 94.102.12.60
11 2026-08-27 02:59 639233961301716608
62 ms 94.102.12.60
10 2026-08-27 02:41 639233950834200647
109 ms 94.102.12.60
9 2026-08-27 02:24 639233940431849026
56 ms 94.102.12.60
8 2026-08-27 02:06 639233930110596398
74 ms 94.102.12.60
7 2026-08-27 01:49 639233919705434540
59 ms 94.102.12.60
6 2026-08-27 01:32 639233909452807845
66 ms 94.102.12.60
5 2026-08-27 01:15 639233899096420820
62 ms 94.102.12.60
4 2026-08-27 00:58 639233888707824939
67 ms 94.102.12.60
3 2026-08-27 00:40 639233878461203802
59 ms 94.102.12.60
2 2026-08-27 00:23 639233868060868209
68 ms 94.102.12.60
1 2026-08-27 00:05 639233857450922991
66 ms 94.102.12.60