leadbelay.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`leadbelay.com`

DNSSEC	⚠️ Not signed
A	199.60.103.56^{🇺🇸 CLOUDFLARESPECTRUM199.60.103.0/24 MNT-HUBSP-8 route 199.060.103.000/24 AS209242}
A	199.60.103.156^{🇺🇸 CLOUDFLARESPECTRUM199.60.103.0/24 MNT-HUBSP-8 route 199.060.103.000/24 AS209242}
NS	`ns63.domaincontrol.com` ⭐
		A	2603:5:2154::2a^{🇺🇸 GODADDY-DNS2603:5:2150::/44}
			PTR	`ns63.domaincontrol.com`
		A	97.74.101.42^{🇺🇸 GODADDY-DNS97.74.100.0/23}
			PTR	`ns63.domaincontrol.com`
NS	`ns64.domaincontrol.com`
		A	2603:5:2254::2a^{🇺🇸 GODADDY-DNS2603:5:2250::/44}
			PTR	`ns64.domaincontrol.com`
		A	173.201.69.42^{🇺🇸 GODADDY-DNS173.201.68.0/23}
			PTR	`ns64.domaincontrol.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1b::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`wv-in-f26.1e100.net`
		A	142.251.163.27^{🇺🇸 Google142.251.163.0/24}
			PTR	`wv-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.26^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-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.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
MX	`isegx3lj5ogu3gey6zd2yx4d3dr6hgfwc32quicykgvwlsqbm2xa.mx-verification.google.com`⁽¹⁵⁾
TXT	`facebook-domain-verification=ix3z99bnq5fvndtt488y5v1sk655kq`
TXT	`v=spf1 include:14511955.spf01.hubspotemail.net include:_spf.google.com ~all`
TXT	`google-site-verification=RIhr7WnrjU2YmPZHrF-D2OPjmLYW9QogWFGrZcoBZq4`
TXT	`include:14511955.spf01.hubspotemail.net`
TXT	`ZOOM_verify_Zg(0x35486954)kyO6AOcaDOZmaOJa`
TXT	`h9qutp1vj4h86936k3h0ved7u`
SOA	`ns63.domaincontrol.com`dns@jomax.net 2026-08-14 #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=1786871649

Same first word

leadbelay.com

Similar names

beadalley.com

delayable.com

DNS History

15 records (10 active, 5 former)

●NSns63.domaincontrol.com2026-02-14 → 2026-08-16 · 3 obs

○ 2017-08-17 23:22:48
● 2026-02-14 19:11:20
● 2026-08-16 09:34:56

●NSns64.domaincontrol.com2026-02-14 → 2026-08-16 · 3 obs

○ 2017-08-17 23:22:48
● 2026-02-14 19:11:20
● 2026-08-16 09:34:56

○NSns65.domaincontrol.com2016-12-15 → 2016-12-15 · 3 obs

● 2016-12-15 10:39:36
○ 2017-08-17 23:22:48
○ 2026-08-16 09:34:56

○NSns66.domaincontrol.com2016-12-15 → 2016-12-15 · 3 obs

● 2016-12-15 10:39:36
○ 2017-08-17 23:22:48
○ 2026-08-16 09:34:56

●MXalt1.aspmx.l.google.com2026-02-14 → 2026-08-16 · 3 obs

○ 2017-08-17 23:22:48
● 2026-02-14 19:11:20
● 2026-08-16 09:34:56

●MXalt2.aspmx.l.google.com2026-02-14 → 2026-08-16 · 3 obs

○ 2017-08-17 23:22:48
● 2026-02-14 19:11:20
● 2026-08-16 09:34:56

●MXalt3.aspmx.l.google.com2026-02-14 → 2026-08-16 · 3 obs

○ 2017-08-17 23:22:48
● 2026-02-14 19:11:20
● 2026-08-16 09:34:56

●MXalt4.aspmx.l.google.com2026-02-14 → 2026-08-16 · 3 obs

○ 2017-08-17 23:22:48
● 2026-02-14 19:11:20
● 2026-08-16 09:34:56

●MXaspmx.l.google.com2026-02-14 → 2026-08-16 · 3 obs

○ 2017-08-17 23:22:48
● 2026-02-14 19:11:20
● 2026-08-16 09:34:56

●MXisegx3lj5ogu3gey6zd2yx4d3dr6hgfwc32quicykgvwlsqbm2xa.mx-verification.google.com2026-02-14 → 2026-08-16 · 3 obs

○ 2017-08-17 23:22:48
● 2026-02-14 19:11:20
● 2026-08-16 09:34:56

○MXmailstore1.secureserver.net2016-12-15 → 2016-12-15 · 3 obs

● 2016-12-15 10:39:36
○ 2017-08-17 23:22:48
○ 2026-08-16 09:34:56

○MXsmtp.secureserver.net2016-12-15 → 2016-12-15 · 3 obs

● 2016-12-15 10:39:36
○ 2017-08-17 23:22:48
○ 2026-08-16 09:34:56

●A199.60.103.1562026-02-14 → 2026-08-16 · 3 obs

○ 2017-08-17 23:22:48
● 2026-02-14 19:11:20
● 2026-08-16 09:34:56

●A199.60.103.562026-02-14 → 2026-08-16 · 3 obs

○ 2017-08-17 23:22:48
● 2026-02-14 19:11:20
● 2026-08-16 09:34:56

○A50.63.202.522016-12-15 → 2016-12-15 · 3 obs

● 2016-12-15 10:39:36
○ 2017-08-17 23:22:48
○ 2026-08-16 09:34:56

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	c.gtld-servers.net, b.gtld-servers.net, f.gtld-servers.net, j.gtld-servers.net...	-
leadbelay.com	ns63.domaincontrol.com, ns64.domaincontrol.com	4 records

✅ Authoritative Response

Server:97.74.101.42

NS records: ns63.domaincontrol.com, ns64.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for leadbelay.com (unsigned zone)

⏱️ Timing

Total: 226ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`199.60.103.156, 199.60.103.56`
NS	2	`ns64.domaincontrol.com, ns63.domaincontrol.com`
MX	6	`alt2.aspmx.l.google.com (pri: 5), aspmx.l.google.com (pri: 1)...`
TXT	6	`facebook-domain-verification=ix3z99bnq5f, v=spf1 include:14511955.spf01.hubspotema...`
SOA	1	`ns63.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns63.domaincontrol.com, ns63.domaincontrol.com, ns64.domaincontrol.com...)

Analysis

IP Addresses

leadbelay.com has two IP addresses: 199.60.103.56 and 199.60.103.156

debos.ai, asjp.dk, fuelius.com plus two other host names have IP numbers in common with leadbelay.com.

Name Servers

DNS delegation for leadbelay.com points to two name servers: ns63.domaincontrol.com and ns64.domaincontrol.com.

The name server configuration of leadbelay.com is shared with other domains, for instance traptie.com, sophiasiopenai.com, karmakametaromatic.com and two others.

ns63.domaincontrol.com directs to 97.74.101.42 and 2603:5:2154::2a. ns64.domaincontrol.com directs to 173.201.69.42 and 2603:5:2254::2a. Each host name carries two IP addresses.

Mail Servers

leadbelay.com has 6 mail servers — aspmx.l.google.com, isegx3lj5ogu3gey6zd2yx4d3dr6hgfwc32quicykgvwlsqbm2xa.mx-verification.google.com, alt1.aspmx.l.google.com plus 3 other.

At least some of the mail servers used by leadbelay.com are shared with other domains: server23.myrealhost.com, wogic.eu, ns500841.ns500841.ns500794.ns500795.ns500794.ns500795.ns500794.ns500795.ns500790.ns500795.lustypartnersfinder.com and two others among them.

It is common to find these mail servers paired with the mail servers alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com, as well as two others.

Host names pointing to two IP addresses:

aspmx.l.google.com has two IP addresses: 142.251.163.27 and 2607:f8b0:4004:c1b::1a.

alt1.aspmx.l.google.com has two IP addresses: 192.178.234.26 and 2800:3f0:4003:c14::1b.

alt2.aspmx.l.google.com has two IP addresses: 172.253.116.27 and 2a00:1450:400b:c02::1a.

alt3.aspmx.l.google.com has two IP addresses: 192.178.223.27 and 2a00:1450:4009:c0f::1a.

alt4.aspmx.l.google.com has two IP addresses: 172.253.157.26 and 2a00:1450:400c:c23::1b.