`mn-linkedin.com`

DNSSEC	⚠️ Not signed
A	91.195.240.123^{🇩🇪 SEDO91.195.240.0/23 -NET-PI}
NS	`ns1.dnsowl.com` ⭐
		A	2400:cb00:2049:1::a29f:1a88^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	2400:cb00:2049:1::a29f:1bad^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.26.136^{Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	162.159.27.173^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns2.dnsowl.com`
		A	2400:cb00:2049:1::a29f:1a31^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	2400:cb00:2049:1::a29f:1b82^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.26.49^{Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	162.159.27.130^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns3.dnsowl.com`
		A	2400:cb00:2049:1::a29f:1aea^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	2400:cb00:2049:1::a29f:1b62^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.26.234^{Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	162.159.27.98^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c21::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`pe-in-f26.1e100.net`
		A	172.253.62.26^{🇺🇸 Google172.253.62.0/24}
			PTR	`bc-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:4013:c1e::1a^{🇳🇱 Google2a00:1450:4013::/48}
			PTR	`yugrqzs-in-f26.1e100.net`
		A	192.178.213.27^{🇺🇸 Google192.178.213.0/24}
			PTR	`yugrqzs-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4025:c01::1a^{🇵🇱 Google2a00:1450:4025::/48}
			PTR	`rd-in-f26.1e100.net`
		A	142.250.147.26^{🇺🇸 Google142.250.147.0/24}
			PTR	`rd-in-f26.1e100.net`
TXT	`google-site-verification=fAZOqoGip4l_R8qYLUue84G5px9cwbiKa7aGA5ZTOxY`
TXT	`v=spf1 include:_spf.mail.google.com ~all`
SOA	`ns1.dnsowl.com`hostmaster@dnsowl.com serial=1769450331

`com`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.gtld-servers.net` ⭐
	NS	`b.gtld-servers.net`
	NS	`c.gtld-servers.net`
	NS	`d.gtld-servers.net`
	NS	`e.gtld-servers.net`
	NS	`f.gtld-servers.net`
	NS	`g.gtld-servers.net`
	NS	`h.gtld-servers.net`
	NS	`i.gtld-servers.net`
	NS	`j.gtld-servers.net`
	NS	`k.gtld-servers.net`
	NS	`l.gtld-servers.net`
	NS	`m.gtld-servers.net`
	SOA	`a.gtld-servers.net`nstld@verisign-grs.com serial=1774673307

Same first word

mn-linkedin.com

DNS History

9 records (9 active, 0 former)

●NSns1.dnsowl.com2026-02-26 → 2026-03-28 · 2 obs

● 2026-02-26 15:33:54
● 2026-03-28 05:03:24

●NSns2.dnsowl.com2026-02-26 → 2026-03-28 · 2 obs

● 2026-02-26 15:33:54
● 2026-03-28 05:03:24

●NSns3.dnsowl.com2026-02-26 → 2026-03-28 · 2 obs

● 2026-02-26 15:33:54
● 2026-03-28 05:03:24

●MXalt1.aspmx.l.google.com2026-02-26 → 2026-03-28 · 2 obs

● 2026-02-26 15:33:54
● 2026-03-28 05:03:24

●MXalt2.aspmx.l.google.com2026-02-26 → 2026-03-28 · 2 obs

● 2026-02-26 15:33:54
● 2026-03-28 05:03:24

●MXalt3.aspmx.l.google.com2026-02-26 → 2026-03-28 · 2 obs

● 2026-02-26 15:33:54
● 2026-03-28 05:03:24

●MXalt4.aspmx.l.google.com2026-02-26 → 2026-03-28 · 2 obs

● 2026-02-26 15:33:54
● 2026-03-28 05:03:24

●MXaspmx.l.google.com2026-02-26 → 2026-03-28 · 2 obs

● 2026-02-26 15:33:54
● 2026-03-28 05:03:24

●A91.195.240.1232026-02-26 → 2026-03-28 · 2 obs

● 2026-02-26 15:33:54
● 2026-03-28 05:03:24

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	d.gtld-servers.net, l.gtld-servers.net, h.gtld-servers.net, a.gtld-servers.net...	-
mn-linkedin.com	ns1.dnsowl.com, ns2.dnsowl.com, ns3.dnsowl.com	12 records

✅ Authoritative Response

Server:162.159.26.136

NS records: ns1.dnsowl.com, ns2.dnsowl.com, ns3.dnsowl.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for mn-linkedin.com (unsigned zone)

⏱️ Timing

Total: 377ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`91.195.240.123`
NS	3	`ns1.dnsowl.com, ns2.dnsowl.com...`
MX	5	`ALT1.ASPMX.L.GOOGLE.com (pri: 5), ALT2.ASPMX.L.GOOGLE.com (pri: 5)...`
TXT	2	`google-site-verification=fAZOqoGip4l_R8q, v=spf1 include:_spf.mail.google.com ~all`
SOA	1	`ns1.dnsowl.com hostmaster.dnsowl.com`

📌 Glue Records Collected

Total: 12

Out-of-bailiwick: 12 (ns1.dnsowl.com, ns1.dnsowl.com, ns1.dnsowl.com...)

Analysis

IP Addresses

mn-linkedin.com points to an IP address: 91.195.240.123.

other host names include www.ltxs520.cc, appforapp.com, kahog.com, lygear.com and www.4c2d00416124.xyz; they share IP numbers with mn-linkedin.com.

Name Servers

mn-linkedin.com is delegated to three name servers ns1.dnsowl.com, ns2.dnsowl.com and ns3.dnsowl.com.

mn-linkedin.com at least partially shares name servers with other domains, for instance accenttech.com, purematue.com, sfast.net, waterfromword.com and bolise.rest.