linked-in.com - robtex.com
linked-in.com
| DNSSEC | ⚠️ Not signed | ||||||
| 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 | ||||||
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1778310776 | ||||||
Same first word
linked-in.de |
linked-in.com |
linked-in.co.uk |
linked-in.org |
linked-in.ru |
linked-in.eu |
linked-in.fr |
linked-in.net |
Similar names
in-linked.com |
dein-link.de |
kind-line.org |
dine-link.com |
linke-din.com |
in-kleind.com |
l-inkedin.com |
link-edin.com |
DNS History
13 records (4 active, 9 former)
●NSns1-42.azure-dns.com2026-02-21 → 2026-05-09 · 3 obs
● 2026-02-21 14:54:16
● 2026-05-09 07:39:28
○NSns1.lamedelegation.net2008-03-20 → 2008-03-20 · 3 obs
○ 2015-06-27 08:13:56
○ 2026-05-09 07:39:28
○NSns1.markmonitor.com2015-11-12 → 2016-04-28 · 5 obs
● 2015-11-12 21:06:38
● 2016-04-28 15:22:24
○ 2026-02-21 14:54:16
○ 2026-05-09 07:39:28
●NSns2-42.azure-dns.net2026-02-21 → 2026-05-09 · 3 obs
● 2026-02-21 14:54:16
● 2026-05-09 07:39:28
○NSns2.lamedelegation.net2008-03-20 → 2008-03-20 · 3 obs
○ 2015-06-27 08:13:56
○ 2026-05-09 07:39:28
○NSns2.markmonitor.com2015-11-12 → 2016-04-28 · 5 obs
● 2015-11-12 21:06:38
● 2016-04-28 15:22:24
○ 2026-02-21 14:54:16
○ 2026-05-09 07:39:28
●NSns3-42.azure-dns.org2026-02-21 → 2026-05-09 · 3 obs
● 2026-02-21 14:54:16
● 2026-05-09 07:39:28
○NSns3.markmonitor.com2015-11-12 → 2016-04-28 · 5 obs
● 2015-11-12 21:06:38
● 2016-04-28 15:22:24
○ 2026-02-21 14:54:16
○ 2026-05-09 07:39:28
●NSns4-42.azure-dns.info2026-02-21 → 2026-05-09 · 3 obs
● 2026-02-21 14:54:16
● 2026-05-09 07:39:28
○NSns4.markmonitor.com2015-11-12 → 2016-04-28 · 5 obs
● 2015-11-12 21:06:38
● 2016-04-28 15:22:24
○ 2026-02-21 14:54:16
○ 2026-05-09 07:39:28
○NSns5.markmonitor.com2015-11-12 → 2016-04-28 · 5 obs
● 2015-11-12 21:06:38
● 2016-04-28 15:22:24
○ 2026-02-21 14:54:16
○ 2026-05-09 07:39:28
○NSns6.markmonitor.com2015-11-12 → 2016-04-28 · 5 obs
● 2015-11-12 21:06:38
● 2016-04-28 15:22:24
○ 2026-02-21 14:54:16
○ 2026-05-09 07:39:28
○NSns7.markmonitor.com2015-11-12 → 2016-04-28 · 5 obs
● 2015-11-12 21:06:38
● 2016-04-28 15:22:24
○ 2026-02-21 14:54:16
○ 2026-05-09 07:39:28
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| linked-in.com | ns3-42.azure-dns.org, ns4-42.azure-dns.info, ns1-42.azure-dns.com, ns2-42.azure-dns.net | 1 record |
✅ Authoritative Response
Server:150.171.10.42
NS records: ns3-42.azure-dns.org, ns4-42.azure-dns.info, ns1-42.azure-dns.com, ns2-42.azure-dns.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for linked-in.com (unsigned zone)
⏱️ Timing
Total: 429ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| 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: 1
Out-of-bailiwick: 1 (ns1-42.azure-dns.com)
Analysis
Name Servers
linked-in.com delegates 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.
linked-in.com at least partially shares name servers with other domains, including linkedin.ae, linkedin.fr, linkedin.co.ke, linkedin.li and 0.174.108.in-addr.arpa.
These name servers are commonly used with 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 one IP number:
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.