ns2.leadforce1.com - robtex.com
ns2.leadforce1.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 3.33.139.32🇺🇸 Amazon3.33.128.0/20 | ||||||
| PTR | aeedc42b70c898c66.awsglobalaccelerator.com | ||||||
leadforce1.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 3.33.139.32🇺🇸 Amazon3.33.128.0/20 | ||||||
| NS | ns1.markmonitor.com ⭐ | ||||||
| NS | ns2.markmonitor.com | ||||||
| NS | ns3.markmonitor.com | ||||||
| NS | ns4.markmonitor.com | ||||||
| NS | ns5.markmonitor.com | ||||||
| NS | ns6.markmonitor.com | ||||||
| NS | ns7.markmonitor.com ⚠️ Not in parent delegation | ||||||
| SOA | ns1.markmonitor.comhostmaster@markmonitor.com 2020-01-30 #2 | ||||||
Same first word
Similar names
DNS History
1 record (1 active, 0 former)
●A3.33.139.322026-03-01 → 2026-03-24 · 2 obs
● 2026-03-01 17:58:12
● 2026-03-24 10:02:46
● 2026-03-24 10:02:46
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| leadforce1.com | ns1.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com... | 12 records |
✅ Authoritative Response
Server:149.112.160.2
NS records: ns1.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com, ns6.markmonitor.com, ns2.markmonitor.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for leadforce1.com (unsigned zone)
⏱️ Timing
Total: 212ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 3.33.139.32 |
📌 Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (ns1.markmonitor.com, ns1.markmonitor.com, ns3.markmonitor.com...)
Analysis
IP Addresses
ns2.leadforce1.com points to a single IP number: 3.33.139.32.
other host names for instance greatvalue.cn, cyberbahnevents.ca, sdiley.com, zapposlife.com and bbby.com.mx share IP numbers with ns2.leadforce1.com.