linkedin.space - robtex.com
linkedin.space
| 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 | ||||||
space
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns01.trs-dns.com ⭐ | ||||||
| NS | ns.trs-dns.com | ||||||
| NS | ns01.trs-dns.net | ||||||
| NS | ns10.trs-dns.info | ||||||
| NS | ns10.trs-dns.org | ||||||
| SOA | ns.trs-dns.comtrs-ops@tucows.com serial=1781018330 | ||||||
Same first word
Similar names
DNS History
4 records (4 active, 0 former)
●NSns1-42.azure-dns.com2026-05-19 → 2026-06-09 · 2 obs
● 2026-06-09 16:00:10
●NSns2-42.azure-dns.net2026-05-19 → 2026-06-09 · 2 obs
● 2026-06-09 16:00:10
●NSns3-42.azure-dns.org2026-05-19 → 2026-06-09 · 2 obs
● 2026-06-09 16:00:10
●NSns4-42.azure-dns.info2026-05-19 → 2026-06-09 · 2 obs
● 2026-06-09 16:00:10
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| space | ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info | 8 records |
| linkedin.space | ns3-42.azure-dns.org, ns4-42.azure-dns.info, ns1-42.azure-dns.com, ns2-42.azure-dns.net | - |
✅ Authoritative Response
Server:13.107.222.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.space (unsigned zone)
⏱️ Timing
Total: 292ms | 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: 8
Out-of-bailiwick: 8 (ns01.trs-dns.com, ns01.trs-dns.com, ns01.trs-dns.net...)
Analysis
Name Servers
linkedin.space delegates DNS authority to 4 name servers — ns1-42.azure-dns.com, ns4-42.azure-dns.info, ns2-42.azure-dns.net and ns3-42.azure-dns.org.
The name servers of linkedin.space overlap at least partially with those of other domains — among them 163.101.199.in-addr.arpa, eathacknosleep.com, linked-in.fr and two more.
It is common to see these name servers paired with dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net and seven other name servers.
Each of the four hosts ns1-42.azure-dns.com, ns4-42.azure-dns.info, ns2-42.azure-dns.net and ns3-42.azure-dns.org points to 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 and ns3-42.azure-dns.org points to 13.107.222.42.