Reverse NS Lookup

Find all domains using this nameserver

This page lists every .dk domain whose delegation includes the nameserver ns2.mono.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.mono.net at a glance#

nameserver profile from our scan data

The nameserver ns2.mono.net appears in the delegation of 1,545 .dk domains in our dataset — 0.12% 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 1,412 (91.4%) are unsigned, with none failing validation outright — a further 133 come back indeterminate.

One thing worth flagging: 11 of these domains (0.7%) 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.

Response time: across 1,534 timed domains, our resolver needed 2,709 ms on average to answer an A query and 1,854 ms for an NS query. Per nameserver set below.

ns2.mono.net#

Probed 2026-11-12 00:11
Network
Probes
AXFR Refused
IXFR Refused
Glue N/A
ANY No response
Version Hidden

Protocols & RFCs#

probed 2026-11-08 14:58
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 1680 (above the 1232 of DNS Flag Day 2020)Extension 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 ip-172-31-42-143Names 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 8914—Explains 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 5358—An 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 185.130.160.1 with questions about foredrag-specialstyrker.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#

19 days
0 ms4,330 ms8,659 ms12,989 ms17,319 ms2026-07-21: median 216 ms, p90 8,046 ms, 6 scans2026-07-23: median 87 ms, p90 9,587 ms, 5 scans2026-08-25: median 6,003 ms, p90 16,036 ms, 25 scans2026-10-09: median 3,809 ms, p90 8,041 ms, 69 scans2026-10-20: median 3,389 ms, p90 5,502 ms, 5 scans2026-10-21: median 4,688 ms, p90 8,027 ms, 49 scans2026-10-22: median 3,673 ms, p90 8,028 ms, 62 scans2026-10-23: median 4,443 ms, p90 8,031 ms, 48 scans2026-10-24: median 4,670 ms, p90 7,439 ms, 61 scans2026-10-25: median 4,411 ms, p90 8,033 ms, 61 scans2026-10-26: median 5,034 ms, p90 8,031 ms, 44 scans2026-10-27: median 4,270 ms, p90 8,028 ms, 59 scans2026-10-28: median 5,146 ms, p90 8,032 ms, 49 scans2026-10-29: median 3,445 ms, p90 8,027 ms, 58 scans2026-10-30: median 3,798 ms, p90 6,173 ms, 60 scans2026-10-31: median 3,757 ms, p90 7,235 ms, 56 scans2026-11-01: median 5,170 ms, p90 8,029 ms, 59 scans2026-11-02: median 4,658 ms, p90 8,027 ms, 56 scans2026-11-03: median 4,240 ms, p90 5,966 ms, 10 scans2026-07-212026-10-252026-11-03
4,240 ms median on 2026-11-03p90 5,966 ms10 timed scanssolid: median · dashed: 90th percentile

Time our reference scanner needed, through its own resolver, to answer the first A query for .dk domains delegated to ns2.mono.net, 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; read the line for changes over time. Days with fewer than 5 timed scans are left out.

Direct round-trip time#

7 days
0 ms7 ms14 ms21 ms28 ms2026-11-10: median 23 ms, p90 25 ms, 5 answers2026-11-11: median 20 ms, p90 25 ms, 8 answers2026-11-12: median 20 ms, p90 25 ms, 8 answers2026-11-13: median 20 ms, p90 26 ms, 8 answers2026-11-14: median 20 ms, p90 24 ms, 8 answers2026-11-15: median 20 ms, p90 25 ms, 8 answers2026-11-16: median 22 ms, p90 25 ms, 7 answers2026-11-102026-11-132026-11-16
22 ms median on 2026-11-16p90 25 mssolid: median · dashed: 90th percentile

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

One SOA query (no recursion, UDP) sent straight to 185.130.160.1 (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 ns2.mono.net#

top 3 by domains
Nameserver setDomainsAvg response (A)NS lookup
ns1.mono.net · ns2.mono.net · ns3.mono.net · ns4.mono.net 1,045 2,748 ms 1,838 ms
ns1.mono.net · ns2.mono.net · ns3.mono.net 495 2,624 ms 1,889 ms
ns1.mono.net · ns2.mono.net 5 4,048 ms 1,180 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.

📈 DNSSEC Status Over Time

Loading…