This page lists every .dk domain whose delegation includes the nameserver ns3.pi.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.
The nameserver ns3.pi.dk appears in the delegation of 653 .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 636 (97.4%) are unsigned, with none failing validation outright — a further 17 come back indeterminate.
One thing worth flagging: 16 of these domains (2.5%) 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.
Response time: across 637 timed domains, our resolver needed 188 ms on average to answer an A query and 207 ms for an NS query. Per nameserver set below.
Not profiled: it did not answer authoritatively for the zones we asked it about. Retried every few days.
| Nameserver set | Domains | Avg response (A) | NS lookup |
|---|---|---|---|
| ns.pi.dk · ns2.pi.dk · ns3.pi.dk | 615 | 195 ms | 211 ms |
| ns.pi.dk · ns2.pi.dk · ns3.pi.dk · ns4.pi.dk · ns5.pi.dk | 38 | 44 ms | 123 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…