`linkedin.how`

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.com`azuredns-hostmaster@microsoft.com serial=1

`how`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns-tld1.charlestonroadregistry.com` ⭐
	NS	`ns-tld2.charlestonroadregistry.com`
	NS	`ns-tld3.charlestonroadregistry.com`
	NS	`ns-tld4.charlestonroadregistry.com`
	NS	`ns-tld5.charlestonroadregistry.com`
	SOA	`ns-tld1.charlestonroadregistry.com`cloud-dns-hostmaster@google.com serial=1

Same first word

linkedin.cz

linkedin.black

linkedin.ma

linkedin.id

linkedin.ua

linkedin.com.es

linkedin.hu

linkedin.mu

linkedin.sk

linkedin.kim

linkedin.org.in

linkedin.vn

linkedin.my

linkedin.al

linkedin.equipment

linkedin.mn

linkedin.camera

linkedin.neustar

linkedin.co.hu

linkedin.name

linkedin.co.cr

linkedin.mk

linkedin.technology

linkedin.com.br

linkedin.berlin

linkedin.lt

linkedin.us

linkedin.soy

linkedin.jetzt

linkedin.blue

linkedin.careers

linkedin.estate

linkedin.dj

linkedin.com.qa

linkedin.uy

linkedin.com.hk

linkedin.lighting

linkedin.in

linkedin.ee

linkedin.pt

linkedin.jp

linkedin.se

linkedin.blog

linkedin.co.at

linkedin.af

linkedin.ru

linkedin.biz

linkedin.ai

linkedin.ug

linkedin.tk

linkedin.web.tr

linkedin.sx

linkedin.directory

linkedin.xin

linkedin.map.fastly.net

linkedin.com.tr

linkedin.de

linkedin.ovh

linkedin.eu.com

linkedin.bg

linkedin.com.ph

linkedin.com.mx

linkedin.place

linkedin.voyage

linkedin.es

linkedin.ba

linkedin.sg

linkedin.com.au

linkedin.co.th

linkedin.cn

linkedin.green

linkedin.enterprises

linkedin.by

linkedin.com.gt

linkedin.com.sg

linkedin.how

linkedin.net

linkedin.be

linkedin.si

linkedin.nyc

linkedin.im

linkedin.graphics

linkedin.co.il

linkedin.su

linkedin.at

linkedin.com.pe

linkedin.lv

linkedin.land

linkedin.lu

linkedin.pet

linkedin.it

linkedin.me

linkedin.tv

linkedin.co

linkedin.org

linkedin.com.ar

linkedin.shiksha

linkedin.no

linkedin.diamonds

linkedin.com.tw

linkedin.gallery

linkedin.co.uk

Similar names

DNS History

11 records (4 active, 7 former)

●NSns1-42.azure-dns.com2026-03-08 → 2026-05-09 · 3 obs

○ 2017-08-27 17:58:30
● 2026-03-08 10:45:48
● 2026-05-09 14:08:36

○NSns1.markmonitor.com2016-12-10 → 2017-08-27 · 4 obs

● 2016-12-10 09:09:34
● 2017-08-27 17:58:30
○ 2026-03-08 10:45:48
○ 2026-05-09 14:08:36

●NSns2-42.azure-dns.net2026-03-08 → 2026-05-09 · 3 obs

○ 2017-08-27 17:58:30
● 2026-03-08 10:45:48
● 2026-05-09 14:08:36

○NSns2.markmonitor.com2016-12-10 → 2017-08-27 · 4 obs

● 2016-12-10 09:09:34
● 2017-08-27 17:58:30
○ 2026-03-08 10:45:48
○ 2026-05-09 14:08:36

●NSns3-42.azure-dns.org2026-03-08 → 2026-05-09 · 3 obs

○ 2017-08-27 17:58:30
● 2026-03-08 10:45:48
● 2026-05-09 14:08:36

○NSns3.markmonitor.com2016-12-10 → 2017-08-27 · 4 obs

● 2016-12-10 09:09:34
● 2017-08-27 17:58:30
○ 2026-03-08 10:45:48
○ 2026-05-09 14:08:36

●NSns4-42.azure-dns.info2026-03-08 → 2026-05-09 · 3 obs

○ 2017-08-27 17:58:30
● 2026-03-08 10:45:48
● 2026-05-09 14:08:36

○NSns4.markmonitor.com2016-12-10 → 2017-08-27 · 4 obs

● 2016-12-10 09:09:34
● 2017-08-27 17:58:30
○ 2026-03-08 10:45:48
○ 2026-05-09 14:08:36

○NSns5.markmonitor.com2016-12-10 → 2017-08-27 · 4 obs

● 2016-12-10 09:09:34
● 2017-08-27 17:58:30
○ 2026-03-08 10:45:48
○ 2026-05-09 14:08:36

○NSns6.markmonitor.com2016-12-10 → 2017-08-27 · 4 obs

● 2016-12-10 09:09:34
● 2017-08-27 17:58:30
○ 2026-03-08 10:45:48
○ 2026-05-09 14:08:36

○NSns7.markmonitor.com2016-12-10 → 2017-08-27 · 4 obs

● 2016-12-10 09:09:34
● 2017-08-27 17:58:30
○ 2026-03-08 10:45:48
○ 2026-05-09 14:08:36

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
how	ns-tld3.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com...	10 records
linkedin.how	ns4-42.azure-dns.info, ns1-42.azure-dns.com, ns3-42.azure-dns.org, ns2-42.azure-dns.net	-

✅ Authoritative Response

Server:13.107.206.42

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for linkedin.how (unsigned zone)

⏱️ Timing

Total: 395ms | 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: 10

Out-of-bailiwick: 10 (ns-tld5.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com...)

Analysis

Name Servers

linkedin.how 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.how shares name servers with other domains at least partially, for instance linkendin.com, linkedin.tt, careerify.info, edubrite.us and linkedinbusinessawards.eu.

these name servers are commonly used with the name servers 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 a single IP:

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.

linkedin.how - robtex.com

linkedin.how

how

Same first word

Similar names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

Name Servers

`linkedin.how`

`how`