Reverse NS Lookup

Find all domains using this nameserver

This page lists every .dk domain whose delegation includes the nameserver ns2.web24tech.com, together with its IP addresses, network, zone-transfer and ANY-query behaviour, the protocols and RFCs it supports (TCP, EDNS, cookies, NSID, DNS over TLS/HTTPS …), the nameserver sets it is used in and how fast those sets answer. Use it to size a DNS provider, audit a migration or find domains still pointing at an old server. Data comes from our own scanners, which re-resolve every .dk domain in the zone roughly once a week.

ns2.web24tech.com at a glance#

nameserver profile from our scan data

The nameserver ns2.web24tech.com appears in the delegation of 609 .dk domains in our dataset — 0.05% of every scanned .dk domain. The full list is below — here is how those domains look under the hood.

On the DNSSEC side, 0 (0.0%) validate as secure — below the zone-wide average of 63.9%, while 609 (100.0%) are unsigned, with none failing validation outright.

Delegation health looks clean, too: none of these domains currently register as lame delegations at this nameserver.

Response time: across 609 timed domains, our resolver needed 118 ms on average to answer an A query and 129 ms for an NS query. Per nameserver set below.

ns2.web24tech.com#

Probed 2026-11-15 00:34
Network
Probes
AXFR Refused
IXFR Refused
Glue N/A
ANY No response
Version Hidden

Protocols & RFCs#

probed 2026-11-14 12:55

Not profiled: it did not answer at all. Retried every few days.

Response time over time#

31 days
0 ms1,745 ms3,491 ms5,236 ms6,981 ms2026-07-23: median 1,616 ms, p90 8,036 ms, 5 scans2026-07-26: median 72 ms, p90 179 ms, 5 scans2026-08-22: median 84 ms, p90 102 ms, 25 scans2026-08-25: median 48 ms, p90 90 ms, 7 scans2026-09-07: median 71 ms, p90 82 ms, 13 scans2026-09-08: median 59 ms, p90 75 ms, 16 scans2026-09-09: median 51 ms, p90 70 ms, 7 scans2026-09-10: median 55 ms, p90 94 ms, 29 scans2026-09-11: median 57 ms, p90 65 ms, 31 scans2026-09-12: median 54 ms, p90 79 ms, 25 scans2026-09-16: median 55 ms, p90 58 ms, 6 scans2026-09-17: median 53 ms, p90 70 ms, 7 scans2026-09-19: median 50 ms, p90 53 ms, 5 scans2026-09-23: median 49 ms, p90 63 ms, 5 scans2026-09-24: median 51 ms, p90 65 ms, 5 scans2026-09-29: median 51 ms, p90 77 ms, 6 scans2026-10-09: median 58 ms, p90 74 ms, 31 scans2026-10-21: median 46 ms, p90 1,199 ms, 36 scans2026-10-22: median 47 ms, p90 1,197 ms, 26 scans2026-10-23: median 48 ms, p90 1,202 ms, 30 scans2026-10-24: median 49 ms, p90 1,200 ms, 37 scans2026-10-25: median 49 ms, p90 1,198 ms, 27 scans2026-10-26: median 46 ms, p90 1,201 ms, 22 scans2026-10-27: median 52 ms, p90 1,203 ms, 30 scans2026-10-28: median 52 ms, p90 1,211 ms, 22 scans2026-10-29: median 48 ms, p90 1,201 ms, 38 scans2026-10-30: median 44 ms, p90 1,196 ms, 29 scans2026-10-31: median 47 ms, p90 1,192 ms, 24 scans2026-11-01: median 47 ms, p90 63 ms, 32 scans2026-11-02: median 46 ms, p90 1,193 ms, 26 scans2026-11-03: median 48 ms, p90 1,197 ms, 14 scans2026-07-232026-09-292026-11-03

The p90 line is clipped at the top of the chart on its worst days (highest p90 8,036 ms).

48 ms median on 2026-11-03p90 1,197 ms14 timed scanssolid: median · dashed: 90th percentile
ScannerDaysTimed scansTypical medianTypical p90
Reference scanner charted1439347 ms1,198 ms
Scanner 2301,02554 ms63 ms
Scanner 3318654 ms890 ms

Time our reference scanner needed, through its own resolver, to answer the first A query for .dk domains delegated to ns2.web24tech.com, per calendar day (lame delegations excluded). It includes the resolver and the network path, and the resolver picks the fastest nameserver of each delegation, so it describes the nameserver sets this server appears in rather than this one server. Other scanners sit elsewhere and see different absolute numbers (table above); read the line for changes over time. Days with fewer than 5 timed scans are left out.

Nameserver sets using ns2.web24tech.com#

top 1 by domains
Nameserver setDomainsAvg response (A)NS lookup
ns1.web24tech.com · ns2.web24tech.com 609 118 ms 129 ms

Times are the scanner's own lookups through its resolver on each domain's latest scan, so they include resolver overhead; compare sets with each other rather than reading them as raw authoritative round-trip times.

📈 DNSSEC Status Over Time

Loading…