leadrop.com - dns.ninja
leadrop.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 23.224.40.221🇺🇸 CNSERVERSLLC23.224.0.0/15 cust proxy reg | ||||||
| NS | ns1.dns.com ⭐ | ||||||
| A | 2001:df2:f080:2::1:1🇭🇰 HKCICL-AS-AP2001:df2:f080::/48 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED | ||||||
| A | 154.23.191.128🇺🇸 HKCICL-AS-AP154.23.191.0/24 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED | ||||||
| A | 154.86.21.128🇭🇰 HKCICL-AS-AP154.86.21.0/24 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED | ||||||
| NS | ns2.dns.com | ||||||
| A | 2001:df2:f080:2::1:2🇭🇰 HKCICL-AS-AP2001:df2:f080::/48 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED | ||||||
| A | 154.23.191.129🇺🇸 HKCICL-AS-AP154.23.191.0/24 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED | ||||||
| A | 154.86.21.129🇭🇰 HKCICL-AS-AP154.86.21.0/24 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED | ||||||
| SOA | ns1.dns.comadmin@dns.com serial=1773385096 | ||||||
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=1781288928 | ||||||
Same first word
leadrop.com |
Similar names
DNS History
17 records (3 active, 14 former)
○NSns1.bluehost-default.domainparkingserver.net2026-05-11 → 2026-06-12 · 2 obs
○ 2026-06-12 18:34:32
○NSns1.bluehost.com2016-12-18 → 2016-12-18 · 3 obs
○ 2026-05-11 11:50:16
○ 2026-06-12 18:34:32
●NSns1.dns.com2026-05-11 → 2026-06-12 · 3 obs
● 2026-05-11 11:50:16
● 2026-06-12 18:34:32
○NSns2.bluehost-default.domainparkingserver.net2026-05-11 → 2026-06-12 · 2 obs
○ 2026-06-12 18:34:32
○NSns2.bluehost.com2016-12-18 → 2016-12-18 · 3 obs
○ 2026-05-11 11:50:16
○ 2026-06-12 18:34:32
●NSns2.dns.com2026-05-11 → 2026-06-12 · 3 obs
● 2026-05-11 11:50:16
● 2026-06-12 18:34:32
○MX~2026-05-11 → 2026-06-12 · 2 obs
○ 2026-06-12 18:34:32
○MXfallbackmx.spamexperts.eu2016-12-18 → 2016-12-18 · 3 obs
○ 2026-05-11 11:50:16
○ 2026-06-12 18:34:32
○MXlastmx.spamexperts.net2016-12-18 → 2016-12-18 · 3 obs
○ 2026-05-11 11:50:16
○ 2026-06-12 18:34:32
○MXmx.spamexperts.com2016-12-18 → 2016-12-18 · 3 obs
○ 2026-05-11 11:50:16
○ 2026-06-12 18:34:32
●A23.224.40.2212026-05-11 → 2026-06-12 · 3 obs
● 2026-05-11 11:50:16
● 2026-06-12 18:34:32
○A66.81.203.1332026-05-11 → 2026-06-12 · 2 obs
○ 2026-06-12 18:34:32
○A66.81.203.1982026-05-11 → 2026-06-12 · 2 obs
○ 2026-06-12 18:34:32
○A66.81.203.82026-05-11 → 2026-06-12 · 2 obs
○ 2026-06-12 18:34:32
○A70.40.220.692016-12-18 → 2016-12-18 · 3 obs
○ 2026-05-11 11:50:16
○ 2026-06-12 18:34:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | g.gtld-servers.net, d.gtld-servers.net, f.gtld-servers.net, h.gtld-servers.net... | - |
| leadrop.com | ns1.dns.com, ns2.dns.com | 6 records |
✅ Authoritative Response
Server:154.23.191.128
NS records: ns1.dns.com, ns2.dns.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for leadrop.com (unsigned zone)
⏱️ Timing
Total: 591ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 23.224.40.221 |
| NS | 2 | ns1.dns.com, ns2.dns.com |
| SOA | 1 | ns1.dns.com admin.dns.com |
📌 Glue Records Collected
Total: 6
Out-of-bailiwick: 6 (ns1.dns.com, ns1.dns.com, ns1.dns.com...)
Analysis
IP Addresses
leadrop.com has exactly one IP address — 23.224.40.221.
Name Servers
leadrop.com is delegated to two name servers: ns1.dns.com and ns2.dns.com.
The name server configuration of leadrop.com is shared with other domains, for instance zchk666.com, 580010.com, hfhzyy.com and two others.
leadrop.com at least partially shares name servers with other domains, for instance lostbuoy.com, hy9887.com and wlykjcdn.com.
ns1.dns.com and ns2.dns.com each resolve to three IP addresses. ns1.dns.com resolves to 154.23.191.128, 154.86.21.128 and 2001:df2:f080:2::1:1. ns2.dns.com resolves to 154.23.191.129, 154.86.21.129 and 2001:df2:f080:2::1:2.