leadenforce.com - dns.ninja
leadenforce.com
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.netnstld@verisign-grs.com serial=1780931946 | ||||||
Subdomains
app.leadenforce.com |
Same first word
leadenforce.com |
DNS History
15 records (9 active, 6 former)
●NSdns1.registrar-servers.com2018-06-07 → 2026-06-08 · 2 obs
● 2026-06-08 15:30:06
●NSdns2.registrar-servers.com2018-06-07 → 2026-06-08 · 2 obs
● 2026-06-08 15:30:06
●MXalt1.aspmx.l.google.com2026-05-18 → 2026-06-08 · 3 obs
● 2026-05-18 11:51:00
● 2026-06-08 15:30:06
●MXalt2.aspmx.l.google.com2026-05-18 → 2026-06-08 · 3 obs
● 2026-05-18 11:51:00
● 2026-06-08 15:30:06
●MXalt3.aspmx.l.google.com2026-05-18 → 2026-06-08 · 3 obs
● 2026-05-18 11:51:00
● 2026-06-08 15:30:06
●MXalt4.aspmx.l.google.com2026-05-18 → 2026-06-08 · 3 obs
● 2026-05-18 11:51:00
● 2026-06-08 15:30:06
●MXard3ugeepolprr3gch2sctwpdc3r2pd7h2wdpqobwoswtsm72nwa.mx-verification.google.com2026-05-18 → 2026-06-08 · 3 obs
● 2026-05-18 11:51:00
● 2026-06-08 15:30:06
●MXaspmx.l.google.com2026-05-18 → 2026-06-08 · 3 obs
● 2026-05-18 11:51:00
● 2026-06-08 15:30:06
○MXeforward1.registrar-servers.com2018-06-07 → 2018-06-07 · 3 obs
○ 2026-05-18 11:51:00
○ 2026-06-08 15:30:06
○MXeforward2.registrar-servers.com2018-06-07 → 2018-06-07 · 3 obs
○ 2026-05-18 11:51:00
○ 2026-06-08 15:30:06
○MXeforward3.registrar-servers.com2018-06-07 → 2018-06-07 · 3 obs
○ 2026-05-18 11:51:00
○ 2026-06-08 15:30:06
○MXeforward4.registrar-servers.com2018-06-07 → 2018-06-07 · 3 obs
○ 2026-05-18 11:51:00
○ 2026-06-08 15:30:06
○MXeforward5.registrar-servers.com2018-06-07 → 2018-06-07 · 3 obs
○ 2026-05-18 11:51:00
○ 2026-06-08 15:30:06
●A144.31.24.382026-05-18 → 2026-06-08 · 3 obs
● 2026-05-18 11:51:00
● 2026-06-08 15:30:06
○A192.64.119.2212018-06-07 → 2018-06-07 · 3 obs
○ 2026-05-18 11:51:00
○ 2026-06-08 15:30:06
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| leadenforce.com | dns1.registrar-servers.com, dns2.registrar-servers.com | 4 records |
✅ Authoritative Response
Server:156.154.133.200
NS records: dns1.registrar-servers.com, dns2.registrar-servers.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for leadenforce.com (unsigned zone)
⏱️ Timing
Total: 1208ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 144.31.24.38 |
| NS | 2 | dns1.registrar-servers.com, dns2.registrar-servers.com |
| MX | 6 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 4 | mandrill_verify.lfGchkXthOIpaFEdo9l-dg, v=DMARC1; p=quarantine; rua=mailto:suppo... |
| SOA | 1 | dns1.registrar-servers.com hostmaster.re |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (dns1.registrar-servers.com, dns1.registrar-servers.com, dns2.registrar-servers.com...)
Analysis
Hierarchy
leadenforce.com serves as the parent of app.leadenforce.com.
IP Addresses
leadenforce.com resolves to just one IP address, 144.31.24.38.
Host names like app.leadenforce.com are further examples that share IP numbers with leadenforce.com.
Name Servers
Two name servers handle the delegation for leadenforce.com: dns1.registrar-servers.com and dns2.registrar-servers.com.
leadenforce.com shares its NS records with other domains, for example eoiv.net, nativephrase.com, stevefar.com and two others.
leadenforce.com has at least partial name server overlap with other domains, such as gleenn.com, buffalostartups.com, newstint.com and two others.
These name servers tend to appear together with the name servers dns3.registrar-servers.com, dns4.registrar-servers.com and dns5.registrar-servers.com.
dns1.registrar-servers.com and dns2.registrar-servers.com both carry two IP addresses. The A records for dns1.registrar-servers.com are 156.154.132.200 and 2610:a1:1024::200; the A records for dns2.registrar-servers.com are 156.154.133.200 and 2610:a1:1025::200.
Mail Servers
leadenforce.com is handled by 6 mail servers, aspmx.l.google.com, ard3ugeepolprr3gch2sctwpdc3r2pd7h2wdpqobwoswtsm72nwa.mx-verification.google.com, alt1.aspmx.l.google.com and three other.
There is at least a partial MX overlap between leadenforce.com and other domains, including ns500754.ns500754.ns500754.ns500678.ns500678.ns500291.ns500678.ns500666.ns500142.lusty(0x736c7574)z.com, ns500759.ns500759.ns500758.ns500698.ns500698.ns500698.ns500708.ns500576.ns500576.ns500576.ns500652.ns500619.ns500652.tracksymphony.com, ns500758.ns500758.ns500759.ns500758.ns500736.ns500736.ns500736.ns500698.ns500576.ns500576.ns500619.ns500686.ns500619.ns500576.trackreceptor.com and two others.
These mail servers frequently co-occur with the mail servers alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.com and two others.
Host names that have two IP addresses:
aspmx.l.google.com resolves to two addresses: 172.253.63.26 and 2607:f8b0:4004:c0b::1a.
alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.27 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.27 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com resolves to two addresses: 192.178.223.27 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com resolves to two addresses: 173.194.76.27 and 2a00:1450:400c:c00::1b.