DNS response history for ns2.webcreds.com

ns2.webcreds.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-25. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 276 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 ns2.webcreds.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

276 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:08

All timestamps shown in UTC

Latest Resolved IP on Selected Date

203.161.58.79

Most recently resolved hosting IP on selected date

Successful Responses

35

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 ns2.webcreds.com

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
35 2026-08-25 12:08 639232556111768563
302 ms 203.161.58.79
34 2026-08-25 11:50 639232545839529039
295 ms 203.161.58.79
33 2026-08-25 11:33 639232535349285207
306 ms 203.161.58.79
32 2026-08-25 11:16 639232524938080723
306 ms 203.161.58.79
31 2026-08-25 10:22 639232492740373468
289 ms 203.161.58.79
30 2026-08-25 10:05 639232482235303141
282 ms 203.161.58.79
29 2026-08-25 09:47 639232471861770303
319 ms 203.161.58.79
28 2026-08-25 09:30 639232461630217327
318 ms 203.161.58.79
27 2026-08-25 09:13 639232451282965990
301 ms 203.161.58.79
26 2026-08-25 08:56 639232440814614938
302 ms 203.161.58.79
25 2026-08-25 08:38 639232430410720425
307 ms 203.161.58.79
24 2026-08-25 08:21 639232420003096185
297 ms 203.161.58.79
23 2026-08-25 08:04 639232409467287444
321 ms 203.161.58.79
22 2026-08-25 07:46 639232399077195997
302 ms 203.161.58.79
21 2026-08-25 07:29 639232388731528337
334 ms 203.161.58.79
20 2026-08-25 07:11 639232378288598612
324 ms 203.161.58.79
19 2026-08-25 06:18 639232346196373643
296 ms 203.161.58.79
18 2026-08-25 06:01 639232336112370741
316 ms 203.161.58.79
17 2026-08-25 05:44 639232326146508970
302 ms 203.161.58.79
16 2026-08-25 05:27 639232316189381720
163 ms 203.161.58.79
15 2026-08-25 05:11 639232306217998913
3 ms 203.161.58.79
14 2026-08-25 04:54 639232296255744174
2 ms 203.161.58.79
13 2026-08-25 04:37 639232286095760789
3 ms 203.161.58.79
12 2026-08-25 04:20 639232276086186273
283 ms 203.161.58.79
11 2026-08-25 04:04 639232265900986425
301 ms 203.161.58.79
10 2026-08-25 03:47 639232255723518075
312 ms 203.161.58.79
9 2026-08-25 03:30 639232245484452890
319 ms 203.161.58.79
8 2026-08-25 03:13 639232235157175331
306 ms 203.161.58.79
7 2026-08-25 02:19 639232203197189095
299 ms 203.161.58.79
6 2026-08-25 02:02 639232192844564298
332 ms 203.161.58.79
5 2026-08-25 01:45 639232182496008942
301 ms 203.161.58.79
4 2026-08-25 01:28 639232172197053132
309 ms 203.161.58.79
3 2026-08-25 00:34 639232140250307418
300 ms 203.161.58.79
2 2026-08-25 00:17 639232129927860324
302 ms 203.161.58.79
1 2026-08-25 00:00 639232119551972438
309 ms 203.161.58.79