linkedin.com.qa - robtex.com
linkedin.com.qa
com.qa
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.registry.qa ⭐ | ||||||
| NS | a.registry.qa ⚠️ Not in parent delegation | ||||||
| NS | b.registry.qa ⚠️ Not in parent delegation | ||||||
| NS | c.registry.qa ⚠️ Not in parent delegation | ||||||
| NS | d.registry.qa ⚠️ Not in parent delegation | ||||||
| NS | e.registry.qa ⚠️ Not in parent delegation | ||||||
| NS | f.registry.qa ⚠️ Not in parent delegation | ||||||
| NS | g.registry.qa ⚠️ Not in parent delegation | ||||||
| NS | h.registry.qa ⚠️ Not in parent delegation | ||||||
| NS | i.registry.qa ⚠️ Not in parent delegation | ||||||
| SOA | ns1.registry.qasendmail@tech.at.domains.qa serial=2018089243 | ||||||
Same first word
Similar names
DNS History
8 records (8 active, 0 former)
●NSdns1.p09.nsone.net2026-04-30 → 2026-05-02 · 2 obs
● 2026-05-02 09:51:12
●NSdns2.p09.nsone.net2026-04-30 → 2026-05-02 · 2 obs
● 2026-05-02 09:51:12
●NSdns3.p09.nsone.net2026-04-30 → 2026-05-02 · 2 obs
● 2026-05-02 09:51:12
●NSdns4.p09.nsone.net2026-04-30 → 2026-05-02 · 2 obs
● 2026-05-02 09:51:12
●NSns1-42.azure-dns.com2026-04-30 → 2026-05-02 · 2 obs
● 2026-05-02 09:51:12
●NSns2-42.azure-dns.net2026-04-30 → 2026-05-02 · 2 obs
● 2026-05-02 09:51:12
●NSns3-42.azure-dns.org2026-04-30 → 2026-05-02 · 2 obs
● 2026-05-02 09:51:12
●NSns4-42.azure-dns.info2026-04-30 → 2026-05-02 · 2 obs
● 2026-05-02 09:51:12
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| qa | b.registry.qa, c.registry.qa, g.registry.qa, e.registry.qa... | 13 records |
| linkedin.com.qa | ns4-42.azure-dns.info, ns2-42.azure-dns.net, dns1.p09.nsone.net, ns1-42.azure-dns.com... | - |
✅ Authoritative Response
Server:150.171.10.42
NS records: ns4-42.azure-dns.info, ns2-42.azure-dns.net, dns1.p09.nsone.net, ns1-42.azure-dns.com, dns3.p09.nsone.net, dns4.p09.nsone.net, dns2.p09.nsone.net, ns3-42.azure-dns.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for qa (unsigned zone)
⏱️ Timing
Total: 519ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 8 | 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 hostmaster.linkedin |
📌 Glue Records Collected
Total: 13
In-bailiwick: 13 (i.registry.qa, h.registry.qa, g.registry.qa...)
Analysis
Name Servers
linkedin.com.qa is delegated to eight name servers: ns1-42.azure-dns.com, ns4-42.azure-dns.info, ns2-42.azure-dns.net, ns3-42.azure-dns.org, dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net and dns4.p09.nsone.net.
linkedin.com.qa at least partially shares its name servers with other domains, for instance schemabenchmarks.dev, artframepro.com, llamarecords.com, paramountwupa.com and scowt.com.
These name servers are commonly paired with dns1.p01.nsone.net, ns01.squarespacedns.com, ns02.squarespacedns.com, ns03.squarespacedns.com, ns04.squarespacedns.com, ns0004.secondary.cloudflare.com, ns0243.secondary.cloudflare.com, connect1.squarespacedns.com and connect2.squarespacedns.com.
Host names with two IP numbers:
dns1.p09.nsone.net points to 2620:4d:4000:6259:7:9:0:1 and 198.51.44.9
dns2.p09.nsone.net points to 2a00:edc0:6259:7:9::2 and 198.51.45.9
dns3.p09.nsone.net points to 2620:4d:4000:6259:7:9:0:3 and 198.51.44.73
dns4.p09.nsone.net points to 2a00:edc0:6259:7:9::4 and 198.51.45.73
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