This page lists every .dk domain whose delegation includes the nameserver ns2.yourhostingaccount.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 ns2.yourhostingaccount.com appears in the delegation of 38 .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 38 (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 38 timed domains, our resolver needed 174 ms on average to answer an A query and 76 ms for an NS query. Per nameserver set below.
Not profiled: it did not answer authoritatively for the zones we asked it about. Retried every few days.
| Nameserver set | Domains | Avg response (A) | NS lookup |
|---|---|---|---|
| ns1.yourhostingaccount.com · ns2.yourhostingaccount.com | 38 | 174 ms | 76 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 |
|---|---|---|---|
| 1.113.38.in-addr.arpa | 38.113.1.0/24 | 1 | 2026-10-20 |
| 128.96.66.in-addr.arpa | 66.96.128.0/24 | 1 | 2026-10-20 |
| 132.96.66.in-addr.arpa | 66.96.132.0/24 | 1 | 2026-10-16 |
| 146.96.66.in-addr.arpa | 66.96.146.0/24 | 1 | 2026-10-02 |
| 147.96.66.in-addr.arpa | 66.96.147.0/24 | 1 | 2026-10-16 |
| 149.96.66.in-addr.arpa | 66.96.149.0/24 | 1 | 2026-10-16 |
| 160.96.66.in-addr.arpa | 66.96.160.0/24 | 1 | 2026-10-16 |
| 162.96.66.in-addr.arpa | 66.96.162.0/24 | 1 | 2026-10-16 |
| 163.96.66.in-addr.arpa | 66.96.163.0/24 | 1 | 2026-10-16 |
| 224.254.65.in-addr.arpa | 65.254.224.0/24 | 1 | 2026-10-20 |
| 227.254.65.in-addr.arpa | 65.254.227.0/24 | 1 | 2026-10-16 |
| 248.254.65.in-addr.arpa | 65.254.248.0/24 | 1 | 2026-10-16 |
in-addr.arpa / ip6.arpa zones delegated to ns2.yourhostingaccount.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…