DNS response history for ns1.hardsex-online.com

ns1.hardsex-online.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 33 DNS check records, 33 successful responses, 0 failed responses, and 328 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.hardsex-online.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

328 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

173.214.253.248

Most recently resolved hosting IP on selected date

Successful Responses

33

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.hardsex-online.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
33 2026-08-26 10:26 639233360361507238
333 ms 173.214.253.248
32 2026-08-26 10:08 639233350067824371
383 ms 173.214.253.248
31 2026-08-26 09:51 639233339545274518
326 ms 173.214.253.248
30 2026-08-26 09:33 639233329214918079
181 ms 173.214.253.248
29 2026-08-26 09:16 639233318749762337
167 ms 173.214.253.248
28 2026-08-26 08:59 639233308387917838
336 ms 173.214.253.248
27 2026-08-26 08:41 639233297961740122
354 ms 173.214.253.248
26 2026-08-26 08:24 639233287487159094
174 ms 173.214.253.248
25 2026-08-26 08:07 639233276995531707
160 ms 173.214.253.248
24 2026-08-26 07:49 639233266521568229
361 ms 173.214.253.248
23 2026-08-26 07:31 639233256081047431
347 ms 173.214.253.248
22 2026-08-26 06:38 639233223620132921
343 ms 173.214.253.248
21 2026-08-26 06:20 639233213287814244
204 ms 173.214.253.248
20 2026-08-26 06:03 639233202925983161
109 ms 173.214.253.248
19 2026-08-26 05:46 639233192644780696
327 ms 173.214.253.248
18 2026-08-26 05:29 639233182401183833
344 ms 173.214.253.248
17 2026-08-26 05:12 639233172074181051
172 ms 173.214.253.248
16 2026-08-26 04:54 639233161808421455
190 ms 173.214.253.248
15 2026-08-26 04:37 639233151357344052
347 ms 173.214.253.248
14 2026-08-26 04:20 639233141034116946
8 ms 173.214.253.248
13 2026-08-26 04:03 639233130828334142
187 ms 173.214.253.248
12 2026-08-26 03:46 639233120373450007
364 ms 173.214.253.248
11 2026-08-26 03:28 639233110066216193
163 ms 173.214.253.248
10 2026-08-26 02:35 639233078065410564
2205 ms 173.214.253.248
9 2026-08-26 02:18 639233067787457832
352 ms 173.214.253.248
8 2026-08-26 02:01 639233057501801162
324 ms 173.214.253.248
7 2026-08-26 01:43 639233047089431703
5 ms 173.214.253.248
6 2026-08-26 01:26 639233036754790688
361 ms 173.214.253.248
5 2026-08-26 01:09 639233026412602472
356 ms 173.214.253.248
4 2026-08-26 00:52 639233016064066127
335 ms 173.214.253.248
3 2026-08-26 00:34 639233005922655772
320 ms 173.214.253.248
2 2026-08-26 00:17 639232995672256907
355 ms 173.214.253.248
1 2026-08-26 00:00 639232985300872416
347 ms 173.214.253.248