DNS response history for ns1.pd-host.com

ns1.pd-host.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-24. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 507 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.pd-host.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

507 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 11:51

All timestamps shown in UTC

Latest Resolved IP on Selected Date

43.249.39.249

Most recently resolved hosting IP on selected date

Successful Responses

28

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.pd-host.com

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
28 2026-08-24 11:51 639231683712487276
364 ms 43.249.39.249
27 2026-08-24 11:34 639231673513573868
182 ms 43.249.39.249
26 2026-08-24 10:41 639231641791249939
358 ms 43.249.39.249
25 2026-08-24 10:24 639231631866211033
182 ms 43.249.39.249
24 2026-08-24 10:07 639231621644955316
216 ms 43.249.39.249
23 2026-08-24 09:50 639231611478799259
184 ms 43.249.39.249
22 2026-08-24 08:58 639231579923718211
354 ms 43.249.39.249
21 2026-08-24 08:41 639231569810702936
179 ms 43.249.39.249
20 2026-08-24 08:24 639231559762411619
361 ms 43.249.39.249
19 2026-08-24 08:07 639231549663595407
179 ms 43.249.39.249
18 2026-08-24 07:15 639231518076817246
200 ms 43.249.39.249
17 2026-08-24 06:58 639231508078650885
2284 ms 43.249.39.249
16 2026-08-24 06:41 639231498210697093
181 ms 43.249.39.249
15 2026-08-24 06:25 639231488109699360
2171 ms 43.249.39.249
14 2026-08-24 05:33 639231456772510692
358 ms 43.249.39.249
13 2026-08-24 05:16 639231447084631185
184 ms 43.249.39.249
12 2026-08-24 05:00 639231437208519473
2251 ms 43.249.39.249
11 2026-08-24 04:43 639231427209627490
286 ms 43.249.39.249
10 2026-08-24 03:51 639231395791246644
3 ms 43.249.39.249
9 2026-08-24 03:35 639231386075551458
180 ms 43.249.39.249
8 2026-08-24 03:18 639231376208713791
356 ms 43.249.39.249
7 2026-08-24 03:02 639231366170589276
357 ms 43.249.39.249
6 2026-08-24 02:09 639231334732159368
4 ms 43.249.39.249
5 2026-08-24 01:53 639231325035670078
2206 ms 43.249.39.249
4 2026-08-24 01:36 639231315132253837
178 ms 43.249.39.249
3 2026-08-24 01:20 639231305014280808
238 ms 43.249.39.249
2 2026-08-24 00:27 639231273779380675
3 ms 43.249.39.249
1 2026-08-24 00:11 639231264180839154
184 ms 43.249.39.249