linkedin.mu - robtex.com
linkedin.mu
| DNSSEC | ⚠️ Not signed | ||||||
| A | 2620:109:c002::6cae:a18🇺🇸 LINKEDIN-12620:109:c002::/48 LinkedIn 2029 Stierlin Ct Mountain View, CA 94043 | ||||||
| A | 108.174.10.24🇺🇸 LINKEDIN-1108.174.10.0/24 Linkedin 2029 Stierlin Ct Mountain View, CA 94043 USA | ||||||
| NS | ns1-42.azure-dns.com ⭐ | ||||||
| A | 150.171.10.42🇺🇸 Microsoft150.171.0.0/16 MICROSOFT | ||||||
| PTR | ns1-42.azure-dns.com | ||||||
| NS | ns2-42.azure-dns.net | ||||||
| A | 150.171.16.42🇺🇸 Microsoft150.171.0.0/16 MICROSOFT | ||||||
| PTR | ns2-42.azure-dns.net | ||||||
| NS | ns3-42.azure-dns.org | ||||||
| A | 13.107.222.42🇺🇸 Microsoft13.104.0.0/14 MICROSOFT | ||||||
| PTR | ns3-42.azure-dns.org | ||||||
| NS | ns4-42.azure-dns.info | ||||||
| A | 13.107.206.42🇺🇸 Microsoft13.104.0.0/14 MICROSOFT | ||||||
| PTR | ns4-42.azure-dns.info | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | ns1-42.azure-dns.comazuredns-hostmaster@microsoft.com serial=1 | ||||||
mu
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | v0n0.tld.mu ⭐ | ||||||
| NS | v0n1.tld.mu | ||||||
| NS | v0n2.tld.mu | ||||||
| NS | v0n3.tld.mu | ||||||
| NS | v2n0.tld.mu | ||||||
| NS | v2n1.tld.mu | ||||||
| SOA | v0n0.tld.muhostmaster@donuts.email serial=1778305412 | ||||||
Same first word
Similar names
DNS History
6 records (6 active, 0 former)
●NSns1-42.azure-dns.com2026-05-07 → 2026-05-09 · 2 obs
● 2026-05-09 06:07:24
●NSns2-42.azure-dns.net2026-05-07 → 2026-05-09 · 2 obs
● 2026-05-09 06:07:24
●NSns3-42.azure-dns.org2026-05-07 → 2026-05-09 · 2 obs
● 2026-05-09 06:07:24
●NSns4-42.azure-dns.info2026-05-07 → 2026-05-09 · 2 obs
● 2026-05-09 06:07:24
●A108.174.10.242026-05-07 → 2026-05-09 · 2 obs
● 2026-05-09 06:07:24
●A2620:109:c002::6cae:a182026-05-07 → 2026-05-09 · 2 obs
● 2026-05-09 06:07:24
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| mu | v2n0.tld.mu, v0n0.tld.mu, v0n2.tld.mu, v0n1.tld.mu... | 12 records |
| linkedin.mu | ns3-42.azure-dns.org, ns2-42.azure-dns.net, ns1-42.azure-dns.com, ns4-42.azure-dns.info | - |
✅ Authoritative Response
Server:13.107.206.42
NS records: ns3-42.azure-dns.org, ns2-42.azure-dns.net, ns1-42.azure-dns.com, ns4-42.azure-dns.info
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for linkedin.mu (unsigned zone)
⏱️ Timing
Total: 1334ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 108.174.10.24 |
| AAAA | 1 | 2620:109:c002::6cae:a18 |
| NS | 4 | ns1-42.azure-dns.com, ns2-42.azure-dns.net... |
| MX | 1 | . (pri: 0) |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ns1-42.azure-dns.com azuredns-hostmaster |
📌 Glue Records Collected
Total: 12
In-bailiwick: 12 (v2n1.tld.mu, v2n0.tld.mu, v0n3.tld.mu...)
Analysis
IP Addresses
linkedin.mu points to two IP numbers: 2620:109:c002::6cae:a18 and 108.174.10.24.
Other host names, for instance mumbo.com, linked.in, linkedin.com.mx, rapportive.com and linkedin-ela4.com share IP numbers with linkedin.mu.
Name Servers
linkedin.mu is delegated to four name servers: ns1-42.azure-dns.com, ns4-42.azure-dns.info, ns2-42.azure-dns.net and ns3-42.azure-dns.org.
linkedin.mu at least partially shares name servers with other domains, for instance linkedin.af, linkedinforgood.org, linkedin.ru, newsle.co and linkedin.biz.
These name servers are commonly used together with the name servers dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net, dns4.p09.nsone.net, 1.ns.linkedin.com, 2.ns.linkedin.com, 3.ns.linkedin.com, 4.ns.linkedin.com, 5.ns.linkedin.com and 6.ns.linkedin.com.
Host names with a single IP address
ns1-42.azure-dns.com points to 150.171.10.42
ns4-42.azure-dns.info points to 13.107.206.42
ns2-42.azure-dns.net points to 150.171.16.42
ns3-42.azure-dns.org points to 13.107.222.42