DNS response history for ns1.hardcored.com

ns1.hardcored.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, 31 successful responses, 1 failed responses, and 181 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.hardcored.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

181 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:19

All timestamps shown in UTC

Latest Resolved IP on Selected Date

83.149.125.175

Most recently resolved hosting IP on selected date

Successful Responses

31

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns1.hardcored.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:19 639233360361507238
165 ms 83.149.125.175
31 2026-08-26 10:02 639233350067824371
24 ms 83.149.125.175
30 2026-08-26 09:45 639233339545274518
10 ms 83.149.125.175
29 2026-08-26 09:27 639233329214918079
2027 ms 83.149.125.175
28 2026-08-26 09:10 639233318749762337
147 ms 83.149.125.175
27 2026-08-26 08:53 639233308387917838
61 ms 83.149.125.175
26 2026-08-26 08:35 639233297961740122
42 ms 83.149.125.175
25 2026-08-26 08:18 639233287487159094
-
24 2026-08-26 08:01 639233276995531707
41 ms 83.149.125.175
23 2026-08-26 07:43 639233266521568229
75 ms 83.149.125.175
22 2026-08-26 07:26 639233256081047431
69 ms 83.149.125.175
21 2026-08-26 06:32 639233223620132921
45 ms 83.149.125.175
20 2026-08-26 06:14 639233213287814244
42 ms 83.149.125.175
19 2026-08-26 05:57 639233202925983161
49 ms 83.149.125.175
18 2026-08-26 05:40 639233192644780696
64 ms 83.149.125.175
17 2026-08-26 05:23 639233182401183833
64 ms 83.149.125.175
16 2026-08-26 05:06 639233172074181051
16 ms 83.149.125.175
15 2026-08-26 04:49 639233161808421455
43 ms 83.149.125.175
14 2026-08-26 04:31 639233151357344052
52 ms 83.149.125.175
13 2026-08-26 04:14 639233141034116946
49 ms 83.149.125.175
12 2026-08-26 03:57 639233130828334142
83 ms 83.149.125.175
11 2026-08-26 03:40 639233120373450007
2034 ms 83.149.125.175
10 2026-08-26 03:22 639233110066216193
56 ms 83.149.125.175
9 2026-08-26 02:29 639233078065410564
75 ms 83.149.125.175
8 2026-08-26 02:12 639233067787457832
8 ms 83.149.125.175
7 2026-08-26 01:55 639233057501801162
59 ms 83.149.125.175
6 2026-08-26 01:37 639233047089431703
25 ms 83.149.125.175
5 2026-08-26 01:20 639233036754790688
21 ms 83.149.125.175
4 2026-08-26 01:03 639233026412602472
33 ms 83.149.125.175
3 2026-08-26 00:46 639233016064066127
46 ms 83.149.125.175
2 2026-08-26 00:29 639233005922655772
44 ms 83.149.125.175
1 2026-08-26 00:12 639232995672256907
39 ms 83.149.125.175