leadlogsys.com - dns.ninja
leadlogsys.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=1783193941 | ||||||
Subdomains
Same first word
leadlogsys.com |
DNS History
13 records (10 active, 3 former)
●NSns01.domaincontrol.com2020-03-16 → 2026-07-04 · 3 obs
● 2020-03-16 04:22:16
● 2026-07-04 20:02:32
●NSns02.domaincontrol.com2020-03-16 → 2026-07-04 · 3 obs
● 2020-03-16 04:22:16
● 2026-07-04 20:02:32
○NSns1.mediatemple.net2015-06-17 → 2017-04-01 · 4 obs
● 2017-04-01 20:09:48
○ 2020-03-16 04:22:16
○ 2026-07-04 20:02:32
○NSns2.mediatemple.net2015-06-17 → 2017-04-01 · 4 obs
● 2017-04-01 20:09:48
○ 2020-03-16 04:22:16
○ 2026-07-04 20:02:32
●MXalt1.aspmx.l.google.com2015-06-17 → 2026-07-04 · 2 obs
● 2026-07-04 20:02:32
●MXalt2.aspmx.l.google.com2015-06-17 → 2026-07-04 · 2 obs
● 2026-07-04 20:02:32
●MXaspmx.l.google.com2015-06-17 → 2026-07-04 · 2 obs
● 2026-07-04 20:02:32
●MXaspmx2.googlemail.com2015-06-17 → 2026-07-04 · 2 obs
● 2026-07-04 20:02:32
●MXaspmx3.googlemail.com2015-06-17 → 2026-07-04 · 2 obs
● 2026-07-04 20:02:32
●MXaspmx4.googlemail.com2015-06-17 → 2026-07-04 · 2 obs
● 2026-07-04 20:02:32
●MXaspmx5.googlemail.com2015-06-17 → 2026-07-04 · 2 obs
● 2026-07-04 20:02:32
○A216.70.101.832015-06-17 → 2017-04-01 · 4 obs
● 2017-04-01 20:09:48
○ 2020-03-16 04:22:16
○ 2026-07-04 20:02:32
●A51.81.16.2292020-03-16 → 2026-07-04 · 3 obs
● 2020-03-16 04:22:16
● 2026-07-04 20:02:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | k.gtld-servers.net, b.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net... | - |
| leadlogsys.com | ns01.domaincontrol.com, ns02.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.68.1
NS records: ns01.domaincontrol.com, ns02.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for leadlogsys.com (unsigned zone)
⏱️ Timing
Total: 135ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 51.81.16.229 |
| NS | 2 | ns01.domaincontrol.com, ns02.domaincontrol.com |
| MX | 7 | aspmx3.googlemail.com (pri: 30), aspmx2.googlemail.com (pri: 30)... |
| SOA | 1 | ns01.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns01.domaincontrol.com, ns01.domaincontrol.com, ns02.domaincontrol.com...)
Analysis
Hierarchy
The parent domain of mail.leadlogsys.com and sprinklr.leadlogsys.com is leadlogsys.com.
IP Addresses
leadlogsys.com directs to one IP number, which is 51.81.16.229.
Among the host names that share IP numbers with leadlogsys.com are mail.leadlogsys.com, sprinklr.leadlogsys.com, www.sprinklr.leadlogsys.com and two others.
Name Servers
Two name servers handle the delegation for leadlogsys.com: ns01.domaincontrol.com and ns02.domaincontrol.com.
leadlogsys.com has the same name server delegation as a number of other domains, such as schroepferfamily.com, thinkunlike.com, checkinconsulting.com and two more.
leadlogsys.com is at least partially co-delegated on name servers with other domains, such as cedarbrook.biz.
ns01.domaincontrol.com and ns02.domaincontrol.com both carry two IP addresses. The A records for ns01.domaincontrol.com are 97.74.100.1 and 2603:5:2140::1; the A records for ns02.domaincontrol.com are 173.201.68.1 and 2603:5:2240::1.
Mail Servers
leadlogsys.com is handled by 7 mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and 4 other.
leadlogsys.com shares at least some of its mail servers with other domains — for example ns500671.ns500731.ns500671.ns500754.ns500731.ns500754.ns500705.ns500705.ns500704.ns500705.ns500688.ns500649.ns500688.ns500649.ns500649.ns500666.tenderladiesbz.com, ns500768.ns500759.ns500758.ns500758.ns500759.ns500698.ns500736.ns500698.ns500735.ns500735.ns500735.ns500576.ns500576.ns500576.ns500576.ns500619.ns500576.trackreceptor.com, sherwoodchevrolet.com and two more.
It is common to find these mail servers paired with mail servers alt2.aspmx.l.google.com, aspmx.l.google.com, alt1.aspmx.l.google.com and 3 more.
Hosts with two IP numbers each:
aspmx2.googlemail.com resolves to two addresses: 108.177.123.27 and 2800:3f0:4003:c0f::1b.
aspmx3.googlemail.com resolves to two addresses: 172.253.116.26 and 2a00:1450:400b:c02::1b.
aspmx4.googlemail.com resolves to two addresses: 192.178.223.26 and 2a00:1450:4009:c0f::1a.
aspmx5.googlemail.com resolves to two addresses: 172.253.157.27 and 2a00:1450:400c:c23::1a.
aspmx.l.google.com resolves to two addresses: 142.251.167.27 and 2607:f8b0:4004:c1d::1b.
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::1b.
aspmx2.googlemail.com along with alt1.aspmx.l.google.com each resolve to 2800:3f0:4003:c0f::1b IP addresses.
aspmx2.googlemail.com along with alt1.aspmx.l.google.com each resolve to 108.177.123.27 IP addresses.
aspmx3.googlemail.com along with alt2.aspmx.l.google.com each resolve to 2a00:1450:400b:c02::1b IP addresses.