`bma-solutions.com`

DNSSEC	⚠️ Not signed
NS	`dns1.lf.net` ⭐
		A	2001:14b0:0:1:212:9:160:10^{🇩🇪 LFNET-AS012001:14b0::/32 LF.net IPv6}
			PTR	`dns1.lf.net`
		A	212.9.160.10^{🇩🇪 LFNET-AS01212.9.160.0/19 LFNET-RO-01}
			PTR	`dns1.lf.net`
NS	`dns2.lf.net`
		A	62.50.111.2^{🇩🇪 LFNET-AS0162.50.96.0/19 LFNET-RO-04}
			PTR	`dns2.lf.net`
NS	`dns3.lf.net`
		A	3.77.208.173^{🇩🇪 Amazon3.64.0.0/12 EC2 FRA Prefix}
			PTR	`ec2-3-77-208-173.eu-central-1.compute.amazonaws.com`
MX	`bmasolutions-com0i.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:ca04::f^{🇮🇪 Microsoft2a01:111:f000::/36}
			PTR	`mail-db7pr03cu00507.inbound.protection.outlook.com`
		A	2a01:111:f403:ca04::10^{🇮🇪 Microsoft2a01:111:f000::/36}
			PTR	`mail-dbapr03cu00100.inbound.protection.outlook.com`
		A	2a01:111:f403:ca09::5^{🇳🇱 Microsoft2a01:111:f000::/36}
			PTR	`mail-am1pr04cu00105.inbound.protection.outlook.com`
		A	2a01:111:f403:ca09::7^{🇳🇱 Microsoft2a01:111:f000::/36}
			PTR	`mail-am9pr04cu00107.inbound.protection.outlook.com`
		A	52.101.68.3^{🇮🇪 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-db7pr03cu00403.inbound.protection.outlook.com`
		A	52.101.73.11^{🇳🇱 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-am1pr04cu00103.inbound.protection.outlook.com`
		A	52.101.73.19^{🇳🇱 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-as8pr04cu00803.inbound.protection.outlook.com`
		A	52.101.73.26^{🇳🇱 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-as9pr05cu01302.inbound.protection.outlook.com`
TXT	`zscaler-verification-96124-02072026-6tqcos54`
TXT	`MS=ms46373357`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
SOA	`dns1.LF.net`hostmaster@LF.net 2026-07-02 #0

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

Similar names

bam-solutions.de

DNS History

4 records (4 active, 0 former)

●NSdns1.lf.net2026-08-02 → 2026-08-02 · 2 obs

● 2026-08-02 20:42:46
● 2026-08-02 20:42:48

●NSdns2.lf.net2026-08-02 → 2026-08-02 · 2 obs

● 2026-08-02 20:42:46
● 2026-08-02 20:42:48

●NSdns3.lf.net2026-08-02 → 2026-08-02 · 2 obs

● 2026-08-02 20:42:46
● 2026-08-02 20:42:48

●MXbmasolutions-com0i.mail.protection.outlook.com2026-08-02 → 2026-08-02 · 2 obs

● 2026-08-02 20:42:46
● 2026-08-02 20:42:48

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
bma-solutions.com	dns1.lf.net, dns2.lf.net, dns3.lf.net	-

✅ Authoritative Response

Server:62.50.111.2

NS records: dns1.lf.net, dns2.lf.net, dns3.lf.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bma-solutions.com (unsigned zone)

⏱️ Timing

Total: 634ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	3	`dns2.LF.net, dns3.LF.net...`
MX	1	`bmasolutions-com0i.mail.protection.outlo`
TXT	3	`v=spf1 include:spf.protection.outlook.co, MS=ms46373357...`
SOA	1	`dns1.LF.net hostmaster.LF.net`

Analysis

Name Servers

DNS for bma-solutions.com is handled by three authoritative name servers: dns1.lf.net, dns2.lf.net and dns3.lf.net.

At least some of bma-solutions.com's name servers are shared with other domains, for example ib-koehler.de, unit-eins.de, topraid.de and two more.

These name servers tend to be deployed in combination with the name servers ns.lf.net and ns2.lf.net.

Host names with two IP numbers:

dns1.lf.net has two IP addresses: 212.9.160.10 and 2001:14b0:0:1:212:9:160:10.

Host names pointing to a single IP address:

dns2.lf.net directs to 62.50.111.2.

dns3.lf.net directs to 3.77.208.173.