Reverse NS Lookup
This page lists every .dk domain whose delegation includes the nameserver ns2.mysmt.net, 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.
ns2.mysmt.net at a glance#
nameserver profile from our scan dataThe nameserver ns2.mysmt.net 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.
ns2.mysmt.net#
Probed 2026-09-29 23:28Protocols & RFCs#
probed 2026-11-15 10:26Not 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 sets using ns2.mysmt.net#
top 1 by domains| Nameserver set | Domains | Avg response (A) | NS lookup |
|---|---|---|---|
| ns1.mysmt.net · ns2.mysmt.net | 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.
Loading…