binarymango.com - dns.ninja
binarymango.com
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=1785262562 | ||||||
Previously MX for
binarymango.com |
Same first word
binarymango.com |
Similar names
DNS History
18 records (7 active, 11 former)
●NSns-cloud-c1.googledomains.com2026-03-02 → 2026-07-28 · 3 obs
● 2026-03-02 15:21:50
● 2026-07-28 18:30:12
●NSns-cloud-c2.googledomains.com2026-03-02 → 2026-07-28 · 3 obs
● 2026-03-02 15:21:50
● 2026-07-28 18:30:12
●NSns-cloud-c3.googledomains.com2026-03-02 → 2026-07-28 · 3 obs
● 2026-03-02 15:21:50
● 2026-07-28 18:30:12
●NSns-cloud-c4.googledomains.com2026-03-02 → 2026-07-28 · 3 obs
● 2026-03-02 15:21:50
● 2026-07-28 18:30:12
○NSns.sourcedns.com2015-07-17 → 2017-03-24 · 4 obs
● 2017-03-24 08:05:06
○ 2020-01-31 12:31:48
○ 2026-07-28 18:30:12
○NSns1.bluehost.com2020-01-31 → 2020-01-31 · 4 obs
● 2020-01-31 12:31:48
○ 2026-03-02 15:21:50
○ 2026-07-28 18:30:12
○NSns1.sourcedns.com2015-07-17 → 2017-03-24 · 4 obs
● 2017-03-24 08:05:06
○ 2020-01-31 12:31:48
○ 2026-07-28 18:30:12
○NSns2.bluehost.com2020-01-31 → 2020-01-31 · 4 obs
● 2020-01-31 12:31:48
○ 2026-03-02 15:21:50
○ 2026-07-28 18:30:12
○MXalt1.aspmx.l.google.com2020-01-31 → 2020-01-31 · 4 obs
● 2020-01-31 12:31:48
○ 2026-03-02 15:21:50
○ 2026-07-28 18:30:12
○MXalt2.aspmx.l.google.com2020-01-31 → 2020-01-31 · 4 obs
● 2020-01-31 12:31:48
○ 2026-03-02 15:21:50
○ 2026-07-28 18:30:12
○MXalt3.aspmx.l.google.com2020-01-31 → 2020-01-31 · 4 obs
● 2020-01-31 12:31:48
○ 2026-03-02 15:21:50
○ 2026-07-28 18:30:12
○MXalt4.aspmx.l.google.com2020-01-31 → 2020-01-31 · 4 obs
● 2020-01-31 12:31:48
○ 2026-03-02 15:21:50
○ 2026-07-28 18:30:12
●MXaspmx.l.google.com2020-01-31 → 2026-07-28 · 3 obs
● 2020-01-31 12:31:48
● 2026-07-28 18:30:12
○MXbinarymango.com2015-07-17 → 2017-03-24 · 4 obs
● 2017-03-24 08:05:06
○ 2020-01-31 12:31:48
○ 2026-07-28 18:30:12
○A162.241.216.1762020-01-31 → 2020-01-31 · 4 obs
● 2020-01-31 12:31:48
○ 2026-03-02 15:21:50
○ 2026-07-28 18:30:12
○A72.52.129.1762015-07-17 → 2017-03-24 · 4 obs
● 2017-03-24 08:05:06
○ 2020-01-31 12:31:48
○ 2026-07-28 18:30:12
●A75.2.70.752026-03-02 → 2026-07-28 · 3 obs
● 2026-03-02 15:21:50
● 2026-07-28 18:30:12
●A99.83.190.1022026-03-02 → 2026-07-28 · 3 obs
● 2026-03-02 15:21:50
● 2026-07-28 18:30:12
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| binarymango.com | ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com | 8 records |
✅ Authoritative Response
Server:216.239.32.108
NS records: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for binarymango.com (unsigned zone)
⏱️ Timing
Total: 319ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 75.2.70.75, 99.83.190.102 |
| NS | 4 | ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com... |
| MX | 1 | aspmx.l.google.com (pri: 1) |
| TXT | 1 | proxy-ssl.webflow.com |
| SOA | 1 | ns-cloud-c1.googledomains.com cloud-dns- |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns-cloud-c1.googledomains.com, ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com...)
Analysis
IP Addresses
binarymango.com directs to two IP numbers, 75.2.70.75 and 99.83.190.102
Additional host names — grupofortaleza.com.br, higher-end.com, wepower.es and two others — share IP numbers with binarymango.com.
Name Servers
binarymango.com has four authoritative name servers: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com and ns-cloud-c4.googledomains.com.
binarymango.com partially shares its NS delegation with several other domains, including agstudio.ca, i-grow.nl, maestrowatches.com and two others.
ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com and ns-cloud-c4.googledomains.com each carry two IP addresses. ns-cloud-c1.googledomains.com has 216.239.32.108 and 2001:4860:4802:32::6c; ns-cloud-c2.googledomains.com has 216.239.34.108 and 2001:4860:4802:34::6c; ns-cloud-c3.googledomains.com has 216.239.36.108 and 2001:4860:4802:36::6c; ns-cloud-c4.googledomains.com has 216.239.38.108 and 2001:4860:4802:38::6c.
Mail Servers
binarymango.com has one mail server: aspmx.l.google.com.
binarymango.com shares the same mail server setup as other domains, including archbishopfultonjsheenmissionsocietyofcanada.org, candles.lt, tscancorp.com and two others.
binarymango.com shares mail servers — at least in part — with other domains, including weddingbellsandseashells.com, ns500768.ns500759.ns500698.ns500759.ns500698.ns500698.ns500698.ns500735.ns500708.ns500698.ns500708.ns500698.ns500619.ns500652.ns500576.trackreceptor.com, ns500671.ns500754.ns500731.ns500742.ns500671.ns500754.ns500688.ns500704.ns500678.ns500671.ns500666.ns500131.lustychickser.com and two others.
These mail servers are frequently used alongside mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 5 other.
The host aspmx.l.google.com resolves to 172.253.122.26 and 2607:f8b0:4004:c08::1b — two IP addresses.