laymor.com - dns.ninja

`laymor.com`

DNSSEC	⚠️ Not signed
A	167.71.190.72^{🇺🇸 DIGITALOCEAN167.71.176.0/20 DigitalOcean}
NS	`ns1-03.azure-dns.com` ⭐
		A	2603:1061:0:700::3^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-03.azure-dns.com`
		A	13.107.236.3^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-03.azure-dns.com`
NS	`ns2-03.azure-dns.net`
		A	2620:1ec:8ec:700::3^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-03.azure-dns.net`
		A	150.171.21.3^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-03.azure-dns.net`
NS	`ns3-03.azure-dns.org` ⚠️ Not in parent delegation
		A	2a01:111:4000:700::3^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-03.azure-dns.org`
		A	204.14.183.3^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-03.azure-dns.org`
NS	`ns4-03.azure-dns.info` ⚠️ Not in parent delegation
		A	2620:1ec:bda:700::3^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-03.azure-dns.info`
		A	208.84.5.3^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-03.azure-dns.info`
MX	`laymor-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c903::3^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-mw2pr02cu00503.inbound.protection.outlook.com`
		A	2a01:111:f403:c927::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bn8pr05cu00301.inbound.protection.outlook.com`
		A	2a01:111:f403:c92c::2^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-dm2pr04cu00102.inbound.protection.outlook.com`
		A	2a01:111:f403:c946::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-ch1pr04cu00101.inbound.protection.outlook.com`
		A	52.101.8.34^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-dm2pr04cu00102.inbound.protection.outlook.com`
		A	52.101.9.0^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bl2pr02cu00100.inbound.protection.outlook.com`
		A	52.101.9.20^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bl0pr02cu00604.inbound.protection.outlook.com`
		A	52.101.40.0^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-cy5pr03cu00300.inbound.protection.outlook.com`
TXT	`v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email -all`
SOA	`ns1-03.azure-dns.com`azuredns-hostmaster@microsoft.com 2022-03-28 #1

`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=1786485469

WOT: SAFE (68/100)

Same first word

laymor.com

Similar names

romaly.org

marylo.net

marylo.co.uk

malory.net

maroly.com

royalm.com

myoral.cn

alymor.com

mylora.hu

mylora.net

aromly.com

amorly.com

lamroy.com

loramy.com

yolmar.net

olarmy.com

romaly.com.br

roamly.it

lamory.fr

lyroma.com

morlay.com

moraly.com

romaly.com

laymro.com

lamory.com

mylora.com

malroy.com

armyol.com

ramoly.com

myalro.com

maylor.co.uk

roamly.ru

loryma.eu

mylora.ca

malory.fr

loymar.es

loramy.co.uk

royalm.dk

loryma.com

roamly.us

malory.ru

yolmar.com

mylora.com.au

malory.com

lymora.io

moryla.com

mroyal.ru

molyar.ru

roamly.com

lomray.com

myoral.com

roamly.ca

loryma.de

malory.cn

molray.com

lomyra.digital

yolmar.es

myorla.com

royalm.ca

myoral.xyz

DNS History

14 records (6 active, 8 former)

○NSdns1.name-services.com2015-08-20 → 2019-03-25 · 4 obs

● 2015-08-20 15:16:54
● 2019-03-25 03:36:12
○ 2026-02-15 00:06:16
○ 2026-08-11 22:03:20

○NSdns2.name-services.com2015-08-20 → 2019-03-25 · 4 obs

● 2015-08-20 15:16:54
● 2019-03-25 03:36:12
○ 2026-02-15 00:06:16
○ 2026-08-11 22:03:20

○NSdns3.name-services.com2015-08-20 → 2019-03-25 · 4 obs

● 2015-08-20 15:16:54
● 2019-03-25 03:36:12
○ 2026-02-15 00:06:16
○ 2026-08-11 22:03:20

○NSdns4.name-services.com2015-08-20 → 2019-03-25 · 4 obs

● 2015-08-20 15:16:54
● 2019-03-25 03:36:12
○ 2026-02-15 00:06:16
○ 2026-08-11 22:03:20

○NSdns5.name-services.com2015-08-20 → 2019-03-25 · 4 obs

● 2015-08-20 15:16:54
● 2019-03-25 03:36:12
○ 2026-02-15 00:06:16
○ 2026-08-11 22:03:20

●NSns1-03.azure-dns.com2026-02-15 → 2026-08-11 · 3 obs

○ 2019-03-25 03:36:12
● 2026-02-15 00:06:16
● 2026-08-11 22:03:20

●NSns2-03.azure-dns.net2026-02-15 → 2026-08-11 · 3 obs

○ 2019-03-25 03:36:12
● 2026-02-15 00:06:16
● 2026-08-11 22:03:20

●NSns3-03.azure-dns.org2026-02-15 → 2026-08-11 · 3 obs

○ 2019-03-25 03:36:12
● 2026-02-15 00:06:16
● 2026-08-11 22:03:20

●NSns4-03.azure-dns.info2026-02-15 → 2026-08-11 · 3 obs

○ 2019-03-25 03:36:12
● 2026-02-15 00:06:16
● 2026-08-11 22:03:20

●MXlaymor-com.mail.protection.outlook.com2026-02-15 → 2026-08-11 · 3 obs

○ 2019-03-25 03:36:12
● 2026-02-15 00:06:16
● 2026-08-11 22:03:20

○MXpop.laymor.com2015-08-20 → 2019-03-25 · 4 obs

● 2015-08-20 15:16:54
● 2019-03-25 03:36:12
○ 2026-02-15 00:06:16
○ 2026-08-11 22:03:20

●A167.71.190.722026-02-15 → 2026-08-11 · 3 obs

○ 2019-03-25 03:36:12
● 2026-02-15 00:06:16
● 2026-08-11 22:03:20

○A208.69.127.362015-08-20 → 2017-01-07 · 4 obs

● 2015-08-20 15:16:54
● 2017-01-07 09:48:02
○ 2019-03-25 03:36:12
○ 2026-08-11 22:03:20

○A74.124.213.1372019-03-25 → 2019-03-25 · 4 obs

○ 2017-01-07 09:48:02
● 2019-03-25 03:36:12
○ 2026-02-15 00:06:16
○ 2026-08-11 22:03:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	h.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, f.gtld-servers.net...	-
laymor.com	ns1-03.azure-dns.com, ns2-03.azure-dns.net	2 records

✅ Authoritative Response

Server:150.171.21.3

NS records: ns1-03.azure-dns.com, ns2-03.azure-dns.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for laymor.com (unsigned zone)

⏱️ Timing

Total: 374ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`167.71.190.72`
NS	4	`ns1-03.azure-dns.com, ns2-03.azure-dns.net...`
MX	1	`laymor-com.mail.protection.outlook.com (`
TXT	1	`v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}.`
SOA	1	`ns1-03.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1-03.azure-dns.com, ns1-03.azure-dns.com)

Analysis

IP Addresses

laymor.com resolves to one IP address: 167.71.190.72.

spartanmotors.com, goldshieldfiberglass.com, laddertower.com and two other host names share IP numbers with laymor.com.

Name Servers

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

laymor.com partially shares its NS delegation with several other domains, including 88.80.20.in-addr.arpa, ccmx.net, dispatchr.com and two others.

ns1-03.azure-dns.com, ns4-03.azure-dns.info, ns2-03.azure-dns.net and ns3-03.azure-dns.org each carry two IP addresses. ns1-03.azure-dns.com has 13.107.236.3 and 2603:1061:0:700::3; ns4-03.azure-dns.info has 208.84.5.3 and 2620:1ec:bda:700::3; ns2-03.azure-dns.net has 150.171.21.3 and 2620:1ec:8ec:700::3; ns3-03.azure-dns.org has 204.14.183.3 and 2a01:111:4000:700::3.

Mail Servers

Mail for laymor.com is handled by a single mail server, laymor-com.mail.protection.outlook.com.

laymor-com.mail.protection.outlook.com resolves to 8 IP addresses — 52.101.8.34, 52.101.9.0, 52.101.9.20 and 5 others.