DNS response history for ns1.getshieldfundinghosts.com

ns1.getshieldfundinghosts.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 34 DNS check records, 34 successful responses, 0 failed responses, and 551 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.getshieldfundinghosts.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

551 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

198.20.172.131

Most recently resolved hosting IP on selected date

Successful Responses

34

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.getshieldfundinghosts.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
34 2026-08-24 14:05 639231765923559455
7 ms 198.20.172.131
33 2026-08-24 13:48 639231755868832964
223 ms 198.20.172.131
32 2026-08-24 13:31 639231745628278877
2163 ms 198.20.172.131
31 2026-08-24 13:14 639231735407682062
2106 ms 198.20.172.131
30 2026-08-24 12:21 639231703815441688
236 ms 198.20.172.131
29 2026-08-24 12:05 639231693747052549
258 ms 198.20.172.131
28 2026-08-24 11:48 639231683712487276
223 ms 198.20.172.131
27 2026-08-24 11:31 639231673513573868
227 ms 198.20.172.131
26 2026-08-24 10:38 639231641791249939
119 ms 198.20.172.131
25 2026-08-24 10:21 639231631866211033
2106 ms 198.20.172.131
24 2026-08-24 10:04 639231621644955316
109 ms 198.20.172.131
23 2026-08-24 09:47 639231611478799259
117 ms 198.20.172.131
22 2026-08-24 08:55 639231579923718211
2109 ms 198.20.172.131
21 2026-08-24 08:38 639231569810702936
164 ms 198.20.172.131
20 2026-08-24 08:21 639231559762411619
7 ms 198.20.172.131
19 2026-08-24 08:04 639231549663595407
234 ms 198.20.172.131
18 2026-08-24 07:12 639231518076817246
7 ms 198.20.172.131
17 2026-08-24 06:55 639231508078650885
2108 ms 198.20.172.131
16 2026-08-24 06:39 639231498210697093
117 ms 198.20.172.131
15 2026-08-24 06:22 639231488109699360
211 ms 198.20.172.131
14 2026-08-24 05:30 639231456772510692
219 ms 198.20.172.131
13 2026-08-24 05:14 639231447084631185
7 ms 198.20.172.131
12 2026-08-24 04:57 639231437208519473
214 ms 198.20.172.131
11 2026-08-24 04:40 639231427209627490
213 ms 198.20.172.131
10 2026-08-24 03:48 639231395791246644
2113 ms 198.20.172.131
9 2026-08-24 03:32 639231386075551458
220 ms 198.20.172.131
8 2026-08-24 03:15 639231376208713791
218 ms 198.20.172.131
7 2026-08-24 02:59 639231366170589276
2116 ms 198.20.172.131
6 2026-08-24 02:06 639231334732159368
7 ms 198.20.172.131
5 2026-08-24 01:50 639231325035670078
12 ms 198.20.172.131
4 2026-08-24 01:34 639231315132253837
179 ms 198.20.172.131
3 2026-08-24 01:17 639231305014280808
150 ms 198.20.172.131
2 2026-08-24 00:25 639231273779380675
124 ms 198.20.172.131
1 2026-08-24 00:09 639231264180839154
105 ms 198.20.172.131