linkedin.rs - robtex.com
linkedin.rs
| 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 | ||||||
rs
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.nic.rs ⭐ | ||||||
| NS | b.nic.rs | ||||||
| NS | c.nic.rs | ||||||
| NS | f.nic.rs | ||||||
| NS | h.nic.rs | ||||||
| NS | l.nic.rs | ||||||
| TXT | rs zone update: 2026-06-11 07:00:03 +02:00 (EPOCH 1781154003) | ||||||
| SOA | a.nic.rshostmaster@nic.rs 2026-06-11 #16 | ||||||
Same first word
Similar names
DNS History
6 records (6 active, 0 former)
●NSns1-42.azure-dns.com2026-05-19 → 2026-06-11 · 2 obs
● 2026-06-11 06:30:00
●NSns2-42.azure-dns.net2026-05-19 → 2026-06-11 · 2 obs
● 2026-06-11 06:30:00
●NSns3-42.azure-dns.org2026-05-19 → 2026-06-11 · 2 obs
● 2026-06-11 06:30:00
●NSns4-42.azure-dns.info2026-05-19 → 2026-06-11 · 2 obs
● 2026-06-11 06:30:00
●A108.174.10.242026-05-19 → 2026-06-11 · 2 obs
● 2026-06-11 06:30:00
●A2620:109:c002::6cae:a182026-05-19 → 2026-06-11 · 2 obs
● 2026-06-11 06:30:00
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| rs | a.nic.rs, b.nic.rs, c.nic.rs, f.nic.rs... | 12 records |
| linkedin.rs | 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.rs (unsigned zone)
⏱️ Timing
Total: 2825ms | 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 (a.nic.rs, b.nic.rs, c.nic.rs...)
Analysis
IP Addresses
linkedin.rs points to two IP numbers: 108.174.10.24 and 2620:109:c002::6cae:a18.
Two other host names, along with linkedin.ec, lynda.co and 108-174-10-24.fwd.linkedin.com, also share IP numbers with linkedin.rs.
Name Servers
linkedin.rs 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.rs has at least partial name server overlap with other domains, such as linkedin.info, linkdin.com, lynda.co and two others.
dns1.p09.nsone.net, dns2.p09.nsone.net and dns3.p09.nsone.net — plus 7 other name servers — are commonly paired with these name servers.
The hosts ns1-42.azure-dns.com, ns4-42.azure-dns.info, ns2-42.azure-dns.net and ns3-42.azure-dns.org all resolve to exactly one IP address each: 150.171.10.42, 13.107.206.42, 150.171.16.42 and 13.107.222.42 respectively.