leadengine.co - dns.ninja
leadengine.co
co
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns0.centralnic.net ⭐ | ||||||
| NS | a.registrydns.co | ||||||
| NS | b.registrydns.co | ||||||
| NS | c.registrydns.co | ||||||
| NS | d.registrydns.co | ||||||
| SOA | ns0.centralnic.nethostmaster@centralnic.net serial=1759682838 | ||||||
Same first word
leadengine.us |
leadengine.hu |
leadengine.co |
leadengine.com |
leadengine.de |
leadengine.eu |
leadengine.info |
leadengine.io |
leadengine.com.au |
leadengine.pro |
leadengine.ai |
leadengine.nl |
leadengine.org |
leadengine.it |
Similar names
enginelead.com |
eingeladen.com |
neildeegan.com |
enginedeal.com |
deineangel.de |
dealengine.com |
neildeegan.org |
eliandegen.com |
eingeladen.de |
DNS History
21 records (9 active, 12 former)
○NSbuy.internettraffic.com2015-07-05 → 2016-05-01 · 4 obs
● 2016-05-01 16:08:08
○ 2017-02-07 10:53:46
○ 2026-06-15 14:39:02
○NSdns1.registrar-servers.com2017-02-07 → 2020-02-02 · 5 obs
● 2017-02-07 10:53:46
● 2020-02-02 13:17:00
○ 2026-03-24 08:43:30
○ 2026-06-15 14:39:02
○NSdns2.registrar-servers.com2017-02-07 → 2020-02-02 · 5 obs
● 2017-02-07 10:53:46
● 2020-02-02 13:17:00
○ 2026-03-24 08:43:30
○ 2026-06-15 14:39:02
●NSns-cloud-a1.googledomains.com2026-03-24 → 2026-06-15 · 3 obs
● 2026-03-24 08:43:30
● 2026-06-15 14:39:02
●NSns-cloud-a2.googledomains.com2026-03-24 → 2026-06-15 · 3 obs
● 2026-03-24 08:43:30
● 2026-06-15 14:39:02
●NSns-cloud-a3.googledomains.com2026-03-24 → 2026-06-15 · 3 obs
● 2026-03-24 08:43:30
● 2026-06-15 14:39:02
●NSns-cloud-a4.googledomains.com2026-03-24 → 2026-06-15 · 3 obs
● 2026-03-24 08:43:30
● 2026-06-15 14:39:02
○NSsell.internettraffic.com2015-07-05 → 2016-05-01 · 4 obs
● 2016-05-01 16:08:08
○ 2017-02-07 10:53:46
○ 2026-06-15 14:39:02
○MXeforward1.registrar-servers.com2017-02-07 → 2020-02-02 · 4 obs
● 2020-02-02 13:17:00
○ 2026-03-24 08:43:30
○ 2026-06-15 14:39:02
○MXeforward2.registrar-servers.com2017-02-07 → 2020-02-02 · 4 obs
● 2020-02-02 13:17:00
○ 2026-03-24 08:43:30
○ 2026-06-15 14:39:02
○MXeforward3.registrar-servers.com2017-02-07 → 2020-02-02 · 4 obs
● 2020-02-02 13:17:00
○ 2026-03-24 08:43:30
○ 2026-06-15 14:39:02
○MXeforward4.registrar-servers.com2017-02-07 → 2020-02-02 · 4 obs
● 2020-02-02 13:17:00
○ 2026-03-24 08:43:30
○ 2026-06-15 14:39:02
○MXeforward5.registrar-servers.com2017-02-07 → 2020-02-02 · 4 obs
● 2020-02-02 13:17:00
○ 2026-03-24 08:43:30
○ 2026-06-15 14:39:02
●MXsmtp.google.com2026-03-24 → 2026-06-15 · 3 obs
● 2026-03-24 08:43:30
● 2026-06-15 14:39:02
○A162.255.119.2492017-02-07 → 2020-02-02 · 5 obs
● 2017-02-07 10:53:46
● 2020-02-02 13:17:00
○ 2026-03-24 08:43:30
○ 2026-06-15 14:39:02
●A198.185.159.1442026-03-24 → 2026-06-15 · 3 obs
● 2026-03-24 08:43:30
● 2026-06-15 14:39:02
●A198.185.159.1452026-03-24 → 2026-06-15 · 3 obs
● 2026-03-24 08:43:30
● 2026-06-15 14:39:02
●A198.49.23.1442026-03-24 → 2026-06-15 · 3 obs
● 2026-03-24 08:43:30
● 2026-06-15 14:39:02
●A198.49.23.1452026-03-24 → 2026-06-15 · 3 obs
● 2026-03-24 08:43:30
● 2026-06-15 14:39:02
○A69.172.201.1532016-05-01 → 2016-05-01 · 4 obs
● 2016-05-01 16:08:08
○ 2017-02-07 10:53:46
○ 2026-06-15 14:39:02
○A69.172.201.2082015-07-05 → 2016-01-28 · 4 obs
● 2016-01-28 10:58:50
○ 2016-05-01 16:08:08
○ 2026-06-15 14:39:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| co | a.registrydns.co, b.registrydns.co, c.registrydns.co, d.registrydns.co | - |
| leadengine.co | ns-cloud-a3.googledomains.com, ns-cloud-a1.googledomains.com, ns-cloud-a4.googledomains.com, ns-cloud-a2.googledomains.com | - |
✅ Authoritative Response
Server:216.239.32.106
NS records: ns-cloud-a3.googledomains.com, ns-cloud-a1.googledomains.com, ns-cloud-a4.googledomains.com, ns-cloud-a2.googledomains.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for leadengine.co (unsigned zone)
⏱️ Timing
Total: 606ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 4 | 198.49.23.144, 198.185.159.145... |
| NS | 4 | ns-cloud-a1.googledomains.com, ns-cloud-a4.googledomains.com... |
| MX | 1 | smtp.google.com (pri: 1) |
| TXT | 1 | v=spf1 include:_spf.google.com ~all |
| HTTPS | 1 | {"priority":1,"target":".","alpn":["h2", |
| SOA | 1 | ns-cloud-a1.googledomains.com cloud-dns- |
Analysis
IP Addresses
leadengine.co resolves to four IP addresses: 198.49.23.144, 198.49.23.145, 198.185.159.144 and 198.185.159.145.
Additional host names — 4elevenbuilders.com, moonwebs.com, 41willcome.com and two others — share IP numbers with leadengine.co.
Name Servers
leadengine.co has four authoritative name servers: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com and ns-cloud-a4.googledomains.com.
leadengine.co has at least partial name server overlap with other domains, such as fueloz.com, gabetti.org, thrivingintiedye.com and two others.
ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com and ns-cloud-a4.googledomains.com all point to exactly two IP numbers each: ns-cloud-a1.googledomains.com → 216.239.32.106 and 2001:4860:4802:32::6a; ns-cloud-a2.googledomains.com → 216.239.34.106 and 2001:4860:4802:34::6a; ns-cloud-a3.googledomains.com → 216.239.36.106 and 2001:4860:4802:36::6a; ns-cloud-a4.googledomains.com → 216.239.38.106 and 2001:4860:4802:38::6a.
Mail Servers
leadengine.co has one mail server: smtp.google.com.
leadengine.co shares the same mail server setup as other domains, including moriah.us, kindesign.com, codegea.com and two others.
leadengine.co shares mail servers — at least in part — with other domains, including acgg.org, eqwise.nl, gkce.edu.in and two others.
These mail servers tend to appear together with the mail servers alt1.aspmx.l.google.com, aspmx.l.google.com and alt2.aspmx.l.google.com.
smtp.google.com points to 9 IP numbers: 142.251.16.27, 142.251.163.26, 142.251.163.27 and 6 other.