binaryforest.com - dns.ninja
binaryforest.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=1786629699 | ||||||
Subdomains
bf4.binaryforest.com |
Same first word
binaryforest.com |
DNS History
11 records (9 active, 2 former)
●NSns1.digitalocean.com2015-08-04 → 2026-08-13 · 2 obs
● 2026-08-13 14:20:06
●NSns2.digitalocean.com2015-08-04 → 2026-08-13 · 2 obs
● 2026-08-13 14:20:06
●NSns3.digitalocean.com2015-08-04 → 2026-08-13 · 2 obs
● 2026-08-13 14:20:06
●MXalt1.aspmx.l.google.com2015-08-04 → 2026-08-13 · 2 obs
● 2026-08-13 14:20:06
●MXalt2.aspmx.l.google.com2015-08-04 → 2026-08-13 · 2 obs
● 2026-08-13 14:20:06
●MXaspmx.l.google.com2015-08-04 → 2026-08-13 · 2 obs
● 2026-08-13 14:20:06
●MXaspmx2.googlemail.com2015-08-04 → 2026-08-13 · 2 obs
● 2026-08-13 14:20:06
●MXaspmx3.googlemail.com2015-08-04 → 2026-08-13 · 2 obs
● 2026-08-13 14:20:06
○A139.59.202.262018-08-19 → 2018-08-19 · 4 obs
● 2018-08-19 11:41:10
○ 2026-02-22 06:36:16
○ 2026-08-13 14:20:06
●A152.53.105.292026-02-22 → 2026-08-13 · 3 obs
● 2026-02-22 06:36:16
● 2026-08-13 14:20:06
○A198.199.121.1822015-08-04 → 2017-01-08 · 4 obs
● 2017-01-08 15:43:40
○ 2018-08-19 11:41:10
○ 2026-08-13 14:20:06
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, m.gtld-servers.net, j.gtld-servers.net, e.gtld-servers.net... | - |
| binaryforest.com | ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com | 3 records |
✅ Authoritative Response
Server:172.64.49.209
NS records: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for binaryforest.com (unsigned zone)
⏱️ Timing
Total: 324ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 152.53.105.29 |
| NS | 3 | ns3.digitalocean.com, ns2.digitalocean.com... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt2.aspmx.l.google.com (pri: 5)... |
| TXT | 2 | v=spf1 a:binaryforest.com include:_spf.g, google-site-verification=CDoo32blBQ5M2aj |
| SOA | 1 | ns1.digitalocean.com hostmaster.binaryfo |
📌 Glue Records Collected
Total: 3
Out-of-bailiwick: 3 (ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com)
Analysis
Hierarchy
bf4.binaryforest.com is delegated beneath binaryforest.com.
IP Addresses
binaryforest.com resolves to just one IP address, 152.53.105.29.
Name Servers
The authoritative name servers for binaryforest.com are ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com — three in total.
There is at least partial name server overlap between binaryforest.com and other domains — standardebooks.org, mowmanagers.com, ztahlis.com and two more among them.
ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com all resolve to exactly two IP numbers apiece: ns1.digitalocean.com → 172.64.52.210 and 2606:4700:52::ac40:34d2; ns2.digitalocean.com → 172.64.53.21 and 2606:4700:5a::ac40:3515; ns3.digitalocean.com → 172.64.49.209 and 2606:4700:52::ac40:31d1.
Mail Servers
binaryforest.com has five mail servers, which are aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
There is at least a partial MX overlap between binaryforest.com and other domains, including peaklearningsolutions.com, goldilocksnurseries.co.uk, lukje.com and two others.
These mail servers tend to appear in combination with mail servers alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Host names that have two IP addresses:
aspmx2.googlemail.com directs traffic to 192.178.234.27 and 2800:3f0:4003:c14::1a.
aspmx3.googlemail.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com directs traffic to 192.178.155.27 and 2607:f8b0:4004:c09::1a.
alt1.aspmx.l.google.com directs traffic to 192.178.234.27 and 2800:3f0:4003:c14::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c14::1a IP addresses each.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 192.178.234.27 IP addresses each.