linkedin-ela4.com - robtex.com
linkedin-ela4.com
| 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 | ||||||
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=1778071551 | ||||||
Same first word
linkedin-ela4.com |
DNS History
26 records (6 active, 20 former)
○NSdns1.p09.nsone.net2016-10-30 → 2016-11-02 · 5 obs
○ 2016-09-05 12:59:42
● 2016-10-30 08:25:10
● 2016-11-02 15:24:08
○ 2026-03-03 05:38:12
○ 2026-05-06 12:59:54
● 2016-10-30 08:25:10
● 2016-11-02 15:24:08
○ 2026-03-03 05:38:12
○ 2026-05-06 12:59:54
○NSdns2.p09.nsone.net2016-10-30 → 2016-10-30 · 4 obs
○ 2016-09-05 12:59:42
● 2016-10-30 08:25:10
○ 2016-11-02 15:24:08
○ 2026-05-06 12:59:54
● 2016-10-30 08:25:10
○ 2016-11-02 15:24:08
○ 2026-05-06 12:59:54
○NSdns3.p09.nsone.net2016-10-30 → 2016-10-30 · 4 obs
○ 2016-09-05 12:59:42
● 2016-10-30 08:25:10
○ 2016-11-02 15:24:08
○ 2026-05-06 12:59:54
● 2016-10-30 08:25:10
○ 2016-11-02 15:24:08
○ 2026-05-06 12:59:54
○NSdns4.p09.nsone.net2016-10-30 → 2016-10-30 · 4 obs
○ 2016-09-05 12:59:42
● 2016-10-30 08:25:10
○ 2016-11-02 15:24:08
○ 2026-05-06 12:59:54
● 2016-10-30 08:25:10
○ 2016-11-02 15:24:08
○ 2026-05-06 12:59:54
●NSns1-42.azure-dns.com2026-03-03 → 2026-05-06 · 3 obs
○ 2016-11-02 15:24:08
● 2026-03-03 05:38:12
● 2026-05-06 12:59:54
● 2026-03-03 05:38:12
● 2026-05-06 12:59:54
○NSns1.linkedin.com2015-07-05 → 2016-09-05 · 6 obs
● 2015-07-05 18:42:48
● 2016-04-19 18:30:42
○ 2016-05-17 01:23:56
● 2016-09-05 12:59:42
○ 2016-10-30 08:25:10
○ 2026-05-06 12:59:54
● 2016-04-19 18:30:42
○ 2016-05-17 01:23:56
● 2016-09-05 12:59:42
○ 2016-10-30 08:25:10
○ 2026-05-06 12:59:54
○NSns1.p02.dynect.net2016-05-17 → 2016-11-02 · 7 obs
○ 2016-04-19 18:30:42
● 2016-05-17 01:23:56
○ 2016-09-05 12:59:42
● 2016-10-30 08:25:10
● 2016-11-02 15:24:08
○ 2026-03-03 05:38:12
○ 2026-05-06 12:59:54
● 2016-05-17 01:23:56
○ 2016-09-05 12:59:42
● 2016-10-30 08:25:10
● 2016-11-02 15:24:08
○ 2026-03-03 05:38:12
○ 2026-05-06 12:59:54
○NSns1.p43.dynect.net2015-07-05 → 2016-09-05 · 4 obs
● 2015-07-05 18:42:48
● 2016-09-05 12:59:42
○ 2016-10-30 08:25:10
○ 2026-05-06 12:59:54
● 2016-09-05 12:59:42
○ 2016-10-30 08:25:10
○ 2026-05-06 12:59:54
●NSns2-42.azure-dns.net2026-03-03 → 2026-05-06 · 3 obs
○ 2016-11-02 15:24:08
● 2026-03-03 05:38:12
● 2026-05-06 12:59:54
● 2026-03-03 05:38:12
● 2026-05-06 12:59:54
○NSns2.linkedin.com2015-07-05 → 2016-09-05 · 4 obs
● 2015-07-05 18:42:48
● 2016-09-05 12:59:42
○ 2016-10-30 08:25:10
○ 2026-05-06 12:59:54
● 2016-09-05 12:59:42
○ 2016-10-30 08:25:10
○ 2026-05-06 12:59:54
○NSns2.p02.dynect.net2016-10-30 → 2016-11-02 · 5 obs
○ 2016-09-05 12:59:42
● 2016-10-30 08:25:10
● 2016-11-02 15:24:08
○ 2026-03-03 05:38:12
○ 2026-05-06 12:59:54
● 2016-10-30 08:25:10
● 2016-11-02 15:24:08
○ 2026-03-03 05:38:12
○ 2026-05-06 12:59:54
○NSns2.p43.dynect.net2015-07-05 → 2016-09-05 · 4 obs
● 2015-07-05 18:42:48
● 2016-09-05 12:59:42
○ 2016-10-30 08:25:10
○ 2026-05-06 12:59:54
● 2016-09-05 12:59:42
○ 2016-10-30 08:25:10
○ 2026-05-06 12:59:54
●NSns3-42.azure-dns.org2026-03-03 → 2026-05-06 · 3 obs
○ 2016-11-02 15:24:08
● 2026-03-03 05:38:12
● 2026-05-06 12:59:54
● 2026-03-03 05:38:12
● 2026-05-06 12:59:54
○NSns3.linkedin.com2015-07-05 → 2016-09-05 · 4 obs
● 2015-07-05 18:42:48
● 2016-09-05 12:59:42
○ 2016-10-30 08:25:10
○ 2026-05-06 12:59:54
● 2016-09-05 12:59:42
○ 2016-10-30 08:25:10
○ 2026-05-06 12:59:54
○NSns3.p02.dynect.net2016-10-30 → 2016-11-02 · 5 obs
○ 2016-09-05 12:59:42
● 2016-10-30 08:25:10
● 2016-11-02 15:24:08
○ 2026-03-03 05:38:12
○ 2026-05-06 12:59:54
● 2016-10-30 08:25:10
● 2016-11-02 15:24:08
○ 2026-03-03 05:38:12
○ 2026-05-06 12:59:54
○NSns3.p43.dynect.net2015-07-05 → 2016-09-05 · 4 obs
● 2015-07-05 18:42:48
● 2016-09-05 12:59:42
○ 2016-10-30 08:25:10
○ 2026-05-06 12:59:54
● 2016-09-05 12:59:42
○ 2016-10-30 08:25:10
○ 2026-05-06 12:59:54
●NSns4-42.azure-dns.info2026-03-03 → 2026-05-06 · 3 obs
○ 2016-11-02 15:24:08
● 2026-03-03 05:38:12
● 2026-05-06 12:59:54
● 2026-03-03 05:38:12
● 2026-05-06 12:59:54
○NSns4.linkedin.com2015-07-05 → 2016-09-05 · 4 obs
● 2015-07-05 18:42:48
● 2016-09-05 12:59:42
○ 2016-10-30 08:25:10
○ 2026-05-06 12:59:54
● 2016-09-05 12:59:42
○ 2016-10-30 08:25:10
○ 2026-05-06 12:59:54
○NSns4.p02.dynect.net2016-10-30 → 2016-11-02 · 5 obs
○ 2016-09-05 12:59:42
● 2016-10-30 08:25:10
● 2016-11-02 15:24:08
○ 2026-03-03 05:38:12
○ 2026-05-06 12:59:54
● 2016-10-30 08:25:10
● 2016-11-02 15:24:08
○ 2026-03-03 05:38:12
○ 2026-05-06 12:59:54
○NSns4.p43.dynect.net2015-07-05 → 2016-09-05 · 4 obs
● 2015-07-05 18:42:48
● 2016-09-05 12:59:42
○ 2016-10-30 08:25:10
○ 2026-05-06 12:59:54
● 2016-09-05 12:59:42
○ 2016-10-30 08:25:10
○ 2026-05-06 12:59:54
○NSns5.linkedin.com2015-07-05 → 2016-09-05 · 4 obs
● 2015-07-05 18:42:48
● 2016-09-05 12:59:42
○ 2016-10-30 08:25:10
○ 2026-05-06 12:59:54
● 2016-09-05 12:59:42
○ 2016-10-30 08:25:10
○ 2026-05-06 12:59:54
○NSns6.linkedin.com2015-07-05 → 2016-09-05 · 4 obs
● 2015-07-05 18:42:48
● 2016-09-05 12:59:42
○ 2016-10-30 08:25:10
○ 2026-05-06 12:59:54
● 2016-09-05 12:59:42
○ 2016-10-30 08:25:10
○ 2026-05-06 12:59:54
○MX(root)2015-07-05 → 2016-04-19 · 4 obs
● 2015-07-05 18:42:48
● 2016-04-19 18:30:42
○ 2016-05-17 01:23:56
○ 2026-05-06 12:59:54
● 2016-04-19 18:30:42
○ 2016-05-17 01:23:56
○ 2026-05-06 12:59:54
●A108.174.10.242026-03-03 → 2026-05-06 · 3 obs
○ 2016-11-02 15:24:08
● 2026-03-03 05:38:12
● 2026-05-06 12:59:54
● 2026-03-03 05:38:12
● 2026-05-06 12:59:54
○A216.52.242.802015-07-05 → 2016-11-02 · 4 obs
● 2015-07-05 18:42:48
● 2016-11-02 15:24:08
○ 2026-03-03 05:38:12
○ 2026-05-06 12:59:54
● 2016-11-02 15:24:08
○ 2026-03-03 05:38:12
○ 2026-05-06 12:59:54
●A2620:109:c002::6cae:a182026-03-03 → 2026-05-06 · 3 obs
○ 2016-11-02 15:24:08
● 2026-03-03 05:38:12
● 2026-05-06 12:59:54
● 2026-03-03 05:38:12
● 2026-05-06 12:59:54
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| linkedin-ela4.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.16.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 linkedin-ela4.com (unsigned zone)
⏱️ Timing
Total: 451ms | 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: 1
Out-of-bailiwick: 1 (ns1-42.azure-dns.com)
Analysis
IP Addresses
linkedin-ela4.com points to two IP numbers: 2620:109:c002::6cae:a18 and 108.174.10.24.
Other host names such as linkedin.ae, linkedin.fr, linkedin.li, eathacknosleep.com and linnkedin.com share IPs with linkedin-ela4.com.
Name Servers
linkedin-ela4.com 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-ela4.com at least partially shares name servers with other domains, for instance linkedin.fr, linkedin.co.ke, linkedin.li, 0.174.108.in-addr.arpa and 163.101.199.in-addr.arpa.
These name servers are commonly used alongside 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.