DNS response history for ns2.permacard-dan.com

ns2.permacard-dan.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 34 DNS check records, 34 successful responses, 0 failed responses, and 428 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.permacard-dan.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

428 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

72.167.46.102

Most recently resolved hosting IP on selected date

Successful Responses

34

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.permacard-dan.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
34 2026-08-25 12:05 639232556111768563
171 ms 72.167.46.102
33 2026-08-25 11:47 639232545839529039
164 ms 72.167.46.102
32 2026-08-25 11:30 639232535349285207
357 ms 72.167.46.102
31 2026-08-25 11:13 639232524938080723
363 ms 72.167.46.102
30 2026-08-25 10:19 639232492740373468
169 ms 72.167.46.102
29 2026-08-25 10:02 639232482235303141
340 ms 72.167.46.102
28 2026-08-25 09:44 639232471861770303
352 ms 72.167.46.102
27 2026-08-25 09:27 639232461630217327
341 ms 72.167.46.102
26 2026-08-25 09:10 639232451282965990
10 ms 72.167.46.102
25 2026-08-25 08:53 639232440814614938
346 ms 72.167.46.102
24 2026-08-25 08:35 639232430410720425
349 ms 72.167.46.102
23 2026-08-25 08:18 639232420003096185
350 ms 72.167.46.102
22 2026-08-25 08:00 639232409467287444
341 ms 72.167.46.102
21 2026-08-25 07:43 639232399077195997
17 ms 72.167.46.102
20 2026-08-25 07:26 639232388731528337
353 ms 72.167.46.102
19 2026-08-25 07:08 639232378288598612
168 ms 72.167.46.102
18 2026-08-25 06:15 639232346196373643
2008 ms 72.167.46.102
17 2026-08-25 05:58 639232336112370741
215 ms 72.167.46.102
16 2026-08-25 05:41 639232326146508970
335 ms 72.167.46.102
15 2026-08-25 05:25 639232316189381720
2219 ms 72.167.46.102
14 2026-08-25 05:08 639232306217998913
7 ms 72.167.46.102
13 2026-08-25 04:51 639232296255744174
190 ms 72.167.46.102
12 2026-08-25 04:34 639232286095760789
349 ms 72.167.46.102
11 2026-08-25 04:18 639232276086186273
342 ms 72.167.46.102
10 2026-08-25 04:01 639232265900986425
2162 ms 72.167.46.102
9 2026-08-25 03:44 639232255723518075
9 ms 72.167.46.102
8 2026-08-25 03:27 639232245484452890
357 ms 72.167.46.102
7 2026-08-25 03:10 639232235157175331
353 ms 72.167.46.102
6 2026-08-25 02:16 639232203197189095
347 ms 72.167.46.102
5 2026-08-25 01:59 639232192844564298
334 ms 72.167.46.102
4 2026-08-25 01:42 639232182496008942
364 ms 72.167.46.102
3 2026-08-25 01:25 639232172197053132
215 ms 72.167.46.102
2 2026-08-25 00:31 639232140250307418
343 ms 72.167.46.102
1 2026-08-25 00:14 639232129927860324
202 ms 72.167.46.102