linkedin.mx - dns.ninja
linkedin.mx
| 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 | ||||||
mx
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | m.mx-ns.mx ⭐ | ||||||
| NS | c.mx-ns.mx | ||||||
| NS | e.mx-ns.mx | ||||||
| NS | i.mx-ns.mx | ||||||
| NS | o.mx-ns.mx | ||||||
| NS | x.mx-ns.mx | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | m.mx-ns.mxhostmaster@nic.mx serial=1784178965 | ||||||
Same first word
Similar names
DNS History
6 records (6 active, 0 former)
●NSns1-42.azure-dns.com2026-05-19 → 2026-07-16 · 2 obs
● 2026-07-16 05:44:22
●NSns2-42.azure-dns.net2026-05-19 → 2026-07-16 · 2 obs
● 2026-07-16 05:44:22
●NSns3-42.azure-dns.org2026-05-19 → 2026-07-16 · 2 obs
● 2026-07-16 05:44:22
●NSns4-42.azure-dns.info2026-05-19 → 2026-07-16 · 2 obs
● 2026-07-16 05:44:22
●A108.174.10.242026-05-19 → 2026-07-16 · 2 obs
● 2026-07-16 05:44:22
●A2620:109:c002::6cae:a182026-05-19 → 2026-07-16 · 2 obs
● 2026-07-16 05:44:22
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| mx | c.mx-ns.mx, i.mx-ns.mx, o.mx-ns.mx, e.mx-ns.mx... | - |
| linkedin.mx | ns1-42.azure-dns.com, ns2-42.azure-dns.net, ns3-42.azure-dns.org, ns4-42.azure-dns.info | - |
✅ Authoritative Response
Server:150.171.10.42
NS records: ns1-42.azure-dns.com, ns2-42.azure-dns.net, ns3-42.azure-dns.org, ns4-42.azure-dns.info
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for linkedin.mx (unsigned zone)
⏱️ Timing
Total: 1283ms | 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 |
Analysis
IP Addresses
linkedin.mx resolves to the IP addresses 108.174.10.24 and 2620:109:c002::6cae:a18
linkedin.ph, linkedin.hk, linkedin.ae plus two other host names have IP numbers in common with linkedin.mx.
Name Servers
Four name servers handle the delegation for linkedin.mx: ns1-42.azure-dns.com, ns4-42.azure-dns.info, ns2-42.azure-dns.net and ns3-42.azure-dns.org.
linkedin.mx shares at least some of its name servers with other domains, including linkedin.co, linkd.in, linkedinmobileapps-ei.com and two others.
These name servers are frequently seen alongside dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net and 7 other name servers.
Four host names, each with one IP address: ns1-42.azure-dns.com has 150.171.10.42, ns4-42.azure-dns.info has 13.107.206.42, ns2-42.azure-dns.net has 150.171.16.42 and ns3-42.azure-dns.org has 13.107.222.42.