Reverse NS Lookup
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 dataThe 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:34Protocols & RFCs#
probed 2026-11-14 12:55Not profiled: it did not answer at all. Retried every few days.
Response time over time#
31 daysThe p90 line is clipped at the top of the chart on its worst days (highest p90 8,036 ms).
| Scanner | Days | Timed scans | Typical median | Typical p90 |
|---|---|---|---|---|
| Reference scanner charted | 14 | 393 | 47 ms | 1,198 ms |
| Scanner 2 | 30 | 1,025 | 54 ms | 63 ms |
| Scanner 3 | 3 | 18 | 654 ms | 890 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 set | Domains | Avg 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.
Loading…