DNS response history for cryptobeholder.com

cryptobeholder.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-26. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 108 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 cryptobeholder.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

108 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:20

All timestamps shown in UTC

Latest Resolved IP on Selected Date

95.217.105.250

Most recently resolved hosting IP on selected date

Successful Responses

32

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 cryptobeholder.com

Showing DNS history for 2026-08-26 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
32 2026-08-26 10:20 639233360361507238
3 ms 95.217.105.250
31 2026-08-26 10:03 639233350067824371
126 ms 95.217.105.250
30 2026-08-26 09:45 639233339545274518
123 ms 95.217.105.250
29 2026-08-26 09:28 639233329214918079
132 ms 95.217.105.250
28 2026-08-26 09:11 639233318749762337
123 ms 95.217.105.250
27 2026-08-26 08:53 639233308387917838
111 ms 95.217.105.250
26 2026-08-26 08:36 639233297961740122
130 ms 95.217.105.250
25 2026-08-26 08:19 639233287487159094
134 ms 95.217.105.250
24 2026-08-26 08:01 639233276995531707
160 ms 95.217.105.250
23 2026-08-26 07:43 639233266521568229
159 ms 95.217.105.250
22 2026-08-26 07:26 639233256081047431
63 ms 95.217.105.250
21 2026-08-26 06:32 639233223620132921
59 ms 95.217.105.250
20 2026-08-26 06:15 639233213287814244
20 ms 95.217.105.250
19 2026-08-26 05:58 639233202925983161
4 ms 95.217.105.250
18 2026-08-26 05:40 639233192644780696
114 ms 95.217.105.250
17 2026-08-26 05:23 639233182401183833
122 ms 95.217.105.250
16 2026-08-26 05:06 639233172074181051
123 ms 95.217.105.250
15 2026-08-26 04:49 639233161808421455
126 ms 95.217.105.250
14 2026-08-26 04:32 639233151357344052
152 ms 95.217.105.250
13 2026-08-26 04:14 639233141034116946
114 ms 95.217.105.250
12 2026-08-26 03:57 639233130828334142
117 ms 95.217.105.250
11 2026-08-26 03:40 639233120373450007
90 ms 95.217.105.250
10 2026-08-26 03:23 639233110066216193
111 ms 95.217.105.250
9 2026-08-26 02:29 639233078065410564
144 ms 95.217.105.250
8 2026-08-26 02:12 639233067787457832
153 ms 95.217.105.250
7 2026-08-26 01:55 639233057501801162
134 ms 95.217.105.250
6 2026-08-26 01:38 639233047089431703
112 ms 95.217.105.250
5 2026-08-26 01:21 639233036754790688
76 ms 95.217.105.250
4 2026-08-26 01:03 639233026412602472
117 ms 95.217.105.250
3 2026-08-26 00:46 639233016064066127
117 ms 95.217.105.250
2 2026-08-26 00:29 639233005922655772
77 ms 95.217.105.250
1 2026-08-26 00:12 639232995672256907
99 ms 95.217.105.250