DNS response history for ns2.webdaddy.pro

ns2.webdaddy.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 299 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.webdaddy.pro.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

299 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:38

All timestamps shown in UTC

Latest Resolved IP on Selected Date

206.225.83.17

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.webdaddy.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:38 639232576780683689
403 ms 206.225.83.17
35 2026-08-25 12:20 639232566381512620
314 ms 206.225.83.17
34 2026-08-25 12:03 639232556111768563
156 ms 206.225.83.17
33 2026-08-25 11:46 639232545839529039
314 ms 206.225.83.17
32 2026-08-25 11:28 639232535349285207
150 ms 206.225.83.17
31 2026-08-25 11:11 639232524938080723
150 ms 206.225.83.17
30 2026-08-25 10:17 639232492740373468
173 ms 206.225.83.17
29 2026-08-25 10:00 639232482235303141
152 ms 206.225.83.17
28 2026-08-25 09:42 639232471861770303
306 ms 206.225.83.17
27 2026-08-25 09:25 639232461630217327
337 ms 206.225.83.17
26 2026-08-25 09:08 639232451282965990
157 ms 206.225.83.17
25 2026-08-25 08:51 639232440814614938
161 ms 206.225.83.17
24 2026-08-25 08:33 639232430410720425
310 ms 206.225.83.17
23 2026-08-25 08:16 639232420003096185
156 ms 206.225.83.17
22 2026-08-25 07:59 639232409467287444
542 ms 206.225.83.17
21 2026-08-25 07:41 639232399077195997
152 ms 206.225.83.17
20 2026-08-25 07:24 639232388731528337
340 ms 206.225.83.17
19 2026-08-25 07:07 639232378288598612
309 ms 206.225.83.17
18 2026-08-25 06:13 639232346196373643
321 ms 206.225.83.17
17 2026-08-25 05:56 639232336112370741
10 ms 206.225.83.17
16 2026-08-25 05:40 639232326146508970
7 ms 206.225.83.17
15 2026-08-25 05:23 639232316189381720
2247 ms 206.225.83.17
14 2026-08-25 05:06 639232306217998913
309 ms 206.225.83.17
13 2026-08-25 04:50 639232296255744174
3 ms 206.225.83.17
12 2026-08-25 04:33 639232286095760789
320 ms 206.225.83.17
11 2026-08-25 04:16 639232276086186273
316 ms 206.225.83.17
10 2026-08-25 03:59 639232265900986425
170 ms 206.225.83.17
9 2026-08-25 03:42 639232255723518075
152 ms 206.225.83.17
8 2026-08-25 03:25 639232245484452890
312 ms 206.225.83.17
7 2026-08-25 03:08 639232235157175331
311 ms 206.225.83.17
6 2026-08-25 02:15 639232203197189095
315 ms 206.225.83.17
5 2026-08-25 01:58 639232192844564298
320 ms 206.225.83.17
4 2026-08-25 01:40 639232182496008942
153 ms 206.225.83.17
3 2026-08-25 01:23 639232172197053132
434 ms 206.225.83.17
2 2026-08-25 00:30 639232140250307418
313 ms 206.225.83.17
1 2026-08-25 00:13 639232129927860324
159 ms 206.225.83.17