DNS response history for ns1.s4dom.org

ns1.s4dom.org 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-25. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 224 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.s4dom.org.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

224 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:48

All timestamps shown in UTC

Latest Resolved IP on Selected Date

131.153.159.66

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.s4dom.org

Showing DNS history for 2026-08-25 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-25 11:48 639232545839529039
203 ms 131.153.159.66
32 2026-08-25 11:31 639232535349285207
336 ms 131.153.159.66
31 2026-08-25 11:14 639232524938080723
480 ms 131.153.159.66
30 2026-08-25 10:20 639232492740373468
426 ms 131.153.159.66
29 2026-08-25 10:03 639232482235303141
4 ms 131.153.159.66
28 2026-08-25 09:45 639232471861770303
4 ms 131.153.159.66
27 2026-08-25 09:28 639232461630217327
4 ms 131.153.159.66
26 2026-08-25 09:11 639232451282965990
512 ms 131.153.159.66
25 2026-08-25 08:53 639232440814614938
332 ms 131.153.159.66
24 2026-08-25 08:36 639232430410720425
338 ms 131.153.159.66
23 2026-08-25 08:19 639232420003096185
14 ms 131.153.159.66
22 2026-08-25 08:01 639232409467287444
7 ms 131.153.159.66
21 2026-08-25 07:44 639232399077195997
325 ms 131.153.159.66
20 2026-08-25 07:26 639232388731528337
159 ms 131.153.159.66
19 2026-08-25 07:09 639232378288598612
348 ms 131.153.159.66
18 2026-08-25 06:15 639232346196373643
4 ms 131.153.159.66
17 2026-08-25 05:59 639232336112370741
157 ms 131.153.159.66
16 2026-08-25 05:42 639232326146508970
4 ms 131.153.159.66
15 2026-08-25 05:25 639232316189381720
339 ms 131.153.159.66
14 2026-08-25 05:09 639232306217998913
6 ms 131.153.159.66
13 2026-08-25 04:52 639232296255744174
331 ms 131.153.159.66
12 2026-08-25 04:35 639232286095760789
261 ms 131.153.159.66
11 2026-08-25 04:18 639232276086186273
161 ms 131.153.159.66
10 2026-08-25 04:02 639232265900986425
332 ms 131.153.159.66
9 2026-08-25 03:45 639232255723518075
169 ms 131.153.159.66
8 2026-08-25 03:28 639232245484452890
329 ms 131.153.159.66
7 2026-08-25 03:11 639232235157175331
229 ms 131.153.159.66
6 2026-08-25 02:17 639232203197189095
334 ms 131.153.159.66
5 2026-08-25 02:00 639232192844564298
4 ms 131.153.159.66
4 2026-08-25 01:43 639232182496008942
326 ms 131.153.159.66
3 2026-08-25 01:26 639232172197053132
3 ms 131.153.159.66
2 2026-08-25 00:32 639232140250307418
580 ms 131.153.159.66
1 2026-08-25 00:15 639232129927860324
333 ms 131.153.159.66