Reverse NS Lookup

Find all domains using this nameserver

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

ns.inwx.de at a glance#

nameserver profile from our scan data

The nameserver ns.inwx.de appears in the delegation of 523 .dk domains in our dataset — 0.04% of every scanned .dk domain. The full list is below — here is how those domains look under the hood.

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

One thing worth flagging: 4 of these domains (0.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 519 timed domains, our resolver needed 87 ms on average to answer an A query and 64 ms for an NS query. Per nameserver set below.

ns.inwx.de#

Probed 2026-11-14 14:05
Network
Probes
AXFR Refused
IXFR Refused
Glue N/A
ANY Answers
Version reg-sto1

Protocols & RFCs#

probed 2026-11-08 12:57
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 1400 (above the 1232 of DNS Flag Day 2020)Extension 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 5001Yes reg-sto1_customer3_pdnsNames the server instance that answered (useful behind anycast).
TCP keepaliveRFC 7828NoAnnounces how long an idle TCP connection is kept open.
Client subnet (ECS)RFC 7871NoLets 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 192.174.68.104 with questions about oellegaard.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#

20 days
0 ms54 ms108 ms162 ms216 ms2026-08-24: median 43 ms, p90 110 ms, 10 scans2026-08-25: median 42 ms, p90 45 ms, 5 scans2026-08-27: median 41 ms, p90 1,784 ms, 7 scans2026-10-09: median 50 ms, p90 75 ms, 26 scans2026-10-21: median 36 ms, p90 49 ms, 26 scans2026-10-22: median 38 ms, p90 44 ms, 23 scans2026-10-23: median 38 ms, p90 53 ms, 35 scans2026-10-24: median 36 ms, p90 46 ms, 22 scans2026-10-25: median 36 ms, p90 42 ms, 26 scans2026-10-26: median 38 ms, p90 52 ms, 14 scans2026-10-27: median 37 ms, p90 44 ms, 27 scans2026-10-28: median 37 ms, p90 47 ms, 31 scans2026-10-29: median 33 ms, p90 44 ms, 26 scans2026-10-30: median 37 ms, p90 48 ms, 36 scans2026-10-31: median 38 ms, p90 53 ms, 29 scans2026-11-01: median 36 ms, p90 44 ms, 29 scans2026-11-02: median 36 ms, p90 41 ms, 23 scans2026-11-03: median 35 ms, p90 45 ms, 14 scans2026-11-04: median 37 ms, p90 42 ms, 6 scans2026-11-12: median 37 ms, p90 43 ms, 5 scans2026-08-242026-10-262026-11-12

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

37 ms median on 2026-11-12p90 43 ms5 timed scanssolid: median · dashed: 90th percentile
ScannerDaysTimed scansTypical medianTypical p90
Reference scanner charted1637237 ms44 ms
Scanner 242147 ms51 ms

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

8 days
0.0 ms4.0 ms8.0 ms12.0 ms16.0 ms2026-11-10: median 13.4 ms, p90 13.8 ms, 5 answers2026-11-11: median 13.1 ms, p90 14.5 ms, 8 answers2026-11-12: median 13.2 ms, p90 14.5 ms, 8 answers2026-11-13: median 13.2 ms, p90 14.8 ms, 8 answers2026-11-14: median 13.1 ms, p90 14.5 ms, 8 answers2026-11-15: median 13.3 ms, p90 14.8 ms, 8 answers2026-11-16: median 13.2 ms, p90 14.4 ms, 7 answers2026-11-17: median 12.9 ms, p90 13.3 ms, 4 answers2026-11-102026-11-132026-11-17
12.9 ms median on 2026-11-17p90 13.3 mssolid: median · dashed: 90th percentile

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

One SOA query (no recursion, UDP) sent straight to 192.174.68.104 (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 ns.inwx.de#

top 6 by domains
Nameserver setDomainsAvg response (A)NS lookup
ns.inwx.de · ns2.inwx.de · ns3.inwx.eu 474 89 ms 63 ms
ns.inwx.de · ns2.inwx.de · ns3.inwx.de 28 74 ms 69 ms
dns3.cloudns.net · dns4.cloudns.net · ns.inwx.de · ns2.inwx.de 12 41 ms 43 ms
ns.inwx.de · ns1.first-ns.de · ns2.inwx.de · robotns2.second-ns.de 4 75 ms 132 ms
ns.inwx.de · ns2.inwx.de · ns3.inwx.eu · ns4.inwx.com · ns5.inwx.net 3 127 ms 72 ms
ns-global.kjsl.com · ns.inwx.de · ns1.he.net 2 73 ms 27 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.

Reverse DNS zones served#

5 zones
Reverse zonePrefixPrefixesChecked
104.181.185.in-addr.arpa185.181.104.0/2412026-11-16
105.135.45.in-addr.arpa45.135.105.0/2412026-11-13
105.181.185.in-addr.arpa185.181.105.0/2412026-11-13
156.87.45.in-addr.arpa45.87.156.0/2412026-11-14
158.87.45.in-addr.arpa45.87.158.0/2412026-11-16

in-addr.arpa / ip6.arpa zones delegated to ns.inwx.de, found from the SOA of the reverse name of each IPv4 /24 behind the zone's websites (and any CIDR page viewed), so the zone is the real delegation point, at whatever prefix length it sits. A /24 whose reverse delegation is broken (SERVFAIL) is not credited to anyone.

📈 DNSSEC Status Over Time

Loading…