DNS response history for ns2.sexdating18.com

ns2.sexdating18.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 37 DNS check records, 37 successful responses, 0 failed responses, and 201 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.sexdating18.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

201 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:48

All timestamps shown in UTC

Latest Resolved IP on Selected Date

5.135.59.175

Most recently resolved hosting IP on selected date

Successful Responses

37

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.sexdating18.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
37 2026-08-25 12:48 639232587225721862
9 ms 5.135.59.175
36 2026-08-25 12:31 639232576780683689
37 ms 5.135.59.175
35 2026-08-25 12:14 639232566381512620
67 ms 5.135.59.175
34 2026-08-25 11:56 639232556111768563
33 ms 5.135.59.175
33 2026-08-25 11:39 639232545839529039
36 ms 5.135.59.175
32 2026-08-25 11:22 639232535349285207
57 ms 5.135.59.175
31 2026-08-25 11:05 639232524938080723
23 ms 5.135.59.175
30 2026-08-25 10:11 639232492740373468
52 ms 5.135.59.175
29 2026-08-25 09:53 639232482235303141
58 ms 5.135.59.175
28 2026-08-25 09:36 639232471861770303
43 ms 5.135.59.175
27 2026-08-25 09:19 639232461630217327
47 ms 5.135.59.175
26 2026-08-25 09:02 639232451282965990
2027 ms 5.135.59.175
25 2026-08-25 08:44 639232440814614938
41 ms 5.135.59.175
24 2026-08-25 08:27 639232430410720425
2039 ms 5.135.59.175
23 2026-08-25 08:10 639232420003096185
63 ms 5.135.59.175
22 2026-08-25 07:52 639232409467287444
40 ms 5.135.59.175
21 2026-08-25 07:35 639232399077195997
44 ms 5.135.59.175
20 2026-08-25 07:18 639232388731528337
41 ms 5.135.59.175
19 2026-08-25 07:00 639232378288598612
98 ms 5.135.59.175
18 2026-08-25 06:07 639232346196373643
32 ms 5.135.59.175
17 2026-08-25 05:50 639232336112370741
40 ms 5.135.59.175
16 2026-08-25 05:33 639232326146508970
36 ms 5.135.59.175
15 2026-08-25 05:17 639232316189381720
3 ms 5.135.59.175
14 2026-08-25 05:00 639232306217998913
3 ms 5.135.59.175
13 2026-08-25 04:44 639232296255744174
61 ms 5.135.59.175
12 2026-08-25 04:26 639232286095760789
47 ms 5.135.59.175
11 2026-08-25 04:10 639232276086186273
33 ms 5.135.59.175
10 2026-08-25 03:53 639232265900986425
2014 ms 5.135.59.175
9 2026-08-25 03:36 639232255723518075
45 ms 5.135.59.175
8 2026-08-25 03:19 639232245484452890
23 ms 5.135.59.175
7 2026-08-25 03:02 639232235157175331
42 ms 5.135.59.175
6 2026-08-25 02:08 639232203197189095
29 ms 5.135.59.175
5 2026-08-25 01:51 639232192844564298
19 ms 5.135.59.175
4 2026-08-25 01:34 639232182496008942
33 ms 5.135.59.175
3 2026-08-25 01:17 639232172197053132
20 ms 5.135.59.175
2 2026-08-25 00:23 639232140250307418
39 ms 5.135.59.175
1 2026-08-25 00:06 639232129927860324
48 ms 5.135.59.175