Reverse NS Lookup
This page lists every .dk domain whose delegation includes the nameserver dns-d.duelhost.dk, 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.
dns-d.duelhost.dk at a glance#
nameserver profile from our scan dataThe nameserver dns-d.duelhost.dk appears in the delegation of 18 .dk domains in our dataset — <0.01% 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 0 (0.0%) are unsigned, with none failing validation outright — a further 18 come back indeterminate.
One thing worth flagging: 18 of these domains (100.0%) look like lame delegations — the .dk registry still points them here, but this nameserver doesn't answer authoritatively for the zone, which usually means the hosting was cancelled and the delegation was left dangling.
dns-d.duelhost.dk#
Probed 2026-10-27 00:44Protocols & RFCs#
probed 2026-11-14 20:21Not profiled: every domain we hold for it is a lame delegation, so there is no zone to ask it about. Retried every few days.
Response time over time#
42 daysThe p90 line is clipped at the top of the chart on its worst days (highest p90 8,106 ms).
Time our reference scanner needed, through its own resolver, to answer the first A query for .dk domains delegated to dns-d.duelhost.dk, 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; read the line for changes over time. Days with fewer than 5 timed scans are left out.
Nameserver sets using dns-d.duelhost.dk#
top 1 by domains| Nameserver set | Domains | Avg response (A) | NS lookup |
|---|---|---|---|
| dns-c.duelhost.dk · dns-d.duelhost.dk | 18 | — | — |
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…