Digital exposure report
binah.ai
Moderate exposure. There are gaps an attacker could exploit — fix them soon.
Scanned: 2026-11-19 02:55 UTC
Full coverage: every applicable check was assessed.
What to do first
- 1.
Limit what scripts your pages are allowed to run
This adds one layer of protection against injected scripts.
Who can fix it: Your website developer or web host
How to verify after the fix
curl -sIL https://binah.ai/ | grep -i "Content-Security-Policy"
- 2.
Send visitors to the secure version of your site
Visitors who type your address without https may stay on an unprotected connection.
Who can fix it: Your web host
How to verify after the fix
curl -sI http://binah.ai/ | grep -iE "^(HTTP|location)"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- binah.ai
- Website request
- GET https://binah.ai/ → https://www.binah.ai/
- Scan time
- 2026-11-19 02:55:42 UTC
- Grading method
- Version 2How grading works
- Unverified or excluded checks
- None. Every applicable check was assessed.
This is a snapshot of the public configuration checks listed in this report. It does not verify the site's owner, business legitimacy, application security, or absence of vulnerabilities. It is not a security certification.
Score by category
| Email security | 28/30 | Spoofing email from this domain is hard. |
| Encryption & certificate | 18/25 | Encryption is in place, but a gap could expose users. |
| Browser protections | 20/30 | Some browser protections are missing. |
| DNS infrastructure | 8/15 | The domain's infrastructure works, but recommended hardening is missing. |
Fix priorities
- 1.HighHTTP → HTTPS redirect · Hardening gap+7
- 2.MediumDNSSEC — signed DNS records · Hardening gap+7
- 3.MediumCSP — protection from script injection · Hardening gap+8
- 4.LowReferrer-Policy · Hardening gap+2
Findings
SPF — who may send mail for the domain
Passed · Severity: OK · 10/10An authorized sender list is defined and mail from other servers is rejected.
Valid SPF record with -all. 5 of the 10 allowed DNS lookups.
v=spf1 mx include:_spf.google.com include:sendgrid.net include:_spf.salesforce.com include:spf.brevo.com -all
$ dig +short TXT binah.ai
DMARC — anti-spoofing policy
Passed · Severity: OK · 13/15Forged email in the company's name is sent to the spam folder.
Policy p=quarantine. p=quarantine — consider moving to p=reject.
v=DMARC1; p=quarantine; rua=mailto:ec4e5f1e45ad068@rep.dmarcanalyzer.com,mailto:dmarc_agg@vali.email; ruf=mailto:ec4e5f1e45ad068@for.dmarcanalyzer.com; fo=1;
$ dig +short TXT _dmarc.binah.ai
DKIM — digital signature on email
Passed · Severity: OK · 5/5A DKIM public key is published. On its own this doesn't prove outgoing mail is signed or aligned with your From domain.
DKIM public key found for selector: google, s1, s2. Confirm signing with dkim=pass in a sent message's Authentication-Results.
google._domainkey: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAh+b0LfhOl0UvcIvlV1Fl1h+pZw4/… s1._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAu45pQCoW/uzzuGPvlRfqAx5IMWNNtIkU… s2._domainkey: k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCxf01CDzEZKRLNFud0krFbMg/jeDx72IhssjWP…
$ dig +short TXT google._domainkey.binah.ai
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
5 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
1 aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com
$ dig +short MX binah.ai
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://binah.ai/ returned HTTP 200 (final URL: https://www.binah.ai/). Client-side certificate validation passed.
HTTP 200 Final URL: https://www.binah.ai/
$ curl -sIL https://binah.ai/
HTTP → HTTPS redirect
Failed · Severity: High · Hardening gap · 0/7The site is also reachable over an unencrypted connection, so data may travel in plain text on public networks.
http://binah.ai/ returned HTTP 301 without redirecting to https:// (Location: http://www.binah.ai/).
HTTP 301 Location: http://www.binah.ai/
$ curl -sI http://binah.ai/ | grep -iE "^(HTTP|location)"
- Set up a permanent (301) redirect from every HTTP request to HTTPS on the server or CDN.
- Then add an HSTS header.
server {
listen 80;
server_name binah.ai www.binah.ai;
return 301 https://$host$request_uri;
}Safety: This change is made on your server. Make sure HTTPS works first, otherwise the site won't load.
SSL/TLS certificate validity
Passed · Severity: OK · 8/8The certificate was accepted by a validating TLS client at scan time.
Live TLS handshake succeeded. No matching certificate details were available from CT logs; run the verify command to see the served certificate's dates.
Live TLS handshake: certificate accepted The CT log service was unavailable at the time of the check Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect binah.ai:443 -servername binah.ai 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Passed · Severity: OK · 8/8Browsers are told to always use an encrypted connection to the site.
max-age=31536000 (365 days), includeSubDomains, preload. ≥ 180 days recommended.
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
$ curl -sIL https://binah.ai/ | grep -i "Strict-Transport-Security"
CSP — protection from script injection
Failed · Severity: Medium · Hardening gap · 0/8Missing Content-Security-Policy header: this removes one layer of protection against script injection.
No Content-Security-Policy header found.
Content-Security-Policy: (missing)
$ curl -sIL https://binah.ai/ | grep -i "Content-Security-Policy"
- First publish Content-Security-Policy-Report-Only — it blocks nothing, it only reports.
- Collect violations for a week or two and tune the policy to your legitimate sources.
- Switch to the Content-Security-Policy header and replace 'unsafe-inline' with a nonce or hash.
/* Content-Security-Policy-Report-Only: default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'self'
Safety: This change is made in your server/CDN settings. Test on staging before production. An overly strict CSP will break scripts — that's why you start in Report-Only mode.
Clickjacking protection
Passed · Severity: OK · 5/5The site can't be embedded by foreign sites.
X-Frame-Options: SAMEORIGIN
X-Frame-Options: SAMEORIGIN
$ curl -sIL https://binah.ai/ | grep -i "X-Frame-Options"
X-Content-Type-Options
Passed · Severity: OK · 4/4The browser won't guess file types in a way that could execute code.
nosniff is set.
X-Content-Type-Options: nosniff
$ curl -sIL https://binah.ai/ | grep -i "X-Content-Type-Options"
Referrer-Policy
Needs attention · Severity: Low · Hardening gap · 1/3The policy sends full URLs to external sites.
Referrer-Policy: no-referrer-when-downgrade — sends the full URL including path and query.
Referrer-Policy: no-referrer-when-downgrade
$ curl -sIL https://binah.ai/ | grep -i "Referrer-Policy"
- Set Referrer-Policy: strict-origin-when-cross-origin.
/* Referrer-Policy: strict-origin-when-cross-origin
Safety: This change is made in your server/CDN settings. Test on staging before production.
Permissions-Policy
Passed · Severity: OK · 2/2The site restricts access to sensitive browser features.
Permissions-Policy: autoplay=*, camera=*, cross-origin-isolated=*, display-capture=*, document-domain=*, encrypted-media=*, execution-while-not-rendered=*, execution-while-out-of-v
Permissions-Policy: autoplay=*, camera=*, cross-origin-isolated=*, display-capture=*, document-domain=*, encrypted-media=*, execution-while-not-rendered=*, execution-while-out-of-viewport=*, fullscreen=*, geolocation=*, keyboard-map=*, microphone=*, navigation-override=*, payment=*, sync-xhr=*
$ curl -sIL https://binah.ai/ | grep -i "Permissions-Policy"
Software version disclosure
Passed · Severity: OK · unscoredThe server doesn't disclose software versions.
No version numbers found in the Server / X-Powered-By headers.
server: cloudflare x-powered-by: WP Engine
$ curl -sIL https://binah.ai/ | grep -iE "^(server|x-powered-by)"
DNSSEC — signed DNS records
Needs attention · Severity: Medium · Hardening gap · 0/7The domain's records aren't signed, so in some scenarios users could be redirected to a forged server.
No DS record is published at the parent zone, so there's no DNSSEC chain of trust for this zone.
AD = false DS binah.ai: NODATA
$ dig +short DS binah.ai
- Enable DNSSEC at your DNS provider (one click at most providers).
- Copy the DS record your provider generates to your domain registrar.
- Wait for propagation and verify with DNSViz.
dig +dnssec binah.ai SOA delv binah.ai
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. A wrong DS record at the registrar will make the domain stop resolving — copy it exactly from the provider.
CAA — who may issue certificates
Passed · Severity: OK · 5/5Only authorized certificate authorities can issue certificates for the domain.
CAA records: 0 issue "amazon.com" | 0 issue "digicert.com" | 0 issue "letsencrypt.org"
0 issue "amazon.com" 0 issue "digicert.com" 0 issue "letsencrypt.org"
$ dig +short CAA binah.ai
DNS server redundancy
Passed · Severity: OK · 3/3The domain is served by several DNS servers, so one server failing won't take it down.
2 NS servers.
justin.ns.cloudflare.com veda.ns.cloudflare.com
$ dig +short NS binah.ai
Indicative alignment
Best-practice mapping of public findings to common frameworks. Passive scanning tests public configuration only; it doesn't prove compliance or a violation.
- Google & Yahoo sender rulesNo gaps observed
- PCI DSS v4.02 observed gaps
- NIS2 / vendor due diligence1 observed gaps
- SOC 2 / ISO 27001 baseline1 observed gaps
Indicative alignment only, based on public configuration. It doesn't establish whether a framework applies to you, and it isn't legal advice, an audit or a certification.
Public DNS records
| A | binah.ai | 141.193.213.11 | 141.193.213.10 |
| AAAA | binah.ai | — |
| MX | binah.ai | 1 aspmx.l.google.com | 10 alt3.aspmx.l.google.com | 10 alt4.aspmx.l.google.com | 5 alt1.aspmx.l.google.com | 5 alt2.aspmx.l.google.com |
| NS | binah.ai | justin.ns.cloudflare.com | veda.ns.cloudflare.com |
| TXT | binah.ai | MS=ms61724253 | ZOOM_verify_uTGSVLjBSlej-M3h9Pofew | brevo-code:d18de9843fbc524da01fa44d209293c1 | cursor-domain-verification-pcxqeb=8Uza864wJ6rHM4QLcihjJPkp7 | facebook-domain-verification=xooav5t8pv7h5i042q241eibfpnhh3 | google-site-verification=RGEbJ-4Ft-Zks931Yr079YTfd9sZwPkIY4CXG8y-HuI | google-site-verification=ZkuxNlI1UE3dAYp_5TjxkFXmgwe_GdF7APLj-2N8-Lw | google-site-verification=fCh_AMLbBLpPPR14lleet-ZedVb2dsQbA6q8t08WLR8 | v=spf1 mx include:_spf.google.com include:sendgrid.net include:_spf.salesforce.com include:spf.brevo.com -all |
| TXT | _dmarc.binah.ai | v=DMARC1; p=quarantine; rua=mailto:ec4e5f1e45ad068@rep.dmarcanalyzer.com,mailto:dmarc_agg@vali.email; ruf=mailto:ec4e5f1e45ad068@for.dmarcanalyzer.com; fo=1; |
| CAA | binah.ai | 0 issue "amazon.com" | 0 issue "digicert.com" | 0 issue "letsencrypt.org" |
| DS | binah.ai | — |