binarywall.com - dns.ninja
binarywall.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@binarywall.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=1782580040 | ||||||
Previously MX for
binarywall.com |
Same first word
binarywall.tech |
binarywall.com |
DNS History
12 records (3 active, 9 former)
●NSns1.atom.com2026-05-04 → 2026-06-27 · 3 obs
● 2026-05-04 21:53:32
● 2026-06-27 17:30:54
●NSns2.atom.com2026-05-04 → 2026-06-27 · 3 obs
● 2026-05-04 21:53:32
● 2026-06-27 17:30:54
○NSns6419.hostgator.com2015-06-16 → 2015-06-16 · 3 obs
○ 2015-10-27 13:39:16
○ 2026-06-27 17:30:54
○NSns6420.hostgator.com2015-06-16 → 2015-06-16 · 3 obs
○ 2015-10-27 13:39:16
○ 2026-06-27 17:30:54
○NSns69.domaincontrol.com2015-10-27 → 2017-05-26 · 5 obs
● 2015-10-27 13:39:16
● 2017-05-26 15:24:46
○ 2026-05-04 21:53:32
○ 2026-06-27 17:30:54
○NSns70.domaincontrol.com2015-10-27 → 2017-05-26 · 5 obs
● 2015-10-27 13:39:16
● 2017-05-26 15:24:46
○ 2026-05-04 21:53:32
○ 2026-06-27 17:30:54
○MXbinarywall.com2015-06-16 → 2015-06-16 · 3 obs
○ 2015-10-27 13:39:16
○ 2026-06-27 17:30:54
○MXmail.binarywall.com2015-10-27 → 2017-05-26 · 5 obs
● 2015-10-27 13:39:16
● 2017-05-26 15:24:46
○ 2026-05-04 21:53:32
○ 2026-06-27 17:30:54
○A107.180.38.1042015-10-27 → 2016-01-03 · 5 obs
● 2015-10-27 13:39:16
● 2016-01-03 17:43:16
○ 2016-04-12 23:15:58
○ 2026-06-27 17:30:54
○A192.254.239.2382015-06-16 → 2015-06-16 · 3 obs
○ 2015-10-27 13:39:16
○ 2026-06-27 17:30:54
○A50.63.202.472016-04-12 → 2017-05-26 · 5 obs
● 2016-04-12 23:15:58
● 2017-05-26 15:24:46
○ 2026-05-04 21:53:32
○ 2026-06-27 17:30:54
●A52.20.84.622026-05-04 → 2026-06-27 · 3 obs
● 2026-05-04 21:53:32
● 2026-06-27 17:30:54
🔍 DNS Trace
Analysis
IP Addresses
binarywall.com resolves to just one IP address, 52.20.84.62.
Two other host names, along with webmakes.com, ciqon.com and spicevault.com, also share IP numbers with binarywall.com.
Name Servers
binarywall.com is served by two delegated name servers, ns1.atom.com and ns2.atom.com.
binarywall.com shares its NS records with other domains, for example fulltorrent.com, syncname.com, pageroom.com and two others.
binarywall.com at least partially shares name servers with other domains, including elcoee.com, lawstrategy.org, lwisa.com and tahena.com.
The name servers ns1.sedoparking.com, ns2.sedoparking.com, ns3.afternic.com and two others are commonly seen in use alongside these name servers.
ns1.atom.com and ns2.atom.com each resolve to one IP number: ns1.atom.com points to 44.219.81.145 and ns2.atom.com points to 50.19.240.86.