DNS response history for ns1.s4dom.net

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

33

Historical checks stored for this nameserver on selected date

Average Latency

452 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:47

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

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:47 639232545839529039
26 ms 131.153.159.66
32 2026-08-25 11:30 639232535349285207
321 ms 131.153.159.66
31 2026-08-25 11:12 639232524938080723
320 ms 131.153.159.66
30 2026-08-25 10:19 639232492740373468
334 ms 131.153.159.66
29 2026-08-25 10:01 639232482235303141
348 ms 131.153.159.66
28 2026-08-25 09:44 639232471861770303
375 ms 131.153.159.66
27 2026-08-25 09:27 639232461630217327
301 ms 131.153.159.66
26 2026-08-25 09:10 639232451282965990
337 ms 131.153.159.66
25 2026-08-25 08:52 639232440814614938
2172 ms 131.153.159.66
24 2026-08-25 08:35 639232430410720425
2256 ms 131.153.159.66
23 2026-08-25 08:18 639232420003096185
323 ms 131.153.159.66
22 2026-08-25 08:00 639232409467287444
326 ms 131.153.159.66
21 2026-08-25 07:43 639232399077195997
324 ms 131.153.159.66
20 2026-08-25 07:25 639232388731528337
321 ms 131.153.159.66
19 2026-08-25 07:08 639232378288598612
334 ms 131.153.159.66
18 2026-08-25 06:14 639232346196373643
252 ms 131.153.159.66
17 2026-08-25 05:57 639232336112370741
316 ms 131.153.159.66
16 2026-08-25 05:41 639232326146508970
317 ms 131.153.159.66
15 2026-08-25 05:24 639232316189381720
326 ms 131.153.159.66
14 2026-08-25 05:08 639232306217998913
322 ms 131.153.159.66
13 2026-08-25 04:51 639232296255744174
330 ms 131.153.159.66
12 2026-08-25 04:34 639232286095760789
2172 ms 131.153.159.66
11 2026-08-25 04:17 639232276086186273
3 ms 131.153.159.66
10 2026-08-25 04:00 639232265900986425
314 ms 131.153.159.66
9 2026-08-25 03:44 639232255723518075
328 ms 131.153.159.66
8 2026-08-25 03:26 639232245484452890
321 ms 131.153.159.66
7 2026-08-25 03:09 639232235157175331
3 ms 131.153.159.66
6 2026-08-25 02:16 639232203197189095
327 ms 131.153.159.66
5 2026-08-25 01:59 639232192844564298
317 ms 131.153.159.66
4 2026-08-25 01:42 639232182496008942
5 ms 131.153.159.66
3 2026-08-25 01:24 639232172197053132
198 ms 131.153.159.66
2 2026-08-25 00:31 639232140250307418
320 ms 131.153.159.66
1 2026-08-25 00:14 639232129927860324
319 ms 131.153.159.66