DNS response history for ns2.webhitdd.com

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

36

Historical checks stored for this nameserver on selected date

Average Latency

594 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

119.59.99.103

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.webhitdd.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
36 2026-08-25 12:40 639232576780683689
749 ms 119.59.99.103
35 2026-08-25 12:22 639232566381512620
706 ms 119.59.99.103
34 2026-08-25 12:05 639232556111768563
1044 ms 119.59.99.103
33 2026-08-25 11:48 639232545839529039
4390 ms 119.59.99.103
32 2026-08-25 11:31 639232535349285207
636 ms 119.59.99.103
31 2026-08-25 11:13 639232524938080723
358 ms 119.59.99.103
30 2026-08-25 10:20 639232492740373468
978 ms 119.59.99.103
29 2026-08-25 10:02 639232482235303141
1555 ms 119.59.99.103
28 2026-08-25 09:45 639232471861770303
641 ms 119.59.99.103
27 2026-08-25 09:28 639232461630217327
363 ms 119.59.99.103
26 2026-08-25 09:10 639232451282965990
186 ms 119.59.99.103
25 2026-08-25 08:53 639232440814614938
344 ms 119.59.99.103
24 2026-08-25 08:36 639232430410720425
379 ms 119.59.99.103
23 2026-08-25 08:18 639232420003096185
249 ms 119.59.99.103
22 2026-08-25 08:01 639232409467287444
415 ms 119.59.99.103
21 2026-08-25 07:43 639232399077195997
345 ms 119.59.99.103
20 2026-08-25 07:26 639232388731528337
348 ms 119.59.99.103
19 2026-08-25 07:09 639232378288598612
360 ms 119.59.99.103
18 2026-08-25 06:15 639232346196373643
238 ms 119.59.99.103
17 2026-08-25 05:58 639232336112370741
351 ms 119.59.99.103
16 2026-08-25 05:42 639232326146508970
380 ms 119.59.99.103
15 2026-08-25 05:25 639232316189381720
10 ms 119.59.99.103
14 2026-08-25 05:08 639232306217998913
401 ms 119.59.99.103
13 2026-08-25 04:52 639232296255744174
170 ms 119.59.99.103
12 2026-08-25 04:35 639232286095760789
345 ms 119.59.99.103
11 2026-08-25 04:18 639232276086186273
363 ms 119.59.99.103
10 2026-08-25 04:01 639232265900986425
364 ms 119.59.99.103
9 2026-08-25 03:44 639232255723518075
359 ms 119.59.99.103
8 2026-08-25 03:27 639232245484452890
363 ms 119.59.99.103
7 2026-08-25 03:10 639232235157175331
381 ms 119.59.99.103
6 2026-08-25 02:17 639232203197189095
364 ms 119.59.99.103
5 2026-08-25 02:00 639232192844564298
353 ms 119.59.99.103
4 2026-08-25 01:43 639232182496008942
366 ms 119.59.99.103
3 2026-08-25 01:25 639232172197053132
2169 ms 119.59.99.103
2 2026-08-25 00:32 639232140250307418
177 ms 119.59.99.103
1 2026-08-25 00:15 639232129927860324
202 ms 119.59.99.103