Reverse NS Lookup

Find all domains using this nameserver

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

ns5.linode.com at a glance#

nameserver profile from our scan data

The nameserver ns5.linode.com appears in the delegation of 1,068 .dk domains in our dataset — 0.08% of every scanned .dk domain. The full list is below — here is how those domains look under the hood.

On the DNSSEC side, 5 (0.5%) validate as secure — below the zone-wide average of 63.9%, while 999 (93.5%) are unsigned, with none failing validation outright — a further 64 come back indeterminate.

One thing worth flagging: 62 of these domains (5.8%) 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 1,006 timed domains, our resolver needed 121 ms on average to answer an A query and 111 ms for an NS query. Per nameserver set below.

ns5.linode.com#

Probed 2026-11-13 16:36
Network
Probes
AXFR Refused
IXFR Refused
Glue N/A
ANY REFUSED
Version Linode.com DNS

Protocols & RFCs#

probed 2026-11-08 12:35
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 512Extension 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 9018NoLightweight server cookies against spoofing and amplification.
NSIDRFC 5001NoNames the server instance that answered (useful behind anycast).
TCP keepaliveRFC 7828NoAnnounces how long an idle TCP connection is kept open.
Client subnet (ECS)RFC 7871Yes — tailors answers (scope /32)Lets the nameserver tailor answers to the client's network (CDNs, geo-DNS).
Extended DNS errorsRFC 8914—Explains 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 92.123.95.2 with questions about danskvandrelaug.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#

39 days
0 ms166 ms333 ms499 ms665 ms2026-07-19: median 77 ms, p90 8,059 ms, 6 scans2026-07-22: median 122 ms, p90 536 ms, 5 scans2026-07-25: median 88 ms, p90 154 ms, 5 scans2026-07-26: median 154 ms, p90 223 ms, 5 scans2026-08-24: median 58 ms, p90 156 ms, 16 scans2026-08-25: median 51 ms, p90 175 ms, 6 scans2026-08-26: median 49 ms, p90 133 ms, 6 scans2026-08-28: median 43 ms, p90 189 ms, 8 scans2026-09-23: median 56 ms, p90 185 ms, 7 scans2026-09-24: median 37 ms, p90 167 ms, 6 scans2026-09-25: median 46 ms, p90 58 ms, 10 scans2026-09-26: median 52 ms, p90 146 ms, 5 scans2026-09-27: median 51 ms, p90 135 ms, 7 scans2026-09-28: median 58 ms, p90 161 ms, 6 scans2026-09-29: median 61 ms, p90 197 ms, 9 scans2026-09-30: median 57 ms, p90 135 ms, 7 scans2026-10-05: median 50 ms, p90 127 ms, 5 scans2026-10-09: median 73 ms, p90 165 ms, 67 scans2026-10-12: median 55 ms, p90 113 ms, 5 scans2026-10-18: median 54 ms, p90 123 ms, 5 scans2026-10-19: median 55 ms, p90 143 ms, 5 scans2026-10-20: median 111 ms, p90 181 ms, 9 scans2026-10-21: median 48 ms, p90 175 ms, 49 scans2026-10-22: median 48 ms, p90 150 ms, 51 scans2026-10-23: median 49 ms, p90 145 ms, 56 scans2026-10-24: median 46 ms, p90 139 ms, 53 scans2026-10-25: median 50 ms, p90 176 ms, 62 scans2026-10-26: median 53 ms, p90 172 ms, 49 scans2026-10-27: median 49 ms, p90 176 ms, 56 scans2026-10-28: median 48 ms, p90 150 ms, 53 scans2026-10-29: median 47 ms, p90 174 ms, 56 scans2026-10-30: median 54 ms, p90 149 ms, 57 scans2026-10-31: median 49 ms, p90 171 ms, 35 scans2026-11-01: median 49 ms, p90 171 ms, 48 scans2026-11-02: median 46 ms, p90 144 ms, 44 scans2026-11-03: median 50 ms, p90 142 ms, 14 scans2026-11-04: median 123 ms, p90 148 ms, 9 scans2026-11-07: median 40 ms, p90 142 ms, 6 scans2026-11-13: median 56 ms, p90 176 ms, 7 scans2026-07-192026-10-182026-11-13

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

56 ms median on 2026-11-13p90 176 ms7 timed scanssolid: median · dashed: 90th percentile
ScannerDaysTimed scansTypical medianTypical p90
Reference scanner charted2072449 ms150 ms
Scanner 253163 ms155 ms
Scanner 316100 ms292 ms
Scanner 4211100 ms322 ms

Time our reference scanner needed, through its own resolver, to answer the first A query for .dk domains delegated to ns5.linode.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.

Direct round-trip time#

7 days
0 ms100 ms200 ms300 ms400 ms2026-11-10: median 91 ms, p90 111 ms, 5 answers2026-11-11: median 25 ms, p90 155 ms, 8 answers2026-11-12: median 27 ms, p90 154 ms, 8 answers2026-11-13: median 27 ms, p90 158 ms, 8 answers2026-11-14: median 92 ms, p90 126 ms, 8 answers2026-11-15: median 93 ms, p90 1,009 ms, 8 answers2026-11-16: median 28 ms, p90 160 ms, 7 answers2026-11-102026-11-132026-11-16

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

28 ms median on 2026-11-16p90 160 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 92.123.95.2 (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 ns5.linode.com#

top 2 by domains
Nameserver setDomainsAvg response (A)NS lookup
ns1.linode.com · ns2.linode.com · ns3.linode.com · ns4.linode.com · ns5.linode.com 1,066 121 ms 111 ms
ns1.linode.com · ns1.markright.org · ns2.linode.com · ns3.linode.com · ns4.linode.com · ns5.linode.com 2 93 ms 100 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…