This page lists every .dk domain whose delegation includes the nameserver ns1.zap-hosting.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.
The nameserver ns1.zap-hosting.com appears in the delegation of 3 .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 0 (0.0%) are unsigned, with none failing validation outright — a further 3 come back indeterminate.
One thing worth flagging: 3 of these domains (100.0%) 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.
Not profiled: every domain we hold for it is a lame delegation, so there is no zone to ask it about. Retried every few days.
| Nameserver set | Domains | Avg response (A) | NS lookup |
|---|---|---|---|
| ns1.zap-hosting.com · ns2.zap-hosting.com | 3 | — | — |
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 zone | Prefix | Prefixes | Checked |
|---|---|---|---|
| 127.23.193.in-addr.arpa | 193.23.127.0/24 | 1 | 2026-10-16 |
| 168.189.147.in-addr.arpa | 147.189.168.0/24 | 1 | 2026-10-20 |
| 171.189.147.in-addr.arpa | 147.189.171.0/24 | 1 | 2026-10-16 |
| 173.189.147.in-addr.arpa | 147.189.173.0/24 | 1 | 2026-10-09 |
| 174.189.147.in-addr.arpa | 147.189.174.0/24 | 1 | 2026-10-16 |
| 232.255.134.in-addr.arpa | 134.255.232.0/24 | 1 | 2026-10-22 |
| 233.255.134.in-addr.arpa | 134.255.233.0/24 | 1 | 2026-10-16 |
| 252.255.134.in-addr.arpa | 134.255.252.0/24 | 1 | 2026-10-18 |
| 44.42.92.in-addr.arpa | 92.42.44.0/24 | 1 | 2026-10-18 |
| 46.42.92.in-addr.arpa | 92.42.46.0/24 | 1 | 2026-10-16 |
| 47.42.92.in-addr.arpa | 92.42.47.0/24 | 1 | 2026-10-16 |
| 52.237.87.in-addr.arpa | 87.237.52.0/24 | 1 | 2026-10-18 |
| 55.237.87.in-addr.arpa | 87.237.55.0/24 | 1 | 2026-10-16 |
| 56.214.88.in-addr.arpa | 88.214.56.0/24 | 1 | 2026-10-19 |
| 57.214.88.in-addr.arpa | 88.214.57.0/24 | 1 | 2026-10-16 |
| 59.214.88.in-addr.arpa | 88.214.59.0/24 | 1 | 2026-10-16 |
in-addr.arpa / ip6.arpa zones delegated to ns1.zap-hosting.com, 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.
Loading…