Reverse NS Lookup

Find all domains using this nameserver

This page lists every .dk domain whose delegation includes the nameserver ns1.bdm.microsoftonline.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.

ns1.bdm.microsoftonline.com at a glance#

nameserver profile from our scan data

The nameserver ns1.bdm.microsoftonline.com appears in the delegation of 2,341 .dk domains in our dataset — 0.18% of every scanned .dk domain. The full list is below — here is how those domains look under the hood.

On the DNSSEC side, 11 (0.5%) validate as secure — below the zone-wide average of 63.9%, while 2,303 (98.4%) are unsigned, and 1 (0.0%) currently fail validation outright (bogus) — a further 26 come back indeterminate.

One thing worth flagging: 25 of these domains (1.1%) 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 2,316 timed domains, our resolver needed 45 ms on average to answer an A query and 39 ms for an NS query. Per nameserver set below.

ns1.bdm.microsoftonline.com#

Probed 2026-11-12 16:52
Network
Probes
AXFR Refused
IXFR Refused
Glue N/A
ANY Refused (RFC 8482)
Version Hidden

Protocols & RFCs#

probed 2026-11-08 12:23
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 1232Extension 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 5001NoNames the server instance that answered (useful behind anycast).
TCP keepaliveRFC 7828NoAnnounces how long an idle TCP connection is kept open.
Client subnet (ECS)RFC 7871Understood, not used for this zone (scope /0)Lets the nameserver tailor answers to the client's network (CDNs, geo-DNS).
Extended DNS errorsRFC 8914NoExplains 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 5358YesAn 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 13.107.236.208 with questions about strandhytten.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 ms75 ms149 ms224 ms298 ms2026-07-24: median 69 ms, p90 93 ms, 7 scans2026-08-24: median 40 ms, p90 86 ms, 38 scans2026-08-25: median 34 ms, p90 16,036 ms, 6 scans2026-10-09: median 42 ms, p90 59 ms, 113 scans2026-10-20: median 27 ms, p90 33 ms, 12 scans2026-10-21: median 28 ms, p90 35 ms, 115 scans2026-10-22: median 28 ms, p90 32 ms, 91 scans2026-10-23: median 28 ms, p90 33 ms, 101 scans2026-10-24: median 28 ms, p90 34 ms, 96 scans2026-10-25: median 28 ms, p90 33 ms, 122 scans2026-10-26: median 30 ms, p90 35 ms, 112 scans2026-10-27: median 28 ms, p90 34 ms, 120 scans2026-10-28: median 28 ms, p90 34 ms, 122 scans2026-10-29: median 27 ms, p90 34 ms, 108 scans2026-10-30: median 28 ms, p90 31 ms, 87 scans2026-10-31: median 27 ms, p90 32 ms, 87 scans2026-11-01: median 28 ms, p90 33 ms, 120 scans2026-11-02: median 27 ms, p90 32 ms, 118 scans2026-11-03: median 25 ms, p90 31 ms, 25 scans2026-07-242026-10-252026-11-03

The p90 line is clipped at the top of the chart on its worst days (highest p90 16,036 ms).

25 ms median on 2026-11-03p90 31 ms25 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 ns1.bdm.microsoftonline.com, 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.0 ms2.2 ms4.4 ms6.7 ms8.9 ms2026-11-10: median 6.9 ms, p90 7.4 ms, 5 answers2026-11-11: median 6.6 ms, p90 6.9 ms, 8 answers2026-11-12: median 6.5 ms, p90 7.4 ms, 8 answers2026-11-13: median 6.5 ms, p90 6.9 ms, 8 answers2026-11-14: median 6.4 ms, p90 8.2 ms, 8 answers2026-11-15: median 6.6 ms, p90 6.8 ms, 8 answers2026-11-16: median 6.7 ms, p90 6.9 ms, 7 answers2026-11-102026-11-132026-11-16
6.7 ms median on 2026-11-16p90 6.9 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 13.107.236.208 (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 ns1.bdm.microsoftonline.com#

top 2 by domains
Nameserver setDomainsAvg response (A)NS lookup
ns1.bdm.microsoftonline.com · ns2.bdm.microsoftonline.com · ns3.bdm.microsoftonline.com · ns4.bdm.microsoftonline.com 2,323 45 ms 39 ms
ns.dandomain.dk · ns1.bdm.microsoftonline.com · ns2.bdm.microsoftonline.com · ns2.dandomain.dk · ns3.bdm.microsoftonline.com · ns4.bdm.microsoftonline.com 6 32 ms 43 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…