DNS response history for ns1.noharm.net

ns1.noharm.net 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 38 DNS check records, 38 successful responses, 0 failed responses, and 586 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.noharm.net.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

586 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:32

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.38.211.8

Most recently resolved hosting IP on selected date

Successful Responses

38

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.noharm.net

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
38 2026-08-26 12:32 639233434974187439
604 ms 51.38.211.8
37 2026-08-26 12:15 639233424567558554
590 ms 51.38.211.8
36 2026-08-26 11:58 639233414056832719
570 ms 51.38.211.8
35 2026-08-26 11:40 639233403515141099
600 ms 51.38.211.8
34 2026-08-26 10:45 639233370841350248
569 ms 51.38.211.8
33 2026-08-26 10:28 639233360361507238
577 ms 51.38.211.8
32 2026-08-26 10:11 639233350067824371
613 ms 51.38.211.8
31 2026-08-26 09:54 639233339545274518
603 ms 51.38.211.8
30 2026-08-26 09:36 639233329214918079
576 ms 51.38.211.8
29 2026-08-26 09:19 639233318749762337
578 ms 51.38.211.8
28 2026-08-26 09:01 639233308387917838
591 ms 51.38.211.8
27 2026-08-26 08:44 639233297961740122
573 ms 51.38.211.8
26 2026-08-26 08:27 639233287487159094
588 ms 51.38.211.8
25 2026-08-26 08:09 639233276995531707
594 ms 51.38.211.8
24 2026-08-26 07:52 639233266521568229
600 ms 51.38.211.8
23 2026-08-26 07:34 639233256081047431
575 ms 51.38.211.8
22 2026-08-26 06:40 639233223620132921
637 ms 51.38.211.8
21 2026-08-26 06:23 639233213287814244
593 ms 51.38.211.8
20 2026-08-26 06:06 639233202925983161
582 ms 51.38.211.8
19 2026-08-26 05:48 639233192644780696
625 ms 51.38.211.8
18 2026-08-26 05:31 639233182401183833
604 ms 51.38.211.8
17 2026-08-26 05:14 639233172074181051
559 ms 51.38.211.8
16 2026-08-26 04:57 639233161808421455
579 ms 51.38.211.8
15 2026-08-26 04:40 639233151357344052
613 ms 51.38.211.8
14 2026-08-26 04:22 639233141034116946
562 ms 51.38.211.8
13 2026-08-26 04:05 639233130828334142
606 ms 51.38.211.8
12 2026-08-26 03:48 639233120373450007
590 ms 51.38.211.8
11 2026-08-26 03:31 639233110066216193
585 ms 51.38.211.8
10 2026-08-26 02:37 639233078065410564
559 ms 51.38.211.8
9 2026-08-26 02:20 639233067787457832
553 ms 51.38.211.8
8 2026-08-26 02:03 639233057501801162
608 ms 51.38.211.8
7 2026-08-26 01:46 639233047089431703
581 ms 51.38.211.8
6 2026-08-26 01:29 639233036754790688
560 ms 51.38.211.8
5 2026-08-26 01:12 639233026412602472
543 ms 51.38.211.8
4 2026-08-26 00:54 639233016064066127
573 ms 51.38.211.8
3 2026-08-26 00:37 639233005922655772
608 ms 51.38.211.8
2 2026-08-26 00:20 639232995672256907
571 ms 51.38.211.8
1 2026-08-26 00:03 639232985300872416
594 ms 51.38.211.8