microsoft.cd - dns.ninja
microsoft.cd
cd
| DNSSEC | ⚠️ Not signed | ||||||
| NS | pch.nic.cd ⭐ | ||||||
| NS | gransy-anycast1.nic.cd | ||||||
| NS | gransy-anycast2.nic.cd | ||||||
| TXT | Generation Time: 1780579710 | ||||||
| SOA | pch.nic.cdnoc@nic.cd 2026-06-04 #12 | ||||||
Same first word
Similar names
DNS History
13 records (13 active, 0 former)
●NSns1-40.azure-dns.com2026-02-28 → 2026-06-04 · 2 obs
● 2026-06-04 14:02:18
●NSns2-40.azure-dns.net2026-02-28 → 2026-06-04 · 2 obs
● 2026-06-04 14:02:18
●NSns3-40.azure-dns.org2026-02-28 → 2026-06-04 · 2 obs
● 2026-06-04 14:02:18
●NSns4-40.azure-dns.info2026-02-28 → 2026-06-04 · 2 obs
● 2026-06-04 14:02:18
●A20.112.250.1332026-02-28 → 2026-06-04 · 2 obs
● 2026-06-04 14:02:18
●A20.231.239.2462026-02-28 → 2026-06-04 · 2 obs
● 2026-06-04 14:02:18
●A20.236.44.1622026-02-28 → 2026-06-04 · 2 obs
● 2026-06-04 14:02:18
●A20.70.246.202026-02-28 → 2026-06-04 · 2 obs
● 2026-06-04 14:02:18
●A20.76.201.1712026-02-28 → 2026-06-04 · 2 obs
● 2026-06-04 14:02:18
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| cd | pch.nic.cd, gransy-anycast1.nic.cd, gransy-anycast2.nic.cd | 3 records |
| microsoft.cd | ns1.msft.net, ns2.msft.net, ns3.msft.net, ns4.msft.net | - |
✅ Authoritative Response
Server:150.171.10.40
NS records: ns1.msft.net, ns2.msft.net, ns3.msft.net, ns4.msft.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for cd (unsigned zone)
⏱️ Timing
Total: 541ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 5 | 20.70.246.20, 20.76.201.171... |
| NS | 4 | ns1-40.azure-dns.com, ns2-40.azure-dns.net... |
| SOA | 1 | ns1-40.azure-dns.com azuredns-hostmaster |
📌 Glue Records Collected
Total: 3
In-bailiwick: 3 (pch.nic.cd, gransy-anycast1.nic.cd, gransy-anycast2.nic.cd)
Analysis
IP Addresses
microsoft.cd has 5 IP addresses: 20.70.246.20, 20.76.201.171, 20.112.250.133 and two more.
bingebuyers.com, msflightaddons.com, msdn.cn plus two other host names have IP numbers in common with microsoft.cd.
Name Servers
The DNS authority for microsoft.cd is spread across 8 name servers, among them ns1-40.azure-dns.com, ns4-40.azure-dns.info, ns2-40.azure-dns.net and five others.
microsoft.cd partially shares its NS delegation with several other domains, including microsoftnews.cd, microsoft.sa, teamflux.io and two others.
It is common to see these name servers paired with name servers ns2.msft.net, ns3.msft.net and ns4.msft.net plus three others.
Host names pointing to two IP addresses:
ns1-40.azure-dns.com resolves to two addresses: 150.171.10.40 and 2603:1061:0:10::28.
ns4-40.azure-dns.info resolves to two addresses: 13.107.206.40 and 2620:1ec:bda:10::28.
ns2-40.azure-dns.net resolves to two addresses: 150.171.16.40 and 2620:1ec:8ec:10::28.
ns3-40.azure-dns.org resolves to two addresses: 13.107.222.40 and 2a01:111:4000:10::28.
Host names with one IP number:
The hostname ns1.msft.net resolves to 150.171.10.40.
The hostname ns2.msft.net resolves to 150.171.16.40.
The hostname ns3.msft.net resolves to 13.107.222.40.
The hostname ns4.msft.net resolves to 13.107.206.40.
ns1-40.azure-dns.com along with ns1.msft.net each resolve to 150.171.10.40 IP addresses.
ns4-40.azure-dns.info along with ns4.msft.net each resolve to 13.107.206.40 IP addresses.
ns2-40.azure-dns.net along with ns2.msft.net each resolve to 150.171.16.40 IP addresses.
ns3-40.azure-dns.org along with ns3.msft.net each resolve to 13.107.222.40 IP addresses.