linkedin.tk - robtex.com

linkedin.tk

DNSSEC⚠️ Not signed
A2620:109:c002::6cae:a18πŸ‡ΊπŸ‡Έ LINKEDIN-12620:109:c002::/48 LinkedIn 2029 Stierlin Ct Mountain View, CA 94043
A108.174.10.24πŸ‡ΊπŸ‡Έ LINKEDIN-1108.174.10.0/24 Linkedin 2029 Stierlin Ct Mountain View, CA 94043 USA
NSns1-42.azure-dns.com ⭐
A150.171.10.42πŸ‡ΊπŸ‡Έ Microsoft150.171.0.0/16 MICROSOFT
PTRns1-42.azure-dns.com
NSns2-42.azure-dns.net
A150.171.16.42πŸ‡ΊπŸ‡Έ Microsoft150.171.0.0/16 MICROSOFT
PTRns2-42.azure-dns.net
NSns3-42.azure-dns.org
A13.107.222.42πŸ‡ΊπŸ‡Έ Microsoft13.104.0.0/14 MICROSOFT
PTRns3-42.azure-dns.org
NSns4-42.azure-dns.info
A13.107.206.42πŸ‡ΊπŸ‡Έ Microsoft13.104.0.0/14 MICROSOFT
PTRns4-42.azure-dns.info
TXTv=spf1 -all
SOAns1-42.azure-dns.comazuredns-hostmaster@microsoft.com serial=1

tk

DNSSEC⚠️ Not signed
A217.119.57.22
NSa.ns.tk ⭐
NSb.ns.tk
NSc.ns.tk
NSd.ns.tk
SOAa.ns.tkjoost\@zuurbier.dot.tk serial=1777823140

Same first word

Similar names

DNS History

26 records (6 active, 20 former)

20162017201820192020202120222023202420252026NSns1-42.azure-dns.comns2-42.azure-dns.netns3-42.azure-dns.orgns4-42.azure-dns.infons1.linkedin.comns1.markmonitor.comns1.p43.dynect.netns2.linkedin.comns2.markmonitor.comns2.p43.dynect.netns3.linkedin.comns3.markmonitor.comns3.p43.dynect.netns4.linkedin.comns4.markmonitor.comns4.p43.dynect.netns5.linkedin.comns5.markmonitor.comns6.linkedin.comns6.markmonitor.comns7.markmonitor.comMXA108.174.10.242620:109:c002::6cae:a18108.174.10.142620:109:c002::6cae:a0e
●NSns1-42.azure-dns.com2026-04-30 β†’ 2026-05-04 Β· 3 obs
β—‹ 2021-10-28 06:16:04
● 2026-04-30 14:47:24
● 2026-05-04 00:59:52
β—‹NSns1.linkedin.com2015-06-28 β†’ 2015-11-07 Β· 4 obs
● 2015-06-28 16:09:20
● 2015-11-07 02:48:46
β—‹ 2016-02-02 17:27:52
β—‹ 2026-05-04 00:59:52
β—‹NSns1.markmonitor.com2016-02-02 β†’ 2017-01-12 Β· 5 obs
β—‹ 2015-11-07 02:48:46
● 2016-02-02 17:27:52
● 2017-01-12 04:54:06
β—‹ 2018-05-30 08:19:14
β—‹ 2026-05-04 00:59:52
β—‹NSns1.p43.dynect.net2015-06-28 β†’ 2015-11-07 Β· 4 obs
● 2015-06-28 16:09:20
● 2015-11-07 02:48:46
β—‹ 2016-02-02 17:27:52
β—‹ 2026-05-04 00:59:52
●NSns2-42.azure-dns.net2026-04-30 β†’ 2026-05-04 Β· 3 obs
β—‹ 2021-10-28 06:16:04
● 2026-04-30 14:47:24
● 2026-05-04 00:59:52
β—‹NSns2.linkedin.com2015-06-28 β†’ 2015-11-07 Β· 4 obs
● 2015-06-28 16:09:20
● 2015-11-07 02:48:46
β—‹ 2016-02-02 17:27:52
β—‹ 2026-05-04 00:59:52
β—‹NSns2.markmonitor.com2016-02-02 β†’ 2021-10-28 Β· 5 obs
β—‹ 2015-11-07 02:48:46
● 2016-02-02 17:27:52
● 2021-10-28 06:16:04
β—‹ 2026-04-30 14:47:24
β—‹ 2026-05-04 00:59:52
β—‹NSns2.p43.dynect.net2015-06-28 β†’ 2015-11-07 Β· 4 obs
● 2015-06-28 16:09:20
● 2015-11-07 02:48:46
β—‹ 2016-02-02 17:27:52
β—‹ 2026-05-04 00:59:52
●NSns3-42.azure-dns.org2026-04-30 β†’ 2026-05-04 Β· 3 obs
β—‹ 2021-10-28 06:16:04
● 2026-04-30 14:47:24
● 2026-05-04 00:59:52
β—‹NSns3.linkedin.com2015-06-28 β†’ 2015-11-07 Β· 4 obs
● 2015-06-28 16:09:20
● 2015-11-07 02:48:46
β—‹ 2016-02-02 17:27:52
β—‹ 2026-05-04 00:59:52
β—‹NSns3.markmonitor.com2016-02-02 β†’ 2021-10-28 Β· 5 obs
β—‹ 2015-11-07 02:48:46
● 2016-02-02 17:27:52
● 2021-10-28 06:16:04
β—‹ 2026-04-30 14:47:24
β—‹ 2026-05-04 00:59:52
β—‹NSns3.p43.dynect.net2015-06-28 β†’ 2015-11-07 Β· 4 obs
● 2015-06-28 16:09:20
● 2015-11-07 02:48:46
β—‹ 2016-02-02 17:27:52
β—‹ 2026-05-04 00:59:52
●NSns4-42.azure-dns.info2026-04-30 β†’ 2026-05-04 Β· 3 obs
β—‹ 2021-10-28 06:16:04
● 2026-04-30 14:47:24
● 2026-05-04 00:59:52
β—‹NSns4.linkedin.com2015-06-28 β†’ 2015-11-07 Β· 4 obs
● 2015-06-28 16:09:20
● 2015-11-07 02:48:46
β—‹ 2016-02-02 17:27:52
β—‹ 2026-05-04 00:59:52
β—‹NSns4.markmonitor.com2016-02-02 β†’ 2021-10-28 Β· 5 obs
β—‹ 2015-11-07 02:48:46
● 2016-02-02 17:27:52
● 2021-10-28 06:16:04
β—‹ 2026-04-30 14:47:24
β—‹ 2026-05-04 00:59:52
β—‹NSns4.p43.dynect.net2015-06-28 β†’ 2015-11-07 Β· 4 obs
● 2015-06-28 16:09:20
● 2015-11-07 02:48:46
β—‹ 2016-02-02 17:27:52
β—‹ 2026-05-04 00:59:52
β—‹NSns5.linkedin.com2015-06-28 β†’ 2015-11-07 Β· 4 obs
● 2015-06-28 16:09:20
● 2015-11-07 02:48:46
β—‹ 2016-02-02 17:27:52
β—‹ 2026-05-04 00:59:52
β—‹NSns5.markmonitor.com2016-02-02 β†’ 2021-10-28 Β· 5 obs
β—‹ 2015-11-07 02:48:46
● 2016-02-02 17:27:52
● 2021-10-28 06:16:04
β—‹ 2026-04-30 14:47:24
β—‹ 2026-05-04 00:59:52
β—‹NSns6.linkedin.com2015-06-28 β†’ 2015-11-07 Β· 4 obs
● 2015-06-28 16:09:20
● 2015-11-07 02:48:46
β—‹ 2016-02-02 17:27:52
β—‹ 2026-05-04 00:59:52
β—‹NSns6.markmonitor.com2016-02-02 β†’ 2021-10-28 Β· 5 obs
β—‹ 2015-11-07 02:48:46
● 2016-02-02 17:27:52
● 2021-10-28 06:16:04
β—‹ 2026-04-30 14:47:24
β—‹ 2026-05-04 00:59:52
β—‹NSns7.markmonitor.com2016-02-02 β†’ 2017-01-12 Β· 5 obs
β—‹ 2015-11-07 02:48:46
● 2016-02-02 17:27:52
● 2017-01-12 04:54:06
β—‹ 2018-05-30 08:19:14
β—‹ 2026-05-04 00:59:52
β—‹MX(root)2018-05-30 β†’ 2021-10-28 Β· 4 obs
● 2018-05-30 08:19:14
● 2021-10-28 06:16:04
β—‹ 2026-04-30 14:47:24
β—‹ 2026-05-04 00:59:52
β—‹A108.174.10.142016-02-02 β†’ 2021-10-28 Β· 4 obs
● 2016-02-02 17:27:52
● 2021-10-28 06:16:04
β—‹ 2026-04-30 14:47:24
β—‹ 2026-05-04 00:59:52
●A108.174.10.242026-04-30 β†’ 2026-05-04 Β· 3 obs
β—‹ 2021-10-28 06:16:04
● 2026-04-30 14:47:24
● 2026-05-04 00:59:52
β—‹A2620:109:c002::6cae:a0e2016-02-02 β†’ 2021-10-28 Β· 4 obs
● 2016-02-02 17:27:52
● 2021-10-28 06:16:04
β—‹ 2026-04-30 14:47:24
β—‹ 2026-05-04 00:59:52
●A2620:109:c002::6cae:a182026-04-30 β†’ 2026-05-04 Β· 3 obs
β—‹ 2021-10-28 06:16:04
● 2026-04-30 14:47:24
● 2026-05-04 00:59:52

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
tka.ns.tk, b.ns.tk, c.ns.tk, d.ns.tk8 records
linkedin.tkns1-42.azure-dns.com, ns2-42.azure-dns.net, ns3-42.azure-dns.org, ns4-42.azure-dns.info-

βœ… Authoritative Response

Server:13.107.222.42

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

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for tk (unsigned zone)

⏱️ Timing

Total: 466ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A1108.174.10.24
AAAA12620:109:c002::6cae:a18
NS4ns1-42.azure-dns.com, ns2-42.azure-dns.net...
MX1. (pri: 0)
TXT1v=spf1 -all
SOA1ns1-42.azure-dns.com azuredns-hostmaster

πŸ“Œ Glue Records Collected

Total: 8

In-bailiwick: 8 (a.ns.tk, b.ns.tk, c.ns.tk...)

Analysis

IP Addresses

linkedin.tk resolves to two IP numbers: 2620:109:c002::6cae:a18 and 108.174.10.24.

other host names including linkedin.dk, linkedin.is, linkedin.nl, linkedin.com.pt and linkedin.fi share IP numbers with linkedin.tk.

Name Servers

linkedin.tk 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.tk at least partially shares name servers with other domains, for instance linkedintraining.de, bizo.graphics, linkedin.ma, thelinkedinstrategist.com and connecttoopportunity.com.

These name servers are commonly used with the following name servers: dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net, dns4.p09.nsone.net, 6.ns.linkedin.com, 1.ns.linkedin.com, 4.ns.linkedin.com, 2.ns.linkedin.com, 8.ns.linkedin.com and 7.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.