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-27. For this date, NameServerHistory found 26 DNS check records, 26 successful responses, 0 failed responses, and 494 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

26

Historical checks stored for this nameserver on selected date

Average Latency

494 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 08:33

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

26

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-27 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
26 2026-08-27 08:33 639234160341037652
137 ms 95.217.105.250
25 2026-08-27 08:16 639234149799404224
102 ms 95.217.105.250
24 2026-08-27 07:58 639234139553286469
116 ms 95.217.105.250
23 2026-08-27 07:05 639234107183588293
146 ms 95.217.105.250
22 2026-08-27 06:47 639234096905435724
113 ms 95.217.105.250
21 2026-08-27 06:30 639234086579410775
51 ms 95.217.105.250
20 2026-08-27 06:13 639234076291157956
129 ms 95.217.105.250
19 2026-08-27 05:56 639234065981939454
13 ms 95.217.105.250
18 2026-08-27 05:39 639234055548642997
203 ms 95.217.105.250
17 2026-08-27 05:21 639234045267979603
120 ms 95.217.105.250
16 2026-08-27 05:04 639234034999717463
123 ms 95.217.105.250
15 2026-08-27 04:47 639234024739225358
2038 ms 95.217.105.250
14 2026-08-27 04:30 639234014311170162
2076 ms 95.217.105.250
13 2026-08-27 04:12 639234003806017640
2092 ms 95.217.105.250
12 2026-08-27 03:55 639233993356203030
121 ms 95.217.105.250
11 2026-08-27 03:02 639233961301716608
50 ms 95.217.105.250
10 2026-08-27 02:44 639233950834200647
131 ms 95.217.105.250
9 2026-08-27 02:27 639233940431849026
144 ms 95.217.105.250
8 2026-08-27 02:09 639233930110596398
142 ms 95.217.105.250
7 2026-08-27 01:52 639233919705434540
124 ms 95.217.105.250
6 2026-08-27 01:35 639233909452807845
59 ms 95.217.105.250
5 2026-08-27 01:18 639233899096420820
2158 ms 95.217.105.250
4 2026-08-27 01:00 639233888707824939
110 ms 95.217.105.250
3 2026-08-27 00:43 639233878461203802
112 ms 95.217.105.250
2 2026-08-27 00:26 639233868060868209
2092 ms 95.217.105.250
1 2026-08-27 00:08 639233857450922991
142 ms 95.217.105.250