DNS response history for c.gooddomain.com

c.gooddomain.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 38 DNS check records, 38 successful responses, 0 failed responses, and 236 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 c.gooddomain.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

236 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:03

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.159.11.104

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 c.gooddomain.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
38 2026-08-25 13:03 639232597643611557
12 ms 162.159.11.104
37 2026-08-25 12:46 639232587225721862
24 ms 162.159.11.104
36 2026-08-25 12:28 639232576780683689
9 ms 162.159.11.104
35 2026-08-25 12:11 639232566381512620
9 ms 162.159.11.104
34 2026-08-25 11:54 639232556111768563
5 ms 162.159.11.104
33 2026-08-25 11:37 639232545839529039
12 ms 162.159.11.104
32 2026-08-25 11:19 639232535349285207
10 ms 162.159.11.104
31 2026-08-25 11:02 639232524938080723
15 ms 162.159.11.104
30 2026-08-25 10:08 639232492740373468
31 ms 162.159.11.104
29 2026-08-25 09:51 639232482235303141
75 ms 162.159.11.104
28 2026-08-25 09:33 639232471861770303
24 ms 162.159.11.104
27 2026-08-25 09:16 639232461630217327
2035 ms 162.159.11.104
26 2026-08-25 08:59 639232451282965990
28 ms 162.159.11.104
25 2026-08-25 08:42 639232440814614938
29 ms 162.159.11.104
24 2026-08-25 08:24 639232430410720425
9 ms 162.159.11.104
23 2026-08-25 08:07 639232420003096185
30 ms 162.159.11.104
22 2026-08-25 07:49 639232409467287444
54 ms 162.159.11.104
21 2026-08-25 07:32 639232399077195997
4021 ms 162.159.11.104
20 2026-08-25 07:15 639232388731528337
38 ms 162.159.11.104
19 2026-08-25 06:58 639232378288598612
23 ms 162.159.11.104
18 2026-08-25 06:04 639232346196373643
24 ms 162.159.11.104
17 2026-08-25 05:47 639232336112370741
17 ms 162.159.11.104
16 2026-08-25 05:31 639232326146508970
26 ms 162.159.11.104
15 2026-08-25 05:14 639232316189381720
29 ms 162.159.11.104
14 2026-08-25 04:57 639232306217998913
37 ms 162.159.11.104
13 2026-08-25 04:41 639232296255744174
2019 ms 162.159.11.104
12 2026-08-25 04:24 639232286095760789
37 ms 162.159.11.104
11 2026-08-25 04:07 639232276086186273
26 ms 162.159.11.104
10 2026-08-25 03:50 639232265900986425
26 ms 162.159.11.104
9 2026-08-25 03:33 639232255723518075
44 ms 162.159.11.104
8 2026-08-25 03:16 639232245484452890
12 ms 162.159.11.104
7 2026-08-25 02:59 639232235157175331
16 ms 162.159.11.104
6 2026-08-25 02:06 639232203197189095
39 ms 162.159.11.104
5 2026-08-25 01:48 639232192844564298
44 ms 162.159.11.104
4 2026-08-25 01:31 639232182496008942
34 ms 162.159.11.104
3 2026-08-25 01:14 639232172197053132
8 ms 162.159.11.104
2 2026-08-25 00:21 639232140250307418
9 ms 162.159.11.104
1 2026-08-25 00:04 639232129927860324
33 ms 162.159.11.104