DNS response history for ns2.webhm.pro

ns2.webhm.pro 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 36 DNS check records, 36 successful responses, 0 failed responses, and 547 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.webhm.pro.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

547 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

213.152.43.251

Most recently resolved hosting IP on selected date

Successful Responses

36

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.webhm.pro

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
36 2026-08-25 12:39 639232576780683689
349 ms 213.152.43.251
35 2026-08-25 12:22 639232566381512620
57 ms 213.152.43.251
34 2026-08-25 12:05 639232556111768563
1471 ms 213.152.43.251
33 2026-08-25 11:47 639232545839529039
185 ms 213.152.43.251
32 2026-08-25 11:30 639232535349285207
56 ms 213.152.43.251
31 2026-08-25 11:13 639232524938080723
1107 ms 213.152.43.251
30 2026-08-25 10:19 639232492740373468
1134 ms 213.152.43.251
29 2026-08-25 10:02 639232482235303141
28 ms 213.152.43.251
28 2026-08-25 09:44 639232471861770303
32 ms 213.152.43.251
27 2026-08-25 09:27 639232461630217327
895 ms 213.152.43.251
26 2026-08-25 09:10 639232451282965990
129 ms 213.152.43.251
25 2026-08-25 08:53 639232440814614938
1057 ms 213.152.43.251
24 2026-08-25 08:35 639232430410720425
969 ms 213.152.43.251
23 2026-08-25 08:18 639232420003096185
5 ms 213.152.43.251
22 2026-08-25 08:00 639232409467287444
530 ms 213.152.43.251
21 2026-08-25 07:43 639232399077195997
1357 ms 213.152.43.251
20 2026-08-25 07:26 639232388731528337
59 ms 213.152.43.251
19 2026-08-25 07:08 639232378288598612
977 ms 213.152.43.251
18 2026-08-25 06:15 639232346196373643
70 ms 213.152.43.251
17 2026-08-25 05:58 639232336112370741
1098 ms 213.152.43.251
16 2026-08-25 05:41 639232326146508970
2228 ms 213.152.43.251
15 2026-08-25 05:25 639232316189381720
471 ms 213.152.43.251
14 2026-08-25 05:08 639232306217998913
27 ms 213.152.43.251
13 2026-08-25 04:51 639232296255744174
9 ms 213.152.43.251
12 2026-08-25 04:34 639232286095760789
30 ms 213.152.43.251
11 2026-08-25 04:18 639232276086186273
38 ms 213.152.43.251
10 2026-08-25 04:01 639232265900986425
472 ms 213.152.43.251
9 2026-08-25 03:44 639232255723518075
39 ms 213.152.43.251
8 2026-08-25 03:27 639232245484452890
421 ms 213.152.43.251
7 2026-08-25 03:10 639232235157175331
423 ms 213.152.43.251
6 2026-08-25 02:16 639232203197189095
57 ms 213.152.43.251
5 2026-08-25 01:59 639232192844564298
2067 ms 213.152.43.251
4 2026-08-25 01:42 639232182496008942
415 ms 213.152.43.251
3 2026-08-25 01:25 639232172197053132
72 ms 213.152.43.251
2 2026-08-25 00:31 639232140250307418
477 ms 213.152.43.251
1 2026-08-25 00:14 639232129927860324
867 ms 213.152.43.251