DNS response history for ns1.webdaddy.pro

ns1.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-24. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 395 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 ns1.webdaddy.pro.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

395 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:16

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 ns1.webdaddy.pro

Showing DNS history for 2026-08-24 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-24 15:16 639231807961539652
173 ms 206.225.83.17
35 2026-08-24 14:59 639231797631669865
329 ms 206.225.83.17
34 2026-08-24 14:06 639231765923559455
155 ms 206.225.83.17
33 2026-08-24 13:49 639231755868832964
322 ms 206.225.83.17
32 2026-08-24 13:32 639231745628278877
2154 ms 206.225.83.17
31 2026-08-24 13:15 639231735407682062
186 ms 206.225.83.17
30 2026-08-24 12:22 639231703815441688
160 ms 206.225.83.17
29 2026-08-24 12:05 639231693747052549
4 ms 206.225.83.17
28 2026-08-24 11:48 639231683712487276
162 ms 206.225.83.17
27 2026-08-24 11:32 639231673513573868
306 ms 206.225.83.17
26 2026-08-24 10:39 639231641791249939
4 ms 206.225.83.17
25 2026-08-24 10:22 639231631866211033
296 ms 206.225.83.17
24 2026-08-24 10:05 639231621644955316
2277 ms 206.225.83.17
23 2026-08-24 09:48 639231611478799259
146 ms 206.225.83.17
22 2026-08-24 08:56 639231579923718211
302 ms 206.225.83.17
21 2026-08-24 08:39 639231569810702936
157 ms 206.225.83.17
20 2026-08-24 08:22 639231559762411619
298 ms 206.225.83.17
19 2026-08-24 08:05 639231549663595407
295 ms 206.225.83.17
18 2026-08-24 07:13 639231518076817246
307 ms 206.225.83.17
17 2026-08-24 06:56 639231508078650885
298 ms 206.225.83.17
16 2026-08-24 06:39 639231498210697093
2288 ms 206.225.83.17
15 2026-08-24 06:23 639231488109699360
309 ms 206.225.83.17
14 2026-08-24 05:31 639231456772510692
2166 ms 206.225.83.17
13 2026-08-24 05:14 639231447084631185
2 ms 206.225.83.17
12 2026-08-24 04:58 639231437208519473
20 ms 206.225.83.17
11 2026-08-24 04:41 639231427209627490
5 ms 206.225.83.17
10 2026-08-24 03:49 639231395791246644
2 ms 206.225.83.17
9 2026-08-24 03:33 639231386075551458
4 ms 206.225.83.17
8 2026-08-24 03:16 639231376208713791
321 ms 206.225.83.17
7 2026-08-24 02:59 639231366170589276
409 ms 206.225.83.17
6 2026-08-24 02:07 639231334732159368
3 ms 206.225.83.17
5 2026-08-24 01:51 639231325035670078
21 ms 206.225.83.17
4 2026-08-24 01:34 639231315132253837
295 ms 206.225.83.17
3 2026-08-24 01:18 639231305014280808
2 ms 206.225.83.17
2 2026-08-24 00:25 639231273779380675
24 ms 206.225.83.17
1 2026-08-24 00:09 639231264180839154
6 ms 206.225.83.17