DNS response history for d.ns.coresense.com

d.ns.coresense.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 396 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 d.ns.coresense.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

396 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.123.63.85

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 d.ns.coresense.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:36 639233370841350248
37 ms 209.123.63.85
32 2026-08-26 10:19 639233360361507238
35 ms 209.123.63.85
31 2026-08-26 10:02 639233350067824371
11 ms 209.123.63.85
30 2026-08-26 09:45 639233339545274518
16 ms 209.123.63.85
29 2026-08-26 09:27 639233329214918079
140 ms 209.123.63.85
28 2026-08-26 09:10 639233318749762337
11 ms 209.123.63.85
27 2026-08-26 08:53 639233308387917838
44 ms 209.123.63.85
26 2026-08-26 08:35 639233297961740122
17 ms 209.123.63.85
25 2026-08-26 08:18 639233287487159094
6 ms 209.123.63.85
24 2026-08-26 08:00 639233276995531707
116 ms 209.123.63.85
23 2026-08-26 07:43 639233266521568229
12 ms 209.123.63.85
22 2026-08-26 07:25 639233256081047431
23 ms 209.123.63.85
21 2026-08-26 06:31 639233223620132921
57 ms 209.123.63.85
20 2026-08-26 06:14 639233213287814244
2048 ms 209.123.63.85
19 2026-08-26 05:57 639233202925983161
19 ms 209.123.63.85
18 2026-08-26 05:39 639233192644780696
40 ms 209.123.63.85
17 2026-08-26 05:22 639233182401183833
22 ms 209.123.63.85
16 2026-08-26 05:05 639233172074181051
29 ms 209.123.63.85
15 2026-08-26 04:48 639233161808421455
14 ms 209.123.63.85
14 2026-08-26 04:31 639233151357344052
9 ms 209.123.63.85
13 2026-08-26 04:14 639233141034116946
37 ms 209.123.63.85
12 2026-08-26 03:56 639233130828334142
18 ms 209.123.63.85
11 2026-08-26 03:39 639233120373450007
25 ms 209.123.63.85
10 2026-08-26 03:22 639233110066216193
2064 ms 209.123.63.85
9 2026-08-26 02:29 639233078065410564
4 ms 209.123.63.85
8 2026-08-26 02:12 639233067787457832
2046 ms 209.123.63.85
7 2026-08-26 01:54 639233057501801162
2031 ms 209.123.63.85
6 2026-08-26 01:37 639233047089431703
2019 ms 209.123.63.85
5 2026-08-26 01:20 639233036754790688
8 ms 209.123.63.85
4 2026-08-26 01:03 639233026412602472
2037 ms 209.123.63.85
3 2026-08-26 00:45 639233016064066127
22 ms 209.123.63.85
2 2026-08-26 00:28 639233005922655772
41 ms 209.123.63.85
1 2026-08-26 00:11 639232995672256907
25 ms 209.123.63.85