binarysentinel.com - dns.ninja
binarysentinel.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=1784094067 | ||||||
Previously MX for
binarysentinel.com |
Subdomains
Same first word
binarysentinel.com |
DNS History
19 records (10 active, 9 former)
○NSdns130.a.register.com2016-05-04 → 2016-12-29 · 5 obs
● 2016-05-04 11:04:30
● 2016-12-29 09:10:40
○ 2026-02-18 01:46:12
○ 2026-07-15 05:50:34
○NSdns205.b.register.com2016-05-04 → 2016-12-29 · 5 obs
● 2016-05-04 11:04:30
● 2016-12-29 09:10:40
○ 2026-02-18 01:46:12
○ 2026-07-15 05:50:34
○NSdns228.c.register.com2016-05-04 → 2016-12-29 · 5 obs
● 2016-05-04 11:04:30
● 2016-12-29 09:10:40
○ 2026-02-18 01:46:12
○ 2026-07-15 05:50:34
○NSdns249.d.register.com2016-05-04 → 2016-12-29 · 5 obs
● 2016-05-04 11:04:30
● 2016-12-29 09:10:40
○ 2026-02-18 01:46:12
○ 2026-07-15 05:50:34
●NSns-1502.awsdns-59.org2026-02-18 → 2026-07-15 · 3 obs
● 2026-02-18 01:46:12
● 2026-07-15 05:50:34
●NSns-1903.awsdns-45.co.uk2026-02-18 → 2026-07-15 · 3 obs
● 2026-02-18 01:46:12
● 2026-07-15 05:50:34
●NSns-224.awsdns-28.com2026-02-18 → 2026-07-15 · 3 obs
● 2026-02-18 01:46:12
● 2026-07-15 05:50:34
●NSns-730.awsdns-27.net2026-02-18 → 2026-07-15 · 3 obs
● 2026-02-18 01:46:12
● 2026-07-15 05:50:34
○NSns1.binarysentinel.com2015-06-29 → 2015-06-29 · 3 obs
○ 2016-05-04 11:04:30
○ 2026-07-15 05:50:34
●MXalt1.aspmx.l.google.com2026-02-18 → 2026-07-15 · 3 obs
● 2026-02-18 01:46:12
● 2026-07-15 05:50:34
●MXalt2.aspmx.l.google.com2026-02-18 → 2026-07-15 · 3 obs
● 2026-02-18 01:46:12
● 2026-07-15 05:50:34
●MXalt3.aspmx.l.google.com2026-02-18 → 2026-07-15 · 3 obs
● 2026-02-18 01:46:12
● 2026-07-15 05:50:34
●MXalt4.aspmx.l.google.com2026-02-18 → 2026-07-15 · 3 obs
● 2026-02-18 01:46:12
● 2026-07-15 05:50:34
●MXaspmx.l.google.com2026-02-18 → 2026-07-15 · 3 obs
● 2026-02-18 01:46:12
● 2026-07-15 05:50:34
○MXbinarysentinel.com2015-06-29 → 2016-02-10 · 4 obs
● 2016-02-10 14:18:18
○ 2016-05-04 11:04:30
○ 2026-07-15 05:50:34
○MXp.webcom.ctmail.com2016-05-04 → 2016-12-29 · 5 obs
● 2016-05-04 11:04:30
● 2016-12-29 09:10:40
○ 2026-02-18 01:46:12
○ 2026-07-15 05:50:34
○A132.148.0.2292016-05-04 → 2016-12-29 · 5 obs
● 2016-05-04 11:04:30
● 2016-12-29 09:10:40
○ 2026-02-18 01:46:12
○ 2026-07-15 05:50:34
●A54.158.48.882026-02-18 → 2026-07-15 · 3 obs
● 2026-02-18 01:46:12
● 2026-07-15 05:50:34
○A67.223.250.582015-06-29 → 2015-11-07 · 4 obs
● 2015-11-07 18:30:02
○ 2016-05-04 11:04:30
○ 2026-07-15 05:50:34
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | k.gtld-servers.net, f.gtld-servers.net, j.gtld-servers.net, c.gtld-servers.net... | - |
| binarysentinel.com | ns-224.awsdns-28.com, ns-730.awsdns-27.net, ns-1903.awsdns-45.co.uk, ns-1502.awsdns-59.org | 2 records |
✅ Authoritative Response
Server:205.251.199.111
NS records: ns-224.awsdns-28.com, ns-730.awsdns-27.net, ns-1903.awsdns-45.co.uk, ns-1502.awsdns-59.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for binarysentinel.com (unsigned zone)
⏱️ Timing
Total: 442ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 54.158.48.88 |
| NS | 4 | ns-1502.awsdns-59.org, ns-1903.awsdns-45.co.uk... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 1 | v=spf1 include:_spf.google.com ~all |
| SOA | 1 | ns-1502.awsdns-59.org awsdns-hostmaster. |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns-224.awsdns-28.com, ns-224.awsdns-28.com)
Analysis
Hierarchy
binarysentinel.com is the parent domain of ns1.binarysentinel.com and ns2.binarysentinel.com.
IP Addresses
binarysentinel.com points to a single IP number: 54.158.48.88.
Additional host names — ns.comslash.com, ns2.binarysentinel.com, ec2-54-158-48-88.compute-1.amazonaws.com and two others — share IP numbers with binarysentinel.com.
Name Servers
binarysentinel.com has four authoritative name servers: ns-224.awsdns-28.com, ns-730.awsdns-27.net, ns-1502.awsdns-59.org and ns-1903.awsdns-45.co.uk.
binarysentinel.com partially shares its NS delegation with several other domains, including fixxpert.com, dz2flckm00k1k.cloudfront.net, nuvosight.com and two others.
ns-224.awsdns-28.com, ns-730.awsdns-27.net, ns-1502.awsdns-59.org and ns-1903.awsdns-45.co.uk each carry two IP addresses. ns-224.awsdns-28.com has 205.251.192.224 and 2600:9000:5300:e000::1; ns-730.awsdns-27.net has 205.251.194.218 and 2600:9000:5302:da00::1; ns-1502.awsdns-59.org has 205.251.197.222 and 2600:9000:5305:de00::1; ns-1903.awsdns-45.co.uk has 205.251.199.111 and 2600:9000:5307:6f00::1.
Mail Servers
binarysentinel.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
binarysentinel.com shares mail servers — at least in part — with other domains, including forestlakes-efca.org, matthewboatman.com, gridasundurvis.lv and two others.
These mail servers are frequently used alongside the mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com and aspmx2.googlemail.com, plus two others.
Host names with two IP numbers:
aspmx.l.google.com points to 142.251.167.27 and 2607:f8b0:4004:c25::1a.
alt1.aspmx.l.google.com points to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com points to 172.253.116.26 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com points to 192.178.223.27 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com points to 172.253.157.26 and 2a00:1450:400c:c23::1a.