linkedintraining.de - dns.ninja

`linkedintraining.de`

DNSSEC	⚠️ Not signed
A	108.174.10.24^{🇺🇸 LINKEDIN-1108.174.10.0/24 Linkedin 2029 Stierlin Ct Mountain View, CA 94043 USA}
		PTR	`108-174-10-24.fwd.linkedin.com`
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.com`azuredns-hostmaster@microsoft.com serial=1

`de`

	DNSSEC	🔒 Signed (DS record present)
	NS	`f.nic.de` ⭐
	NS	`a.nic.de`
	NS	`l.de.net` ⚠️ Not in parent delegation
	NS	`n.de.net` ⚠️ Not in parent delegation
	NS	`s.de.net` ⚠️ Not in parent delegation
	NS	`z.nic.de`
	SOA	`f.nic.de`dns-operations@denic.de serial=1784892479

Same first word

linkedintraining.co.nz

linkedintraining.de

linkedintraining.com.au

linkedintraining.co.uk

DNS History

23 records (5 active, 18 former)

●NSns1-42.azure-dns.com2026-03-03 → 2026-07-24 · 3 obs

○ 2016-06-04 17:00:22
● 2026-03-03 05:38:10
● 2026-07-24 11:36:58

○NSns1.linkedin.com2015-06-10 → 2016-05-05 · 4 obs

● 2015-06-10 14:31:22
● 2016-05-05 11:03:48
○ 2016-06-04 17:00:22
○ 2026-07-24 11:36:58

○NSns1.p02.dynect.net2016-06-04 → 2016-06-04 · 4 obs

○ 2016-05-05 11:03:48
● 2016-06-04 17:00:22
○ 2026-03-03 05:38:10
○ 2026-07-24 11:36:58

○NSns1.p43.dynect.net2015-06-10 → 2016-05-05 · 4 obs

● 2015-06-10 14:31:22
● 2016-05-05 11:03:48
○ 2016-06-04 17:00:22
○ 2026-07-24 11:36:58

●NSns2-42.azure-dns.net2026-03-03 → 2026-07-24 · 3 obs

○ 2016-06-04 17:00:22
● 2026-03-03 05:38:10
● 2026-07-24 11:36:58

○NSns2.linkedin.com2015-06-10 → 2016-05-05 · 4 obs

● 2015-06-10 14:31:22
● 2016-05-05 11:03:48
○ 2016-06-04 17:00:22
○ 2026-07-24 11:36:58

○NSns2.p02.dynect.net2016-06-04 → 2016-06-04 · 4 obs

○ 2016-05-05 11:03:48
● 2016-06-04 17:00:22
○ 2026-03-03 05:38:10
○ 2026-07-24 11:36:58

○NSns2.p43.dynect.net2015-06-10 → 2016-05-05 · 4 obs

● 2015-06-10 14:31:22
● 2016-05-05 11:03:48
○ 2016-06-04 17:00:22
○ 2026-07-24 11:36:58

●NSns3-42.azure-dns.org2026-03-03 → 2026-07-24 · 3 obs

○ 2016-06-04 17:00:22
● 2026-03-03 05:38:10
● 2026-07-24 11:36:58

○NSns3.linkedin.com2015-06-10 → 2016-05-05 · 4 obs

● 2015-06-10 14:31:22
● 2016-05-05 11:03:48
○ 2016-06-04 17:00:22
○ 2026-07-24 11:36:58

○NSns3.p02.dynect.net2016-06-04 → 2016-06-04 · 4 obs

○ 2016-05-05 11:03:48
● 2016-06-04 17:00:22
○ 2026-03-03 05:38:10
○ 2026-07-24 11:36:58

○NSns3.p43.dynect.net2015-06-10 → 2016-05-05 · 4 obs

● 2015-06-10 14:31:22
● 2016-05-05 11:03:48
○ 2016-06-04 17:00:22
○ 2026-07-24 11:36:58

●NSns4-42.azure-dns.info2026-03-03 → 2026-07-24 · 3 obs

○ 2016-06-04 17:00:22
● 2026-03-03 05:38:10
● 2026-07-24 11:36:58

○NSns4.linkedin.com2015-06-10 → 2016-05-05 · 4 obs

● 2015-06-10 14:31:22
● 2016-05-05 11:03:48
○ 2016-06-04 17:00:22
○ 2026-07-24 11:36:58

○NSns4.p02.dynect.net2016-06-04 → 2016-06-04 · 4 obs

○ 2016-05-05 11:03:48
● 2016-06-04 17:00:22
○ 2026-03-03 05:38:10
○ 2026-07-24 11:36:58

○NSns4.p43.dynect.net2015-06-10 → 2016-05-05 · 4 obs

● 2015-06-10 14:31:22
● 2016-05-05 11:03:48
○ 2016-06-04 17:00:22
○ 2026-07-24 11:36:58

○NSns5.linkedin.com2015-06-10 → 2016-05-05 · 4 obs

● 2015-06-10 14:31:22
● 2016-05-05 11:03:48
○ 2016-06-04 17:00:22
○ 2026-07-24 11:36:58

○NSns6.linkedin.com2015-06-10 → 2016-05-05 · 4 obs

● 2015-06-10 14:31:22
● 2016-05-05 11:03:48
○ 2016-06-04 17:00:22
○ 2026-07-24 11:36:58

○MXmail-c.linkedin.com2015-06-10 → 2015-06-10 · 3 obs

● 2015-06-10 14:31:22
○ 2015-10-25 09:16:02
○ 2026-07-24 11:36:58

○MXmail.linkedin.com2015-06-10 → 2015-06-10 · 3 obs

● 2015-06-10 14:31:22
○ 2015-10-25 09:16:02
○ 2026-07-24 11:36:58

●A108.174.10.242026-03-03 → 2026-07-24 · 3 obs

○ 2015-10-25 09:16:02
● 2026-03-03 05:38:10
● 2026-07-24 11:36:58

○A108.174.2.1332015-06-10 → 2015-06-10 · 3 obs

● 2015-06-10 14:31:22
○ 2015-10-25 09:16:02
○ 2026-07-24 11:36:58

○A199.101.163.1332015-06-10 → 2015-06-10 · 3 obs

● 2015-06-10 14:31:22
○ 2015-10-25 09:16:02
○ 2026-07-24 11:36:58

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
de	a.nic.de, f.nic.de, z.nic.de	-
linkedintraining.de	ns1-42.azure-dns.com, ns3-42.azure-dns.org, ns2-42.azure-dns.net, ns4-42.azure-dns.info	-

✅ Authoritative Response

Server:150.171.10.42

NS records: ns1-42.azure-dns.com, ns3-42.azure-dns.org, ns2-42.azure-dns.net, ns4-42.azure-dns.info

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for linkedintraining.de (unsigned zone)

⏱️ Timing

Total: 1942ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`108.174.10.24`
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`

Analysis

IP Addresses

linkedintraining.de resolves to one IP address: 108.174.10.24.

linkedin.us, linkedininvestors.com, newsle.net and two other host names share IP numbers with linkedintraining.de.

Name Servers

The authoritative name servers for linkedintraining.de are ns1-42.azure-dns.com, ns4-42.azure-dns.info, ns2-42.azure-dns.net and ns3-42.azure-dns.org.

linkedintraining.de shares at least some of its name servers with other domains, including lyndapro.com, linkedinmail.us, 0.2.144.in-addr.arpa and two others.

These name servers are frequently seen alongside dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net and 7 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.