Reverse NS Lookup

Find all domains using this nameserver

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

ns3.hostpoint.ch at a glance#

nameserver profile from our scan data

The nameserver ns3.hostpoint.ch appears in the delegation of 190 .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 190 (100.0%) are unsigned, with none failing validation outright.

Delegation health looks clean, too: none of these domains currently register as lame delegations at this nameserver.

Response time: across 190 timed domains, our resolver needed 74 ms on average to answer an A query and 75 ms for an NS query. Per nameserver set below.

ns3.hostpoint.ch#

Probed 2026-11-19 07:17
Network
Probes
AXFR Refused
IXFR Refused
Glue N/A
ANY REFUSED
Version Hostpoint DNS

Protocols & RFCs#

probed 2026-11-08 14:47
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 9018NoLightweight server cookies against spoofing and amplification.
NSIDRFC 5001Yes auth04.ext.dns.hostpoint.internalNames 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 8914NoExplains 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 217.26.60.250 with questions about socceryou.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#

58 days
0 ms41 ms81 ms122 ms162 ms2026-07-23: median 73 ms, p90 93 ms, 93 scans2026-07-24: median 83 ms, p90 97 ms, 20 scans2026-07-30: median 79 ms, p90 92 ms, 8 scans2026-07-31: median 64 ms, p90 90 ms, 22 scans2026-08-01: median 71 ms, p90 92 ms, 18 scans2026-08-02: median 68 ms, p90 110 ms, 12 scans2026-08-03: median 68 ms, p90 93 ms, 12 scans2026-08-06: median 73 ms, p90 99 ms, 18 scans2026-08-07: median 82 ms, p90 99 ms, 13 scans2026-08-08: median 75 ms, p90 95 ms, 11 scans2026-08-09: median 93 ms, p90 112 ms, 6 scans2026-08-13: median 72 ms, p90 99 ms, 19 scans2026-08-14: median 76 ms, p90 96 ms, 9 scans2026-08-20: median 77 ms, p90 107 ms, 13 scans2026-08-27: median 45 ms, p90 51 ms, 107 scans2026-08-28: median 45 ms, p90 53 ms, 32 scans2026-09-03: median 48 ms, p90 64 ms, 18 scans2026-09-04: median 50 ms, p90 79 ms, 39 scans2026-09-05: median 62 ms, p90 78 ms, 14 scans2026-09-06: median 73 ms, p90 89 ms, 14 scans2026-09-07: median 61 ms, p90 85 ms, 13 scans2026-09-10: median 56 ms, p90 150 ms, 15 scans2026-09-11: median 54 ms, p90 68 ms, 22 scans2026-09-12: median 51 ms, p90 79 ms, 23 scans2026-09-13: median 55 ms, p90 70 ms, 8 scans2026-09-14: median 62 ms, p90 137 ms, 7 scans2026-09-15: median 59 ms, p90 89 ms, 5 scans2026-09-17: median 50 ms, p90 59 ms, 20 scans2026-09-18: median 49 ms, p90 61 ms, 22 scans2026-09-19: median 49 ms, p90 54 ms, 19 scans2026-09-20: median 48 ms, p90 54 ms, 13 scans2026-09-21: median 53 ms, p90 54 ms, 10 scans2026-09-22: median 52 ms, p90 55 ms, 5 scans2026-09-23: median 48 ms, p90 79 ms, 9 scans2026-09-24: median 52 ms, p90 65 ms, 139 scans2026-09-25: median 50 ms, p90 60 ms, 23 scans2026-10-01: median 56 ms, p90 68 ms, 83 scans2026-10-02: median 55 ms, p90 74 ms, 11 scans2026-10-08: median 55 ms, p90 69 ms, 100 scans2026-10-09: median 60 ms, p90 69 ms, 18 scans2026-10-15: median 54 ms, p90 59 ms, 34 scans2026-10-16: median 56 ms, p90 71 ms, 12 scans2026-10-21: median 44 ms, p90 54 ms, 11 scans2026-10-22: median 43 ms, p90 48 ms, 10 scans2026-10-23: median 47 ms, p90 50 ms, 13 scans2026-10-24: median 44 ms, p90 56 ms, 5 scans2026-10-26: median 43 ms, p90 53 ms, 9 scans2026-10-27: median 44 ms, p90 52 ms, 11 scans2026-10-28: median 47 ms, p90 52 ms, 13 scans2026-10-29: median 44 ms, p90 47 ms, 10 scans2026-10-30: median 44 ms, p90 53 ms, 16 scans2026-10-31: median 43 ms, p90 48 ms, 13 scans2026-11-01: median 46 ms, p90 48 ms, 15 scans2026-11-02: median 42 ms, p90 49 ms, 10 scans2026-11-04: median 46 ms, p90 49 ms, 6 scans2026-11-05: median 45 ms, p90 51 ms, 69 scans2026-11-06: median 45 ms, p90 59 ms, 7 scans2026-11-12: median 44 ms, p90 51 ms, 60 scans2026-07-232026-09-182026-11-12
44 ms median on 2026-11-12p90 51 ms60 timed scanssolid: median · dashed: 90th percentile
ScannerDaysTimed scansTypical medianTypical p90
Reference scanner charted1627844 ms51 ms
Scanner 21436451 ms60 ms
Scanner 312111160 ms314 ms
Scanner 47139115 ms325 ms

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

10 days
0 ms8 ms15 ms23 ms31 ms2026-11-10: median 24 ms, p90 24 ms, 5 answers2026-11-11: median 24 ms, p90 25 ms, 8 answers2026-11-12: median 24 ms, p90 24 ms, 8 answers2026-11-13: median 24 ms, p90 25 ms, 8 answers2026-11-14: median 24 ms, p90 25 ms, 7 answers2026-11-15: median 24 ms, p90 25 ms, 8 answers2026-11-16: median 24 ms, p90 25 ms, 8 answers2026-11-17: median 24 ms, p90 29 ms, 8 answers2026-11-18: median 24 ms, p90 24 ms, 8 answers2026-11-19: median 24 ms, p90 26 ms, 3 answers2026-11-102026-11-142026-11-19
24 ms median on 2026-11-19p90 26 mssolid: median · dashed: 90th percentile

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

One SOA query (no recursion, UDP) sent straight to 217.26.60.250 (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 ns3.hostpoint.ch#

top 1 by domains
Nameserver setDomainsAvg response (A)NS lookup
ns.hostpoint.ch · ns2.hostpoint.ch · ns3.hostpoint.ch 190 74 ms 75 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#

12 zones
Reverse zonePrefixPrefixesChecked
0.0.0.0.0.0.0.0.0.7.d.0.0.0.a.2.ip6.arpa2a00:d70::/6412026-11-16
48.26.217.in-addr.arpa217.26.48.0/2412026-11-16
50.26.217.in-addr.arpa217.26.50.0/2412026-11-13
51.26.217.in-addr.arpa217.26.51.0/2412026-11-13
52.26.217.in-addr.arpa217.26.52.0/2412026-11-12
53.26.217.in-addr.arpa217.26.53.0/2412026-11-19
54.26.217.in-addr.arpa217.26.54.0/2412026-11-19
55.26.217.in-addr.arpa217.26.55.0/2412026-11-13
56.26.217.in-addr.arpa217.26.56.0/2412026-11-16
60.26.217.in-addr.arpa217.26.60.0/2412026-11-13
61.26.217.in-addr.arpa217.26.61.0/2412026-11-13
63.26.217.in-addr.arpa217.26.63.0/2412026-11-13

in-addr.arpa / ip6.arpa zones delegated to ns3.hostpoint.ch, 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…