Back to results

Digital exposure report

bancodobrasil.com.br

Low exposure. The domain is well protected in most areas checked.

Scanned: 2026-11-19 03:31 UTC

Full coverage: every applicable check was assessed.

A
100/100

What to do first

Nothing urgent. Your basics look fine.

A starting point, not a security guarantee.

What this grade means

Tested hostname
bancodobrasil.com.br
Website request
GET https://bancodobrasil.com.br/(no HTTPS response)
Scan time
2026-11-19 03:31:39 UTC
Grading method
Version 2How grading works
Unverified or excluded checks
  • HTTPS available · Not applicable
  • HTTP → HTTPS redirect · Not applicable
  • SSL/TLS certificate validity · Not applicable
  • HSTS — enforce encryption in the browser · Not applicable
  • CSP — protection from script injection · Not applicable
  • Clickjacking protection · Not applicable
  • X-Content-Type-Options · Not applicable
  • Referrer-Policy · Not applicable
  • Permissions-Policy · Not applicable

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 security30/30Spoofing email from this domain is hard.
Encryption & certificate—Not applicable to this domain.
Browser protections—Not applicable to this domain.
DNS infrastructure15/15The domain's infrastructure is well hardened.

Findings

SPF — who may send mail for the domain

Passed · Severity: OK · 10/10

An authorized sender list is defined and mail from other servers is rejected.

Valid SPF record with -all. 2 of the 10 allowed DNS lookups.

Source data: DNS TXT bancodobrasil.com.br
v=spf1 ip4:170.66.0.0/16 include:spf.protection.outlook.com include:spf.tmes.trendmicro.com -all
$ dig +short TXT bancodobrasil.com.br
Documentation: RFC 7208 — SPF (https://www.rfc-editor.org/rfc/rfc7208) · M3AAWG — Email Authentication Best Practices (https://www.m3aawg.org/sites/default/files/m3aawg-email-authentication-recommended-best-practices-09-2020.pdf)

DMARC — anti-spoofing policy

Passed · Severity: OK · 15/15

Forged email in the company's name is blocked by mail servers.

Policy p=reject.

Source data: DNS TXT _dmarc.bancodobrasil.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
$ dig +short TXT _dmarc.bancodobrasil.com.br
Documentation: RFC 7489 — DMARC (https://www.rfc-editor.org/rfc/rfc7489) · dmarc.org — FAQ (https://dmarc.org/resources/frequently-asked-questions/)

DKIM — digital signature on email

Passed · Severity: OK · 5/5

A 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.

Source data: DNS TXT <selector>._domainkey.bancodobrasil.com.br
default._domainkey: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC5uvCxkil8xwYOM97pdlYN8u6l4ghRi2Zz…
$ dig +short TXT default._domainkey.bancodobrasil.com.br
Documentation: RFC 6376 — DKIM (https://www.rfc-editor.org/rfc/rfc6376) · M3AAWG — Email Authentication Best Practices (https://www.m3aawg.org/sites/default/files/m3aawg-email-authentication-recommended-best-practices-09-2020.pdf)

MX — inbound mail routing

Passed · Severity: OK · unscored

Mail 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.

Source data: DNS MX bancodobrasil.com.br
1 bancodobrasil.in.tmes.trendmicro.com
$ dig +short MX bancodobrasil.com.br
Documentation: RFC 7505 — Null MX (https://www.rfc-editor.org/rfc/rfc7505) · RFC 5321 §5.1 — Locating the target host (https://www.rfc-editor.org/rfc/rfc5321#section-5.1)

HTTPS available

Not applicable · Severity: OK · Not applicable

The domain has no web address (no A/AAAA records), so website checks don't apply.

The domain has no web address (no A/AAAA records), so website checks don't apply.

Source data: HTTPS GET https://bancodobrasil.com.br/
No A/AAAA record for the domain
$ curl -svI https://bancodobrasil.com.br/ 2>&1 | grep -E "SSL|HTTP|expire"
Documentation: OWASP — Transport Layer Security Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Transport_Layer_Security_Cheat_Sheet.html) · Mozilla — Server Side TLS (https://wiki.mozilla.org/Security/Server_Side_TLS)

HTTP → HTTPS redirect

Not applicable · Severity: OK · Not applicable

The domain has no web address (no A/AAAA records), so website checks don't apply.

The domain has no web address (no A/AAAA records), so website checks don't apply.

Source data: HTTP GET http://bancodobrasil.com.br/ (redirects not followed)
Not checked
$ curl -sI http://bancodobrasil.com.br/ | grep -iE "^(HTTP|location)"
Documentation: OWASP — Transport Layer Security Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Transport_Layer_Security_Cheat_Sheet.html) · RFC 6797 — HSTS (https://www.rfc-editor.org/rfc/rfc6797)

SSL/TLS certificate validity

Not applicable · Severity: OK · Not applicable

The domain has no web address (no A/AAAA records), so website checks don't apply.

The domain has no web address (no A/AAAA records), so website checks don't apply.

Source data: Certificate Transparency logs (certspotter) for bancodobrasil.com.br
No valid certificate found in CT logs
Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect bancodobrasil.com.br:443 -servername bancodobrasil.com.br 2>/dev/null | openssl x509 -noout -issuer -dates
Documentation: Certificate Transparency (https://certificate.transparency.dev/) · Let's Encrypt — Docs (https://letsencrypt.org/docs/) · Mozilla — Server Side TLS (https://wiki.mozilla.org/Security/Server_Side_TLS)

HSTS — enforce encryption in the browser

Not applicable · Severity: OK · Not applicable

Not applicable — the domain has no web address.

Not applicable — the domain has no web address.

Source data: Response headers from https://bancodobrasil.com.br/
No HTTPS response received
$ curl -sIL https://bancodobrasil.com.br/
Documentation: MDN — Strict-Transport-Security (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Strict-Transport-Security) · RFC 6797 — HSTS (https://www.rfc-editor.org/rfc/rfc6797) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

CSP — protection from script injection

Not applicable · Severity: OK · Not applicable

Not applicable — the domain has no web address.

Not applicable — the domain has no web address.

Source data: Response headers from https://bancodobrasil.com.br/
No HTTPS response received
$ curl -sIL https://bancodobrasil.com.br/
Documentation: MDN — Content Security Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP) · OWASP — CSP Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Content_Security_Policy_Cheat_Sheet.html)

Clickjacking protection

Not applicable · Severity: OK · Not applicable

Not applicable — the domain has no web address.

Not applicable — the domain has no web address.

Source data: Response headers from https://bancodobrasil.com.br/
No HTTPS response received
$ curl -sIL https://bancodobrasil.com.br/
Documentation: MDN — X-Frame-Options (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Frame-Options) · OWASP — Clickjacking Defense (https://cheatsheetseries.owasp.org/cheatsheets/Clickjacking_Defense_Cheat_Sheet.html)

X-Content-Type-Options

Not applicable · Severity: OK · Not applicable

Not applicable — the domain has no web address.

Not applicable — the domain has no web address.

Source data: Response headers from https://bancodobrasil.com.br/
No HTTPS response received
$ curl -sIL https://bancodobrasil.com.br/
Documentation: MDN — X-Content-Type-Options (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Content-Type-Options) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

Referrer-Policy

Not applicable · Severity: OK · Not applicable

Not applicable — the domain has no web address.

Not applicable — the domain has no web address.

Source data: Response headers from https://bancodobrasil.com.br/
No HTTPS response received
$ curl -sIL https://bancodobrasil.com.br/
Documentation: MDN — Referrer-Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Referrer-Policy) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

Permissions-Policy

Not applicable · Severity: OK · Not applicable

Not applicable — the domain has no web address.

Not applicable — the domain has no web address.

Source data: Response headers from https://bancodobrasil.com.br/
No HTTPS response received
$ curl -sIL https://bancodobrasil.com.br/
Documentation: MDN — Permissions-Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Permissions-Policy) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

DNSSEC — signed DNS records

Passed · Severity: OK · 7/7

The domain's records are digitally signed and hard to forge.

An AD (Authenticated Data) flag was returned by a validating resolver.

Source data: DNS-over-HTTPS (Cloudflare / Google): AD flag and DS record at the parent
AD = true
$ dig +dnssec bancodobrasil.com.br | grep -E "flags:.* ad"
Documentation: RFC 4033 — DNSSEC (https://www.rfc-editor.org/rfc/rfc4033) · ICANN — DNSSEC: what and why (https://www.icann.org/resources/pages/dnssec-what-is-it-why-important-2019-03-05-en)

CAA — who may issue certificates

Passed · Severity: OK · 5/5

Only 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"

Source data: DNS CAA bancodobrasil.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 bancodobrasil.com.br
Documentation: RFC 8659 — CAA (https://www.rfc-editor.org/rfc/rfc8659)

DNS server redundancy

Passed · Severity: OK · 3/3

The domain is served by several DNS servers, so one server failing won't take it down.

4 NS servers.

Source data: DNS NS bancodobrasil.com.br
dns1.bb.com.br
dns2.bb.com.br
dns3.bb.com.br
dns4.bb.com.br
$ dig +short NS bancodobrasil.com.br
Documentation: RFC 2182 — Secondary DNS server operation (https://www.rfc-editor.org/rfc/rfc2182)

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.0Not applicable
  • NIS2 / vendor due diligenceNo gaps observed
  • SOC 2 / ISO 27001 baselineNo gaps observed

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

Abancodobrasil.com.br—
AAAAbancodobrasil.com.br—
MXbancodobrasil.com.br1 bancodobrasil.in.tmes.trendmicro.com
NSbancodobrasil.com.brdns1.bb.com.br | dns2.bb.com.br | dns3.bb.com.br | dns4.bb.com.br
TXTbancodobrasil.com.brMS=ms70100408 | google-site-verification=dC39ZidAqaaYueiagyVqB7B5STKN8X83CBGOtOFM24g | J0rMGalvbmM5V46F9Ch7Cz9Mnji43XhWyn9PCSELODgG0qL6dFXa1olMKEDnecsqmbK9KDt/rocHRXbEh3vI/g== | v=spf1 ip4:170.66.0.0/16 include:spf.protection.outlook.com include:spf.tmes.trendmicro.com -all | trend-micro-v1-domain-verification.fd31304899a63af41830d0221e50ebe6=5ab7e79c-c809-4fb9-9a13-b3ac4e086dd4
TXT_dmarc.bancodobrasil.com.brv=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
CAAbancodobrasil.com.br0 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"
DSbancodobrasil.com.br59054 8 2 40258f98eb127d676eb32118fd24af054bb2d951d66207d7a7c95b83bec1d170 | 62962 8 2 870fa5046e4c9c968fda5a12e51cedba2a8843ee59074adacfa53b13a3967f8b
Passive check only: reading public DNS records, Certificate Transparency logs and ordinary GET requests to the homepage over HTTPS and HTTP. No changes were made to the scanned domain. Results are an indication and do not replace a professional security assessment.

Check your own domain