`lasignsbanners.com`

DNSSEC	⚠️ Not signed
A	191.101.30.221^{🇺🇸 TIER-NET191.101.30.0/24}
		PTR	`mars.gendns.com`
NS	`ns1.bdm.microsoftonline.com` ⭐
		A	2603:1061:0:700::d0^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-208.azure-dns.com`
		A	13.107.236.208^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-208.azure-dns.com`
NS	`ns2.bdm.microsoftonline.com`
		A	2620:1ec:8ec:700::d0^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-208.azure-dns.net`
		A	150.171.21.208^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-208.azure-dns.net`
NS	`ns3.bdm.microsoftonline.com`
		A	2a01:111:4000:700::d0^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-208.azure-dns.org`
		A	204.14.183.208^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-208.azure-dns.org`
NS	`ns4.bdm.microsoftonline.com`
		A	2620:1ec:bda:700::d0^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-208.azure-dns.info`
		A	208.84.5.208^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-208.azure-dns.info`
MX	`lasignsbanners-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c92c::2^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-dm2pr04cu00102.inbound.protection.outlook.com`
		A	2a01:111:f403:c931::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sn1pr02cu00100.inbound.protection.outlook.com`
		A	2a01:111:f403:f902::2^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-mn2pr02cu00202.inbound.protection.outlook.com`
		A	2a01:111:f403:f903::^{🇺🇸 Microsoft2a01:111:f000::/36}
		A	52.101.8.34^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-dm2pr04cu00102.inbound.protection.outlook.com`
		A	52.101.11.15^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sa9pr02cu00207.inbound.protection.outlook.com`
		A	52.101.11.19^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sa9pr04cu00203.inbound.protection.outlook.com`
		A	52.101.41.6^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sj0pr03cu01406.inbound.protection.outlook.com`
TXT	`v=spf1 include:spf.protection.outlook.com include:spf.sendinblue.com include:...`
TXT	`mscid=i0BqSO94pX605FEZXBojUE8Y4M5cnwaUC5tWq8D6Ti+zWGUwoG+m1a91to0QvVtH5dN1VCO...`
TXT	`MS=ms16493251`
TXT	`Sendinblue-code:a929ab6fa2e02d99b3951bfed9cd30b2`
SOA	`ns1.bdm.microsoftonline.com`azuredns-hostmaster@microsoft.com serial=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=1774425722

Subdomains

mail.lasignsbanners.com

www.lasignsbanners.com

Same first word

lasignsbanners.com

DNS History

9 records (6 active, 3 former)

●NSns1.bdm.microsoftonline.com2026-03-25 → 2026-03-25 · 2 obs

○ 2017-07-09 19:25:46
● 2026-03-25 08:16:28

○NSns1.pdrmm.com2015-07-15 → 2017-07-09 · 3 obs

● 2015-07-15 03:35:14
● 2017-07-09 19:25:46
○ 2026-03-25 08:16:28

●NSns2.bdm.microsoftonline.com2026-03-25 → 2026-03-25 · 2 obs

○ 2017-07-09 19:25:46
● 2026-03-25 08:16:28

○NSns2.pdrmm.com2015-07-15 → 2017-07-09 · 3 obs

● 2015-07-15 03:35:14
● 2017-07-09 19:25:46
○ 2026-03-25 08:16:28

●NSns3.bdm.microsoftonline.com2026-03-25 → 2026-03-25 · 2 obs

○ 2017-07-09 19:25:46
● 2026-03-25 08:16:28

●NSns4.bdm.microsoftonline.com2026-03-25 → 2026-03-25 · 2 obs

○ 2017-07-09 19:25:46
● 2026-03-25 08:16:28

●MXlasignsbanners-com.mail.protection.outlook.com2015-07-15 → 2026-03-25 · 2 obs

● 2015-07-15 03:35:14
● 2026-03-25 08:16:28

●A191.101.30.2212026-03-25 → 2026-03-25 · 2 obs

○ 2017-07-09 19:25:46
● 2026-03-25 08:16:28

○A50.87.212.2042015-07-15 → 2017-07-09 · 3 obs

● 2015-07-15 03:35:14
● 2017-07-09 19:25:46
○ 2026-03-25 08:16:28

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
lasignsbanners.com	ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com, ns4.bdm.microsoftonline.com	8 records

✅ Authoritative Response

Server:204.14.183.208

NS records: ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com, ns4.bdm.microsoftonline.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for lasignsbanners.com (unsigned zone)

⏱️ Timing

Total: 139ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`191.101.30.221`
NS	4	`ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com...`
MX	1	`lasignsbanners-com.mail.protection.outlo`
TXT	4	`v=spf1 include:spf.protection.outlook.co, mscid=i0BqSO94pX605FEZXBojUE8Y4M5cnwaUC5...`
SOA	1	`ns1.bdm.microsoftonline.com azuredns-hos`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns1.bdm.microsoftonline.com, ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com...)

Analysis

Hierarchy

lasignsbanners.com is a parent of mail.lasignsbanners.com and www.lasignsbanners.com.

IP Addresses

lasignsbanners.com resolves to one IP number: 191.101.30.221.

Name Servers

lasignsbanners.com is delegated to four name servers: ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com and ns4.bdm.microsoftonline.com.

lasignsbanners.com at least partially shares name servers with other domains, for instance globalccc.com, agag.cz, visionjoinery.com.au, sysmaster.dk and propayhr.com.

Host names with two IP numbers:

ns1.bdm.microsoftonline.com points to 2603:1061:0:700::d0 and 13.107.236.208; ns2.bdm.microsoftonline.com points to 2620:1ec:8ec:700::d0 and 150.171.21.208; ns3.bdm.microsoftonline.com points to 2a01:111:4000:700::d0 and 204.14.183.208; ns4.bdm.microsoftonline.com points to 2620:1ec:bda:700::d0 and 208.84.5.208.

Mail Servers

lasignsbanners.com is handled by a single mail server, lasignsbanners-com.mail.protection.outlook.com.

Host lasignsbanners-com.mail.protection.outlook.com points to eight IP numbers: 2a01:111:f403:c92c::2, 2a01:111:f403:c931::, 2a01:111:f403:f902::2, 2a01:111:f403:f903::, 52.101.8.34, 52.101.11.15, 52.101.11.19 and 52.101.41.6.

lasignsbanners.com - robtex.com