Digital exposure report
bb.com.br
High exposure. Significant weaknesses put the brand, customers and email at risk.
Scanned: 2026-11-21 09:50 UTC
Full coverage: every applicable check was assessed.
What to do first
- 1.
Tell browsers to always use the secure version
Helps browsers use HTTPS on future visits after they have received the policy.
Who can fix it: Your web host
How to verify after the fix
curl -sIL https://bb.com.br/ | grep -i "Strict-Transport-Security"
- 2.
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://bb.com.br/ | grep -i "Content-Security-Policy"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- bb.com.br
- Website request
- GET https://bb.com.br/
- Scan time
- 2026-11-21 09:50:05 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 | 30/30 | Spoofing email from this domain is hard. |
| Encryption & certificate | 18/25 | Encryption is in place, but a gap could expose users. |
| Browser protections | 0/30 | Several browser hardening headers are missing, which removes layers of protection against script injection and framing. |
| DNS infrastructure | 15/15 | The domain's infrastructure is well hardened. |
Fix priorities
- 1.HighHSTS — enforce encryption in the browser · Hardening gap+8
- 2.HighHTTP → HTTPS redirect · Hardening gap+7
- 3.MediumClickjacking protection · Hardening gap+5
- 4.MediumCSP — protection from script injection · Hardening gap+8
- 5.LowX-Content-Type-Options · Hardening gap+4
- 6.LowReferrer-Policy · Hardening gap+3
- 7.LowPermissions-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. 2 of the 10 allowed DNS lookups.
v=spf1 ip4:170.66.0.0/16 include:spf.protection.outlook.com include:spf.tmes.trendmicro.com -all
$ dig +short TXT bb.com.br
DMARC — anti-spoofing policy
Passed · Severity: OK · 15/15Forged email in the company's name is blocked by mail servers.
Policy p=reject.
v=DMARC1; p=reject; rua=mailto:dmarc@bb.com.br, mailto:bancodobrasil@dmarcrua.tmes.trendmicro.com; ruf=mailto:dmarc@bb.com.br; aspf=s; pct=100
$ dig +short TXT _dmarc.bb.com.br
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: default. Confirm signing with dkim=pass in a sent message's Authentication-Results.
default._domainkey: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDRhAUPjdT8uF3SD4rgOXpG1xB4vrGDyp/n…
$ dig +short TXT default._domainkey.bb.com.br
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
1 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
1 bancodobrasil.in.tmes.trendmicro.com
$ dig +short MX bb.com.br
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://bb.com.br/ returned HTTP 200 (final URL: https://bb.com.br/). Client-side certificate validation passed.
HTTP 200 Final URL: https://bb.com.br/
$ curl -sIL https://bb.com.br/
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://bb.com.br/ returned HTTP 403 without redirecting to https://.
HTTP 403 Location: (none)
$ curl -sI http://bb.com.br/ | 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 bb.com.br www.bb.com.br;
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. Latest issuance in CT logs: DigiCert, expiring 2027-02-12 (83 days). CT shows issued certificates, not necessarily the one served — confirm dates with the verify command.
Live TLS handshake: certificate accepted CT logs (context only, not scored): Issuer: DigiCert Valid from: 2026-07-29 Valid until: 2027-02-12 Names: bb.com.br, www.bancobrasil.com.br, www.bancodobrasil.com.br, www.bb.com.br Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect bb.com.br:443 -servername bb.com.br 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Failed · Severity: High · Hardening gap · 0/8Browsers aren't told to always use an encrypted connection, enabling interception attacks on public networks.
No Strict-Transport-Security header. Users are exposed to SSL stripping on the first request.
Strict-Transport-Security: (missing)
$ curl -sIL https://bb.com.br/ | grep -i "Strict-Transport-Security"
- Start with a short max-age (300 seconds) and make sure every subdomain works over HTTPS.
- Gradually raise it to 31536000 (one year) and add includeSubDomains.
- Consider preload only once the policy is stable — removal from the preload list is slow.
/* Strict-Transport-Security: max-age=31536000; includeSubDomains
Safety: This change is made in your server/CDN settings. Test on staging before production. HSTS is cached in the visitor's browser — a long max-age on a site without working HTTPS will block access.
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://bb.com.br/ | 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
Failed · Severity: Medium · Hardening gap · 0/5Missing X-Frame-Options / frame-ancestors: this removes one layer of protection against clickjacking.
No valid X-Frame-Options and no frame-ancestors in the CSP.
X-Frame-Options: (missing)
$ curl -sIL https://bb.com.br/ | grep -i "X-Frame-Options"
- Add X-Frame-Options: SAMEORIGIN (or DENY if the site is never embedded anywhere).
- Also set frame-ancestors in the CSP — the modern alternative.
/* X-Frame-Options: SAMEORIGIN
Safety: This change is made in your server/CDN settings. Test on staging before production. If partners embed the site in an iframe, add them to frame-ancestors instead of using DENY.
X-Content-Type-Options
Failed · Severity: Low · Hardening gap · 0/4The browser may interpret files as code unintentionally.
Missing X-Content-Type-Options: nosniff header (MIME sniffing).
X-Content-Type-Options: (missing)
$ curl -sIL https://bb.com.br/ | grep -i "X-Content-Type-Options"
- Add X-Content-Type-Options: nosniff to every response.
/* X-Content-Type-Options: nosniff
Safety: This change is made in your server/CDN settings. Test on staging before production.
Referrer-Policy
Failed · Severity: Low · Hardening gap · 0/3Internal URLs (including parameters) may leak to external sites.
Referrer-Policy is missing; the browser will use its default.
Referrer-Policy: (missing)
$ curl -sIL https://bb.com.br/ | 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
Needs attention · Severity: Low · Hardening gap · 0/2Access to sensitive features like the camera and location isn't restricted.
Missing Permissions-Policy header.
Permissions-Policy: (missing)
$ curl -sIL https://bb.com.br/ | grep -i "Permissions-Policy"
- Disable browser features the site doesn't need (camera, microphone, geolocation).
/* Permissions-Policy: camera=(), microphone=(), geolocation=()
Safety: This change is made in your server/CDN settings. Test on staging before production. Don't disable a feature the site actually uses.
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: (missing)
$ curl -sIL https://bb.com.br/ | grep -iE "^(server|x-powered-by)"
DNSSEC — signed DNS records
Passed · Severity: OK · 7/7The domain's records are digitally signed and hard to forge.
An AD (Authenticated Data) flag was returned by a validating resolver.
AD = true
$ dig +dnssec bb.com.br | grep -E "flags:.* ad"
CAA — who may issue certificates
Passed · Severity: OK · 5/5Only authorized certificate authorities can issue certificates for the domain.
CAA records: 0 iodef "mailto:ditec.redes@bb.com.br" | 0 issue "certigna.com" | 0 issue "certisign.com.br" | 0 issue "comodoca.com" | 0 issue "digicert.com" | 0 issue "globalsign.com" | 0 issue "mastercard.com" | 0 issue "sectigo.com" | 0 issue "soluti.com.br" | 0 issue "visa.com" | 0 issuewild "certisign.com.br" | 0 issuewild "comodoca.com" | 0 issuewild "digicert.com" | 0 issuewild "globalsign.com" | 0 issuewild "sectigo.com" | 0 issuewild "soluti.com.br"
0 iodef "mailto:ditec.redes@bb.com.br" 0 issue "certigna.com" 0 issue "certisign.com.br" 0 issue "comodoca.com" 0 issue "digicert.com" 0 issue "globalsign.com" 0 issue "mastercard.com" 0 issue "sectigo.com" 0 issue "soluti.com.br" 0 issue "visa.com" 0 issuewild "certisign.com.br" 0 issuewild "comodoca.com" 0 issuewild "digicert.com" 0 issuewild "globalsign.com" 0 issuewild "sectigo.com" 0 issuewild "soluti.com.br"
$ dig +short CAA bb.com.br
DNS server redundancy
Passed · Severity: OK · 3/3The domain is served by several DNS servers, so one server failing won't take it down.
4 NS servers.
dns1.bb.com.br dns2.bb.com.br dns3.bb.com.br dns4.bb.com.br
$ dig +short NS bb.com.br
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.04 observed gaps
- NIS2 / vendor due diligence1 observed gaps
- SOC 2 / ISO 27001 baseline4 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 | bb.com.br | 104.18.28.245 | 104.18.29.245 |
| AAAA | bb.com.br | — |
| MX | bb.com.br | 1 bancodobrasil.in.tmes.trendmicro.com |
| NS | bb.com.br | dns1.bb.com.br | dns2.bb.com.br | dns3.bb.com.br | dns4.bb.com.br |
| TXT | bb.com.br | MS=ms78705448 | 00DDn00000C0bb2=1TBNp00000002GL | ef9da41523134534be97127b71bb2856 | apple-domain-verification=bshZ6ehpobzOBAtd | apple-domain-verification=hgAwaITZz7sLYIeR | ibmid=bb9d1049-0b9d-4cec-8ace-a8e9cd8a161f | zscaler-verification-182215184-6242026-iCCDY | facebook-domain-verification=n63bla7q15gijiuxzfn9acg565ppd3 | google-site-verification=0bLzI2YSV1Pc9_v5NkO7vP8qN7GwLRHrsINXqsucLqI | google-site-verification=Wmr6gjjU9yavBiz9uTfI4qf1g8IwZ6w3z02a1_Bw6lA | google-site-verification=ajwAaM6pafcYld-zOnO2NvMfj3AoYd49LRC8tJcf8x4 | google-site-verification=ngM_IDru8SDQmU9Q69frKkSPbfvl537M3vabK0qFDT4 | FCW2MOVE9HrYWYrS32kV+4Jm9FaXfNRy4tkvnmmUgT4CVULXbwNaeu5RvDuqPqwKMNegokfo+dIjGfRgAgtIsw== | Dynatrace-site-verification=9e2f01f2-1a16-45fc-b4c0-581877fe6b3e__o1h9mt219frnfialqcriek79v6 | adobe-idp-site-verification=920c77122fba327f2729d822f4b845a64afb6a9271fd57e2d8afa82c4f850899 | cisco-ci-domain-verification=7828dbaa1b5d18ce8d7db7b24a4e0a90dc491b9cd015fba1d79f27ead64379b8 | atlassian-domain-verification=8jwv6hhHK3rzE7WzZaF6j8SoKzdUOzJgKJmtvSnZabyrDqS2WUEk/IiyHxhBRFKs | v=spf1 ip4:170.66.0.0/16 include:spf.protection.outlook.com include:spf.tmes.trendmicro.com -all | trend-micro-v1-domain-verification.9762af746cf1fa4f78619d281b0ecc2b=97ee2e55-cf50-4365-ad9d-90f3d0214ffa |
| TXT | _dmarc.bb.com.br | v=DMARC1; p=reject; rua=mailto:dmarc@bb.com.br, mailto:bancodobrasil@dmarcrua.tmes.trendmicro.com; ruf=mailto:dmarc@bb.com.br; aspf=s; pct=100 |
| CAA | bb.com.br | 0 iodef "mailto:ditec.redes@bb.com.br" | 0 issue "certigna.com" | 0 issue "certisign.com.br" | 0 issue "comodoca.com" | 0 issue "digicert.com" | 0 issue "globalsign.com" | 0 issue "mastercard.com" | 0 issue "sectigo.com" | 0 issue "soluti.com.br" | 0 issue "visa.com" | 0 issuewild "certisign.com.br" | 0 issuewild "comodoca.com" | 0 issuewild "digicert.com" | 0 issuewild "globalsign.com" | 0 issuewild "sectigo.com" | 0 issuewild "soluti.com.br" |
| DS | bb.com.br | 23119 8 2 8f853ec13b608868b620afc78867552a043fb9c44faefb4334ff712796994630 | 50137 8 2 8816f214a09a2104aa270a740cf041f0adcd1355a21fbc4bc5c4b56427ce2f1a |