leadreply.com - dns.ninja
leadreply.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 | ||||||
| TXT | f0095018235b8109a2bf9f65674a1784b6971ed6 | ||||||
| SOA | ns1.atom.comhostmaster@leadreply.com 2025-11-10 #1 | ||||||
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=1790147564 | ||||||
Same first word
leadreply.org |
leadreply.au |
leadreply.app |
leadreply.com |
leadreply.co.uk |
leadreply.net |
leadreply.xyz |
leadreply.ca |
leadreply.io |
leadreply.de |
leadreply.ai |
leadreply.com.au |
leadreply.help |
Similar names
Previous names
Next names
DNS History
7 records (3 active, 4 former)
○NSns01.cashparking.com2015-07-07 → 2017-04-18 · 4 obs
● 2017-04-18 16:13:16
○ 2026-09-04 08:27:16
○ 2026-09-23 07:22:30
●NSns1.atom.com2026-09-04 → 2026-09-23 · 3 obs
● 2026-09-04 08:27:16
● 2026-09-23 07:22:30
●NSns2.atom.com2026-09-04 → 2026-09-23 · 3 obs
● 2026-09-04 08:27:16
● 2026-09-23 07:22:30
○MXmailstore1.secureserver.net2015-07-07 → 2017-04-18 · 4 obs
● 2017-04-18 16:13:16
○ 2026-09-04 08:27:16
○ 2026-09-23 07:22:30
○MXsmtp.secureserver.net2015-07-07 → 2017-04-18 · 4 obs
● 2017-04-18 16:13:16
○ 2026-09-04 08:27:16
○ 2026-09-23 07:22:30
○A184.168.221.962015-07-07 → 2017-04-18 · 4 obs
● 2017-04-18 16:13:16
○ 2026-09-04 08:27:16
○ 2026-09-23 07:22:30
●A52.20.84.622026-09-04 → 2026-09-23 · 3 obs
● 2026-09-04 08:27:16
● 2026-09-23 07:22:30
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| leadreply.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 leadreply.com (unsigned zone)
⏱️ Timing
Total: 3182ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 52.20.84.62 |
| NS | 2 | ns2.atom.com, ns1.atom.com |
| TXT | 1 | f0095018235b8109a2bf9f65674a1784b6971ed6 |
| SOA | 1 | ns1.atom.com hostmaster.leadreply.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.atom.com, ns2.atom.com)
Analysis
IP Addresses
leadreply.com resolves to just one IP address, 52.20.84.62.
Two other host names, along with solarfederation.com, zalabo.com and futuregrocer.com, also share IP numbers with leadreply.com.
Name Servers
Two name servers handle the delegation for leadreply.com: ns1.atom.com and ns2.atom.com.
leadreply.com shares its NS records with other domains, for example techbeats.store, viatem.com, dopesecurity.com and two others.
The name servers for leadreply.com are at least partly shared with other domains such as parisengineer.com, mdx4.com, transferprocess.com and megaluxury.com.
It is common to see these name servers used together with name servers ns1.afternic.com and ns2.afternic.com.
ns1.atom.com directs to 44.219.81.145 and ns2.atom.com directs to 50.19.240.86; each host name points to exactly one IP number.