bindash.com - dns.ninja
bindash.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 | ||||||
| MX | mx1.parking.namepros.com ⭐ | ||||||
| A | 54.237.57.21🇺🇸 Amazon54.237.0.0/16 EC2 IAD prefix | ||||||
| PTR | ns1.namepros-dns.com | ||||||
| MX | mx2.parking.namepros.com(20) | ||||||
| A | 3.233.30.191🇺🇸 Amazon3.224.0.0/12 EC2 IAD prefix | ||||||
| PTR | ns2.namepros-dns.com | ||||||
| TXT | f0095018235b8109a2bf9f65674a1784b6971ed6 | ||||||
| TXT | 981647cf-04cf-4ffe-bcef-04a413cd77ad | ||||||
| TXT | v=spf1 -all | ||||||
| TXT | 712a4ca5301147228d6ff406173e3c22 | ||||||
| SOA | ns1.atom.comhostmaster@bindash.com 2026-03-17 #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=1783159931 | ||||||
Same first word
bindash.com |
Similar names
inshabd.com |
dbsahin.com |
nbshida.com |
bishdan.ir |
banishd.com |
binshad.com |
badinhs.org |
shdiban.com |
hsabind.com |
bandish.com |
shindab.or.kr |
DNS History
16 records (5 active, 11 former)
●NSns1.atom.com2026-02-25 → 2026-07-04 · 3 obs
● 2026-02-25 12:44:50
● 2026-07-04 10:18:58
○NSns1.commonmx.com2017-02-11 → 2017-02-11 · 4 obs
● 2017-02-11 11:11:52
○ 2019-02-18 00:09:52
○ 2026-07-04 10:18:58
●NSns2.atom.com2026-02-25 → 2026-07-04 · 3 obs
● 2026-02-25 12:44:50
● 2026-07-04 10:18:58
○NSns2.commonmx.com2017-02-11 → 2017-02-11 · 4 obs
● 2017-02-11 11:11:52
○ 2019-02-18 00:09:52
○ 2026-07-04 10:18:58
○NSns41.rookdns.com2015-08-08 → 2016-03-25 · 4 obs
● 2016-03-25 01:35:04
○ 2017-02-11 11:11:52
○ 2026-07-04 10:18:58
○NSns42.rookdns.com2015-08-08 → 2016-03-25 · 4 obs
● 2016-03-25 01:35:04
○ 2017-02-11 11:11:52
○ 2026-07-04 10:18:58
○NSnsg1.namebrightdns.com2019-02-18 → 2019-02-18 · 4 obs
● 2019-02-18 00:09:52
○ 2026-02-25 12:44:50
○ 2026-07-04 10:18:58
○NSnsg2.namebrightdns.com2019-02-18 → 2019-02-18 · 4 obs
● 2019-02-18 00:09:52
○ 2026-02-25 12:44:50
○ 2026-07-04 10:18:58
○MXmail.mxproc.com2015-08-08 → 2016-03-25 · 4 obs
● 2016-03-25 01:35:04
○ 2017-02-11 11:11:52
○ 2026-07-04 10:18:58
●MXmx1.parking.namepros.com2026-02-25 → 2026-07-04 · 3 obs
● 2026-02-25 12:44:50
● 2026-07-04 10:18:58
●MXmx2.parking.namepros.com2026-02-25 → 2026-07-04 · 3 obs
● 2026-02-25 12:44:50
● 2026-07-04 10:18:58
○A141.8.224.1832015-08-08 → 2016-03-25 · 4 obs
● 2016-03-25 01:35:04
○ 2017-02-11 11:11:52
○ 2026-07-04 10:18:58
○A149.56.9.762017-02-11 → 2017-02-11 · 4 obs
● 2017-02-11 11:11:52
○ 2019-02-18 00:09:52
○ 2026-07-04 10:18:58
○A46.166.182.532017-02-11 → 2017-02-11 · 4 obs
● 2017-02-11 11:11:52
○ 2019-02-18 00:09:52
○ 2026-07-04 10:18:58
●A52.20.84.622026-02-25 → 2026-07-04 · 3 obs
● 2026-02-25 12:44:50
● 2026-07-04 10:18:58
○CNAMEhdredirect-lb5-1afb6e2973825a56.elb.us-east-1.amazonaws.com2019-02-18 → 2019-02-18 · 3 obs
○ 2026-02-25 12:44:50
○ 2026-07-04 10:18:58
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, c.gtld-servers.net, j.gtld-servers.net, e.gtld-servers.net... | - |
| bindash.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 bindash.com (unsigned zone)
⏱️ Timing
Total: 3039ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 52.20.84.62 |
| NS | 2 | ns2.atom.com, ns1.atom.com |
| MX | 2 | mx2.parking.namepros.com (pri: 20), mx1.parking.namepros.com (pri: 10) |
| TXT | 4 | 981647cf-04cf-4ffe-bcef-04a413cd77ad, 712a4ca5301147228d6ff406173e3c22... |
| SOA | 1 | ns1.atom.com hostmaster.bindash.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.atom.com, ns2.atom.com)
Analysis
IP Addresses
bindash.com directs to one IP number, which is 52.20.84.62.
Among the host names that share IP numbers with bindash.com are cartinhas.com, atluv.com, snapdual.com and two others.
Name Servers
Two name servers handle the delegation for bindash.com: ns1.atom.com and ns2.atom.com.
bindash.com has the same name server delegation as a number of other domains, such as leafboost.com, stopmalware.org, wegast.com and two more.
There is at least partial name server overlap between bindash.com and other domains — tao.in, ordine.com, appcrypt.com and two more among them.
These name servers are routinely deployed together with the name servers verification-gicpbhdwv5yn9yed2rn2dd.ns101.verify.hn.
ns1.atom.com → 44.219.81.145 and ns2.atom.com → 50.19.240.86: one IP number per host name.
Mail Servers
The MX records for bindash.com point to two mail servers: mx1.parking.namepros.com and mx2.parking.namepros.com.
bindash.com has the same mail server arrangement as a number of other domains, for example ww.tunisietelecom.com, mail.botsarmy.com, wric.jobseeker.net and two more.
mx1.parking.namepros.com → 54.237.57.21 and mx2.parking.namepros.com → 3.233.30.191: one IP number per host name.