Reverse NS Lookup

Find all domains using this nameserver

This page lists every .dk domain whose delegation includes the nameserver dns5.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.

dns5.dk at a glance#

nameserver profile from our scan data

The nameserver dns5.dk appears in the delegation of 146 .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, 125 (85.6%) validate as secure — comfortably above the zone-wide average of 63.9%, while 0 (0.0%) are unsigned, and 9 (6.2%) currently fail validation outright (bogus) — a further 12 come back indeterminate.

One thing worth flagging: 21 of these domains (14.4%) 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 125 timed domains, our resolver needed 130 ms on average to answer an A query and 138 ms for an NS query. Per nameserver set below.

dns5.dk#

Probed 2026-11-16 21:48
Network
Probes
AXFR Refused
IXFR Refused
Glue 168.119.185.218,2a01:4f8:c010:3311::1
ANY Answers
Version unknown

Protocols & RFCs#

probed 2026-11-08 15:32
Protocol / featureStandardSupportedWhat it is
DNS over TCPRFC 7766, RFC 9210YesRequired for every nameserver: large answers, DNSSEC and truncation fall back to TCP.
EDNS(0)RFC 6891Yes UDP buffer 1232Extension mechanism behind DNSSEC, cookies and every other option below.
EDNS version negotiationRFC 6891BADVERS (correct)A query with EDNS version 1 must get BADVERS back.
Unknown EDNS optionsRFC 6891Ignored (correct)An option the server does not know must be ignored, not make the query fail.
DNS cookiesRFC 7873, RFC 9018YesLightweight server cookies against spoofing and amplification.
NSIDRFC 5001NoNames the server instance that answered (useful behind anycast).
TCP keepaliveRFC 7828YesAnnounces how long an idle TCP connection is kept open.
Client subnet (ECS)RFC 7871Understood, not used for this zone (scope /0)Lets the nameserver tailor answers to the client's network (CDNs, geo-DNS).
Extended DNS errorsRFC 8914YesExplains a refusal or failure with an error code, seen on a query outside its zones.
ZONEVERSIONRFC 9660NoReports the zone serial it answered from.
DNS error reportingRFC 9567NoAdvertises a reporting agent resolvers can send failures to.
Refuses recursionRFC 5358YesAn authoritative server should not resolve other people's names for anyone who asks.
DNS over TLS (DoT)RFC 7858, RFC 9539NoEncrypted transport on port 853 (resolver-to-authoritative per RFC 9539).
DNS over HTTPS (DoH)RFC 8484NoEncrypted transport on port 443 (/dns-query). Rare on authoritatives.
DNS over QUIC (DoQ)RFC 9250Not probedOur probe tool cannot speak QUIC yet.

Probed over IPv4 at 168.119.185.218 with questions about 8182.dk, a zone it serves. Other addresses of an anycast or multi-server setup can differ. AXFR, IXFR and minimal ANY answers (RFC 8482) are in the probe card above. “No” for an encrypted transport means nothing answered on its port while plain DNS did. Zone-wide adoption.

Response time over time#

67 days
0 ms154 ms309 ms463 ms618 ms2026-07-21: median 83 ms, p90 240 ms, 52 scans2026-07-22: median 84 ms, p90 189 ms, 26 scans2026-07-23: median 67 ms, p90 168 ms, 6 scans2026-07-26: median 100 ms, p90 272 ms, 52 scans2026-07-27: median 91 ms, p90 144 ms, 11 scans2026-07-31: median 136 ms, p90 257 ms, 16 scans2026-08-01: median 82 ms, p90 258 ms, 16 scans2026-08-02: median 93 ms, p90 290 ms, 16 scans2026-08-03: median 123 ms, p90 214 ms, 13 scans2026-08-06: median 141 ms, p90 8,066 ms, 8 scans2026-08-07: median 93 ms, p90 8,060 ms, 8 scans2026-08-10: median 94 ms, p90 279 ms, 9 scans2026-08-11: median 90 ms, p90 263 ms, 9 scans2026-08-15: median 103 ms, p90 281 ms, 17 scans2026-08-16: median 81 ms, p90 122 ms, 6 scans2026-08-20: median 81 ms, p90 8,174 ms, 7 scans2026-08-25: median 77 ms, p90 183 ms, 12 scans2026-08-26: median 45 ms, p90 191 ms, 30 scans2026-08-27: median 120 ms, p90 195 ms, 14 scans2026-08-28: median 70 ms, p90 137 ms, 6 scans2026-08-30: median 47 ms, p90 143 ms, 24 scans2026-08-31: median 43 ms, p90 189 ms, 19 scans2026-09-01: median 42 ms, p90 192 ms, 6 scans2026-09-03: median 128 ms, p90 502 ms, 6 scans2026-09-04: median 69 ms, p90 224 ms, 20 scans2026-09-05: median 53 ms, p90 211 ms, 16 scans2026-09-06: median 128 ms, p90 219 ms, 15 scans2026-09-07: median 75 ms, p90 205 ms, 14 scans2026-09-08: median 129 ms, p90 195 ms, 5 scans2026-09-09: median 78 ms, p90 206 ms, 18 scans2026-09-10: median 62 ms, p90 204 ms, 14 scans2026-09-11: median 51 ms, p90 209 ms, 9 scans2026-09-12: median 55 ms, p90 938 ms, 7 scans2026-09-13: median 56 ms, p90 191 ms, 11 scans2026-09-14: median 60 ms, p90 202 ms, 10 scans2026-09-15: median 56 ms, p90 189 ms, 15 scans2026-09-16: median 46 ms, p90 148 ms, 11 scans2026-09-17: median 52 ms, p90 148 ms, 14 scans2026-09-18: median 143 ms, p90 210 ms, 6 scans2026-09-19: median 133 ms, p90 198 ms, 11 scans2026-09-20: median 50 ms, p90 198 ms, 16 scans2026-09-21: median 54 ms, p90 200 ms, 24 scans2026-09-22: median 50 ms, p90 189 ms, 18 scans2026-09-23: median 52 ms, p90 190 ms, 42 scans2026-09-24: median 115 ms, p90 200 ms, 21 scans2026-09-26: median 61 ms, p90 202 ms, 103 scans2026-09-27: median 56 ms, p90 201 ms, 16 scans2026-10-01: median 59 ms, p90 204 ms, 50 scans2026-10-02: median 63 ms, p90 124 ms, 14 scans2026-10-09: median 61 ms, p90 205 ms, 6 scans2026-10-11: median 51 ms, p90 198 ms, 30 scans2026-10-12: median 53 ms, p90 112 ms, 9 scans2026-10-13: median 54 ms, p90 197 ms, 36 scans2026-10-18: median 60 ms, p90 205 ms, 31 scans2026-10-19: median 63 ms, p90 212 ms, 10 scans2026-10-23: median 46 ms, p90 201 ms, 6 scans2026-10-24: median 113 ms, p90 200 ms, 12 scans2026-10-26: median 120 ms, p90 198 ms, 5 scans2026-10-28: median 107 ms, p90 199 ms, 10 scans2026-10-31: median 45 ms, p90 193 ms, 8 scans2026-11-02: median 108 ms, p90 197 ms, 17 scans2026-11-03: median 48 ms, p90 190 ms, 21 scans2026-11-04: median 43 ms, p90 192 ms, 12 scans2026-11-07: median 46 ms, p90 194 ms, 36 scans2026-11-08: median 45 ms, p90 118 ms, 13 scans2026-11-12: median 53 ms, p90 197 ms, 53 scans2026-11-13: median 46 ms, p90 194 ms, 8 scans2026-07-212026-09-132026-11-13

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

46 ms median on 2026-11-13p90 194 ms8 timed scanssolid: median · dashed: 90th percentile
ScannerDaysTimed scansTypical medianTypical p90
Reference scanner charted1424248 ms197 ms
Scanner 21330054 ms198 ms
Scanner 310154168 ms335 ms
Scanner 417122223 ms597 ms

Time our reference scanner needed, through its own resolver, to answer the first A query for .dk domains delegated to dns5.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 (table above); read the line for changes over time. Days with fewer than 5 timed scans are left out.

Direct round-trip time#

7 days
0 ms10 ms20 ms29 ms39 ms2026-11-10: median 23 ms, p90 26 ms, 5 answers2026-11-11: median 22 ms, p90 27 ms, 8 answers2026-11-12: median 22 ms, p90 36 ms, 8 answers2026-11-13: median 23 ms, p90 25 ms, 7 answers2026-11-14: median 22 ms, p90 26 ms, 8 answers2026-11-15: median 25 ms, p90 28 ms, 8 answers2026-11-16: median 26 ms, p90 29 ms, 8 answers2026-11-102026-11-132026-11-16
26 ms median on 2026-11-16p90 29 mssolid: median · dashed: 90th percentile

Answered authoritatively: 52 of 52 queries in the last 30 days.

One SOA query (no recursion, UDP) sent straight to 168.119.185.218 (IPv4) from our reference scanner about every three hours, with no resolver in between: the time is this server's own answer plus the network path from us, unlike the resolver-inclusive response time. Other addresses of an anycast or multi-server setup can differ.

Nameserver sets using dns5.dk#

top 1 by domains
Nameserver setDomainsAvg response (A)NS lookup
dns1.dk · dns2.dk · dns3.dk · dns4.dk · dns5.dk 146 130 ms 138 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…