DNS response history for ns1.binraddad.com

ns1.binraddad.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 270 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.binraddad.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

270 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

147.93.98.103

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.binraddad.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:39 639233370841350248
138 ms 147.93.98.103
32 2026-08-26 10:22 639233360361507238
253 ms 147.93.98.103
31 2026-08-26 10:04 639233350067824371
8 ms 147.93.98.103
30 2026-08-26 09:47 639233339545274518
262 ms 147.93.98.103
29 2026-08-26 09:29 639233329214918079
251 ms 147.93.98.103
28 2026-08-26 09:12 639233318749762337
10 ms 147.93.98.103
27 2026-08-26 08:55 639233308387917838
227 ms 147.93.98.103
26 2026-08-26 08:38 639233297961740122
262 ms 147.93.98.103
25 2026-08-26 08:20 639233287487159094
9 ms 147.93.98.103
24 2026-08-26 08:03 639233276995531707
156 ms 147.93.98.103
23 2026-08-26 07:45 639233266521568229
262 ms 147.93.98.103
22 2026-08-26 07:28 639233256081047431
265 ms 147.93.98.103
21 2026-08-26 06:34 639233223620132921
263 ms 147.93.98.103
20 2026-08-26 06:16 639233213287814244
261 ms 147.93.98.103
19 2026-08-26 05:59 639233202925983161
252 ms 147.93.98.103
18 2026-08-26 05:42 639233192644780696
272 ms 147.93.98.103
17 2026-08-26 05:25 639233182401183833
251 ms 147.93.98.103
16 2026-08-26 05:08 639233172074181051
262 ms 147.93.98.103
15 2026-08-26 04:51 639233161808421455
255 ms 147.93.98.103
14 2026-08-26 04:33 639233151357344052
285 ms 147.93.98.103
13 2026-08-26 04:16 639233141034116946
281 ms 147.93.98.103
12 2026-08-26 03:59 639233130828334142
259 ms 147.93.98.103
11 2026-08-26 03:42 639233120373450007
268 ms 147.93.98.103
10 2026-08-26 03:24 639233110066216193
256 ms 147.93.98.103
9 2026-08-26 02:31 639233078065410564
246 ms 147.93.98.103
8 2026-08-26 02:14 639233067787457832
2427 ms 147.93.98.103
7 2026-08-26 01:57 639233057501801162
263 ms 147.93.98.103
6 2026-08-26 01:39 639233047089431703
253 ms 147.93.98.103
5 2026-08-26 01:22 639233036754790688
6 ms 147.93.98.103
4 2026-08-26 01:05 639233026412602472
7 ms 147.93.98.103
3 2026-08-26 00:48 639233016064066127
255 ms 147.93.98.103
2 2026-08-26 00:31 639233005922655772
20 ms 147.93.98.103
1 2026-08-26 00:14 639232995672256907
155 ms 147.93.98.103