`mleasing.com`

DNSSEC	⚠️ Not signed
NS	`dns1.name-services.com` ⚠️ Not in zone NS records
		A	2604:4000:2800:2000:64:98:148:137^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`dns1.name-services.com`
		A	64.98.148.137^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}
NS	`dns2.name-services.com` ⚠️ Not in zone NS records
		A	2604:4000:0:d:216:40:47:201^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`dns2.name-services.com`
		A	216.40.47.201^{🇨🇦 TUCOWS216.40.47.0/24 -BRA-BLK1.4/NET-216-40-47-0}
NS	`dns3.name-services.com` ⚠️ Not in zone NS records
		A	2604:4000:2800:2000:64:98:148:138^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`dns3.name-services.com`
		A	64.98.148.138^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}
NS	`dns4.name-services.com` ⚠️ Not in zone NS records
		A	2604:4000:0:d:216:40:47:202^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`dns4.name-services.com`
		A	216.40.47.202^{🇨🇦 TUCOWS216.40.47.0/24 -BRA-BLK1.4/NET-216-40-47-0}
NS	`dns5.name-services.com` ⚠️ Not in zone NS records
		A	2604:4000:2800:2000:64:98:148:139^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`dns5.name-services.com`
		A	64.98.148.139^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}

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

Same first word

mleasing.ru

mleasing.com

mleasing.finance

mleasing.bg

mleasing.pl

mleasing.de

Similar names

DNS History

8 records (5 active, 3 former)

●NSdns1.name-services.com2015-06-14 → 2026-08-06 · 2 obs

● 2015-06-14 23:21:18
● 2026-08-06 12:15:42

●NSdns2.name-services.com2015-06-14 → 2026-08-06 · 2 obs

● 2015-06-14 23:21:18
● 2026-08-06 12:15:42

●NSdns3.name-services.com2015-06-14 → 2026-08-06 · 2 obs

● 2015-06-14 23:21:18
● 2026-08-06 12:15:42

●NSdns4.name-services.com2015-06-14 → 2026-08-06 · 2 obs

● 2015-06-14 23:21:18
● 2026-08-06 12:15:42

●NSdns5.name-services.com2015-06-14 → 2026-08-06 · 2 obs

● 2015-06-14 23:21:18
● 2026-08-06 12:15:42

○A98.124.198.12015-06-14 → 2015-06-14 · 3 obs

● 2015-06-14 23:21:18
○ 2017-05-27 18:38:04
○ 2026-08-06 12:15:42

○A98.124.199.12015-06-14 → 2015-10-29 · 4 obs

● 2015-06-14 23:21:18
● 2015-10-29 17:19:58
○ 2016-01-19 06:36:34
○ 2026-08-06 12:15:42

○A98.124.199.182016-01-19 → 2017-05-27 · 5 obs

○ 2015-10-29 17:19:58
● 2016-01-19 06:36:34
● 2017-05-27 18:38:04
○ 2026-06-29 16:23:22
○ 2026-08-06 12:15:42

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
mleasing.com	dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com...	10 records

✅ Authoritative Response

Server:64.98.148.137

NS records: dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com, dns5.name-services.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for mleasing.com (unsigned zone)

⏱️ Timing

Total: 306ms | Queries: -

📄 Records

Type	Count	Sample Data

📌 Glue Records Collected

Total: 10

Out-of-bailiwick: 10 (dns1.name-services.com, dns1.name-services.com, dns2.name-services.com...)

Analysis

Name Servers

Five name servers handle delegation for mleasing.com: dns1.name-services.com, dns2.name-services.com, dns3.name-services.com and two others.

mleasing.com partially shares its NS delegation with several other domains, including aabuyer.com, harrisware.com, myboulle.org and two others.

These name servers are regularly seen alongside dns4.name-services.com and dns5.name-services.com as name servers.

Host names pointing to two IP addresses:

dns1.name-services.com directs traffic to 64.98.148.137 and 2604:4000:2800:2000:64:98:148:137.

dns2.name-services.com directs traffic to 216.40.47.201 and 2604:4000:0:d:216:40:47:201.

dns3.name-services.com directs traffic to 64.98.148.138 and 2604:4000:2800:2000:64:98:148:138.

dns4.name-services.com directs traffic to 216.40.47.202 and 2604:4000:0:d:216:40:47:202.

dns5.name-services.com directs traffic to 64.98.148.139 and 2604:4000:2800:2000:64:98:148:139.