DNS response history for ns2.ph0rbidden.chat

ns2.ph0rbidden.chat 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 18 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.ph0rbidden.chat.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

18 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:33

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.178.87.8

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 ns2.ph0rbidden.chat

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:33 639232535349285207
10 ms 51.178.87.8
32 2026-08-25 11:15 639232524938080723
8 ms 51.178.87.8
31 2026-08-25 10:22 639232492740373468
49 ms 51.178.87.8
30 2026-08-25 10:04 639232482235303141
14 ms 51.178.87.8
29 2026-08-25 09:47 639232471861770303
21 ms 51.178.87.8
28 2026-08-25 09:30 639232461630217327
10 ms 51.178.87.8
27 2026-08-25 09:13 639232451282965990
8 ms 51.178.87.8
26 2026-08-25 08:55 639232440814614938
36 ms 51.178.87.8
25 2026-08-25 08:38 639232430410720425
10 ms 51.178.87.8
24 2026-08-25 08:21 639232420003096185
23 ms 51.178.87.8
23 2026-08-25 08:03 639232409467287444
24 ms 51.178.87.8
22 2026-08-25 07:46 639232399077195997
9 ms 51.178.87.8
21 2026-08-25 07:28 639232388731528337
8 ms 51.178.87.8
20 2026-08-25 07:11 639232378288598612
7 ms 51.178.87.8
19 2026-08-25 06:17 639232346196373643
3 ms 51.178.87.8
18 2026-08-25 06:00 639232336112370741
27 ms 51.178.87.8
17 2026-08-25 05:44 639232326146508970
11 ms 51.178.87.8
16 2026-08-25 05:27 639232316189381720
11 ms 51.178.87.8
15 2026-08-25 05:11 639232306217998913
12 ms 51.178.87.8
14 2026-08-25 04:54 639232296255744174
4 ms 51.178.87.8
13 2026-08-25 04:37 639232286095760789
23 ms 51.178.87.8
12 2026-08-25 04:20 639232276086186273
25 ms 51.178.87.8
11 2026-08-25 04:03 639232265900986425
15 ms 51.178.87.8
10 2026-08-25 03:47 639232255723518075
50 ms 51.178.87.8
9 2026-08-25 03:29 639232245484452890
36 ms 51.178.87.8
8 2026-08-25 03:12 639232235157175331
24 ms 51.178.87.8
7 2026-08-25 02:19 639232203197189095
9 ms 51.178.87.8
6 2026-08-25 02:02 639232192844564298
11 ms 51.178.87.8
5 2026-08-25 01:45 639232182496008942
9 ms 51.178.87.8
4 2026-08-25 01:27 639232172197053132
23 ms 51.178.87.8
3 2026-08-25 00:34 639232140250307418
10 ms 51.178.87.8
2 2026-08-25 00:17 639232129927860324
20 ms 51.178.87.8
1 2026-08-25 00:00 639232119551972438
34 ms 51.178.87.8