leadsloop.com - dns.ninja
leadsloop.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 52.20.84.62🇺🇸 Amazon52.20.0.0/14 EC2 IAD prefix | ||||||
| PTR | ec2-52-20-84-62.compute-1.amazonaws.com | ||||||
| NS | ns1.atom.com ⭐ | ||||||
| A | 44.219.81.145🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix | ||||||
| PTR | ec2-44-219-81-145.compute-1.amazonaws.com | ||||||
| NS | ns2.atom.com | ||||||
| A | 50.19.240.86🇺🇸 Amazon50.19.128.0/17 EC2 IAD prefix | ||||||
| PTR | ec2-50-19-240-86.compute-1.amazonaws.com | ||||||
| SOA | ns1.atom.comhostmaster@leadsloop.com 2026-03-01 #2 | ||||||
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=1783157931 | ||||||
Previously MX for
leadsloop.com |
Same first word
leadsloop.com |
Similar names
DNS History
14 records (3 active, 11 former)
●NSns1.atom.com2026-06-22 → 2026-07-04 · 3 obs
● 2026-06-22 22:08:08
● 2026-07-04 10:07:08
○NSns1.namebrightdns.com2018-09-29 → 2018-09-29 · 4 obs
● 2018-09-29 21:45:38
○ 2026-06-22 22:08:08
○ 2026-07-04 10:07:08
○NSns1.speedydns.net2015-06-25 → 2016-04-22 · 4 obs
● 2016-04-22 21:34:50
○ 2017-02-03 00:02:04
○ 2026-07-04 10:07:08
○NSns1626.ztomy.com2017-02-03 → 2017-02-03 · 4 obs
● 2017-02-03 00:02:04
○ 2018-09-29 21:45:38
○ 2026-07-04 10:07:08
●NSns2.atom.com2026-06-22 → 2026-07-04 · 3 obs
● 2026-06-22 22:08:08
● 2026-07-04 10:07:08
○NSns2.namebrightdns.com2018-09-29 → 2018-09-29 · 4 obs
● 2018-09-29 21:45:38
○ 2026-06-22 22:08:08
○ 2026-07-04 10:07:08
○NSns2.speedydns.net2015-06-25 → 2016-04-22 · 4 obs
● 2016-04-22 21:34:50
○ 2017-02-03 00:02:04
○ 2026-07-04 10:07:08
○NSns2626.ztomy.com2017-02-03 → 2017-02-03 · 4 obs
● 2017-02-03 00:02:04
○ 2018-09-29 21:45:38
○ 2026-07-04 10:07:08
○MXleadsloop.com2015-06-25 → 2016-04-22 · 4 obs
● 2016-04-22 21:34:50
○ 2017-02-03 00:02:04
○ 2026-07-04 10:07:08
○A129.121.177.692015-06-25 → 2016-04-22 · 4 obs
● 2016-04-22 21:34:50
○ 2017-02-03 00:02:04
○ 2026-07-04 10:07:08
○A204.11.56.482017-02-03 → 2017-02-03 · 4 obs
● 2017-02-03 00:02:04
○ 2018-09-29 21:45:38
○ 2026-07-04 10:07:08
●A52.20.84.622026-06-22 → 2026-07-04 · 3 obs
● 2026-06-22 22:08:08
● 2026-07-04 10:07:08
○CNAMEhdredirect-lb3-890977680.us-east-1.elb.amazonaws.com2018-09-29 → 2018-09-29 · 3 obs
○ 2026-06-22 22:08:08
○ 2026-07-04 10:07:08
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | c.gtld-servers.net, m.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net... | - |
| leadsloop.com | ns1.atom.com, ns2.atom.com | 2 records |
✅ Authoritative Response
Server:44.219.81.145
NS records: ns1.atom.com, ns2.atom.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for leadsloop.com (unsigned zone)
⏱️ Timing
Total: 3046ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 52.20.84.62 |
| NS | 2 | ns2.atom.com, ns1.atom.com |
| SOA | 1 | ns1.atom.com hostmaster.leadsloop.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.atom.com, ns2.atom.com)
Analysis
IP Addresses
leadsloop.com has exactly one IP address — 52.20.84.62.
tourvox.com, recentbid.com, viarr.com plus two other host names have IP numbers in common with leadsloop.com.
Name Servers
leadsloop.com is delegated to two name servers: ns1.atom.com and ns2.atom.com.
The name server configuration of leadsloop.com is shared with other domains, for instance lecerf.ca, vpnpronet.com, transaction.group and two others.
leadsloop.com partially shares its name servers with domains like namenta.com and debrid.me.
ns1.atom.com resolves to 44.219.81.145. ns2.atom.com resolves to 50.19.240.86. Both host names point to a single IP number.