This page lists every .dk domain whose delegation includes the nameserver ns2.asom-net.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.
The nameserver ns2.asom-net.dk appears in the delegation of 21 .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, 19 (90.5%) validate as secure — comfortably above the zone-wide average of 63.9%, while 2 (9.5%) 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 21 timed domains, our resolver needed 143 ms on average to answer an A query and 157 ms for an NS query. Per nameserver set below.
Not profiled: it did not answer at all. Retried every few days.
| Nameserver set | Domains | Avg response (A) | NS lookup |
|---|---|---|---|
| ns1.asom-net.dk · ns2.asom-net.dk | 20 | 148 ms | 163 ms |
| ns1.asom-net.dk · ns2.asom-net.dk · ns3.as60111.net | 1 | 46 ms | 38 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 zone | Prefix | Prefixes | Checked |
|---|---|---|---|
| 0.2.c.5.2.0.a.2.ip6.arpa | 2a02:5c20::/32 | 1 | 2026-10-18 |
| 118.157.185.in-addr.arpa | 185.157.118.0/24 | 1 | 2026-10-02 |
| 146.199.62.in-addr.arpa | 62.199.146.0/24 | 1 | 2026-10-16 |
| 150.199.62.in-addr.arpa | 62.199.150.0/24 | 1 | 2026-10-16 |
| 156.255.185.in-addr.arpa | 185.255.156.0/24 | 1 | 2026-10-17 |
| 157.255.185.in-addr.arpa | 185.255.157.0/24 | 1 | 2026-10-16 |
| 204.182.185.in-addr.arpa | 185.182.204.0/24 | 1 | 2026-10-18 |
| 205.182.185.in-addr.arpa | 185.182.205.0/24 | 1 | 2026-10-16 |
| 206.182.185.in-addr.arpa | 185.182.206.0/24 | 1 | 2026-10-16 |
| 207.182.185.in-addr.arpa | 185.182.207.0/24 | 1 | 2026-10-16 |
| 220.125.185.in-addr.arpa | 185.125.220.0/24 | 1 | 2026-10-19 |
| 222.125.185.in-addr.arpa | 185.125.222.0/24 | 1 | 2026-10-16 |
| 252.143.185.in-addr.arpa | 185.143.252.0/24 | 1 | 2026-10-18 |
| 253.143.185.in-addr.arpa | 185.143.253.0/24 | 1 | 2026-10-16 |
| 254.143.185.in-addr.arpa | 185.143.254.0/24 | 1 | 2026-10-16 |
in-addr.arpa / ip6.arpa zones delegated to ns2.asom-net.dk, 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…