Digital exposure report
bancodechile.cl
Moderate exposure. There are gaps an attacker could exploit — fix them soon.
Scanned: 2026-11-19 03:31 UTC
Partial coverage: the score is based on 88% of applicable check weight. 1 unverified check(s) are excluded, not counted as failures.
What to do first
- 1.
Turn on DNS signing for your domain
Signing helps resolvers detect forged answers about your domain.
Who can fix it: Your domain registrar or DNS provider
How to verify after the fix
dig +short DS bancodechile.cl
- 2.
Choose which companies may issue certificates for your domain
This reduces the chance of a certificate being issued by a provider you did not choose.
Who can fix it: Your domain registrar or DNS provider
How to verify after the fix
dig +short CAA bancodechile.cl
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- bancodechile.cl
- Website request
- GET https://bancodechile.cl/(no HTTPS response)
- Scan time
- 2026-11-19 03:31:39 UTC
- Grading method
- Version 2How grading works
- Unverified or excluded checks
- DKIM — digital signature on email · Not detected (common selectors only)
- 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 security | 25/25 | Spoofing email from this domain is hard. |
| Encryption & certificate | — | Not applicable to this domain. |
| Browser protections | — | Not applicable to this domain. |
| DNS infrastructure | 3/15 | The domain's infrastructure lacks basic protections. |
Fix priorities
- 1.MediumDNSSEC — signed DNS records · Hardening gap+18
- 2.LowCAA — who may issue certificates · Hardening gap+13
To verify
Couldn't be confirmed from public data, so excluded from the score. Checking them clarifies your posture; it doesn't guarantee a score change.
- DKIM — digital signature on email
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. 0 of the 10 allowed DNS lookups.
v=spf1 -all
$ dig +short TXT bancodechile.cl
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;pct=100;fo=1;ri=3600; rua=mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com
$ dig +short TXT _dmarc.bancodechile.cl
DKIM — digital signature on email
Not detected (common selectors only) · Severity: OK · Not scoredNo DKIM key was found under the common selectors we probed. That doesn't mean DKIM is missing — selectors can't be listed from public DNS. Not scored.
A missing name for a probed selector (NXDOMAIN/NODATA) only means that selector isn't published. DKIM is marked unverified and excluded from the score. Check a sent message's Authentication-Results for dkim=pass and its s= selector.
Selectors checked: google, selector1, selector2, default, k1, s1, s2, dkim, mail, smtp — no key found google._domainkey: nxdomain selector1._domainkey: nxdomain selector2._domainkey: nxdomain default._domainkey: nxdomain k1._domainkey: nxdomain s1._domainkey: nxdomain s2._domainkey: nxdomain dkim._domainkey: nxdomain mail._domainkey: nxdomain smtp._domainkey: nxdomain
$ dig +short TXT google._domainkey.bancodechile.cl
MX — inbound mail routing
Info · Severity: OK · unscoredNo MX records are published. On its own this doesn't prove the domain can't receive email.
Without MX, senders may fall back to the A/AAAA address (RFC 5321 §5.1). A Null MX is appropriate only once you've confirmed the domain receives no email.
(no MX records)
$ dig +short MX bancodechile.cl
- Only if you've confirmed the domain receives no email: publish a Null MX (MX 0 .), and keep SPF -all and DMARC p=reject if it also sends none.
bancodechile.cl. MX 0 .
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain.
HTTPS available
Not applicable · Severity: OK · Not applicableThe 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.
No A/AAAA record for the domain
$ curl -svI https://bancodechile.cl/ 2>&1 | grep -E "SSL|HTTP|expire"
HTTP → HTTPS redirect
Not applicable · Severity: OK · Not applicableThe 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.
Not checked
$ curl -sI http://bancodechile.cl/ | grep -iE "^(HTTP|location)"
SSL/TLS certificate validity
Not applicable · Severity: OK · Not applicableThe 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.
CT logs (context only, not scored): Issuer: GlobalSign Valid from: 2026-10-23 Valid until: 2027-01-21 Names: *.apistore.bancochile.cl, *.apitravel.cl, *.bancodechile.cl, *.tiendaentelvisa.cl, *.travel.cl, *.traveldelta.cl Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect bancodechile.cl:443 -servername bancodechile.cl 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Not applicable · Severity: OK · Not applicableNot applicable — the domain has no web address.
Not applicable — the domain has no web address.
No HTTPS response received
$ curl -sIL https://bancodechile.cl/
CSP — protection from script injection
Not applicable · Severity: OK · Not applicableNot applicable — the domain has no web address.
Not applicable — the domain has no web address.
No HTTPS response received
$ curl -sIL https://bancodechile.cl/
Clickjacking protection
Not applicable · Severity: OK · Not applicableNot applicable — the domain has no web address.
Not applicable — the domain has no web address.
No HTTPS response received
$ curl -sIL https://bancodechile.cl/
X-Content-Type-Options
Not applicable · Severity: OK · Not applicableNot applicable — the domain has no web address.
Not applicable — the domain has no web address.
No HTTPS response received
$ curl -sIL https://bancodechile.cl/
Referrer-Policy
Not applicable · Severity: OK · Not applicableNot applicable — the domain has no web address.
Not applicable — the domain has no web address.
No HTTPS response received
$ curl -sIL https://bancodechile.cl/
Permissions-Policy
Not applicable · Severity: OK · Not applicableNot applicable — the domain has no web address.
Not applicable — the domain has no web address.
No HTTPS response received
$ curl -sIL https://bancodechile.cl/
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 bancodechile.cl: NODATA
$ dig +short DS bancodechile.cl
- 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 bancodechile.cl SOA delv bancodechile.cl
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
Needs attention · Severity: Low · Hardening gap · 0/5Any certificate authority can issue a certificate for the domain, raising the risk of mis-issuance.
No CAA records found. RFC 8659 lets the domain owner restrict which CAs are authorized.
(no CAA records found)
$ dig +short CAA bancodechile.cl
- Identify which certificate authority issued your current certificate (see the certificate check).
- Publish CAA for that authority only, and add iodef to receive alerts.
bancodechile.cl. CAA 0 issue "letsencrypt.org" bancodechile.cl. CAA 0 iodef "mailto:security@bancodechile.cl"
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. If your CDN issues certificates on your behalf, include it too — otherwise certificate renewal will fail.
DNS server redundancy
Passed · Severity: OK · 3/3The domain is served by several DNS servers, so one server failing won't take it down.
6 NS servers.
a3-66.akam.net a1-24.akam.net a2-64.akam.net a28-67.akam.net a13-64.akam.net a6-65.akam.net
$ dig +short NS bancodechile.cl
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 rules1 unverified
- PCI DSS v4.0Not applicable
- NIS2 / vendor due diligence2 observed gaps
- 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
| A | bancodechile.cl | — |
| AAAA | bancodechile.cl | — |
| MX | bancodechile.cl | — |
| NS | bancodechile.cl | a3-66.akam.net | a1-24.akam.net | a2-64.akam.net | a28-67.akam.net | a13-64.akam.net | a6-65.akam.net |
| TXT | bancodechile.cl | _krqqtycimdbzzew8025qnnrn4945wfj | globalsign-domain-verification=D4E33C6291F95B8A085D490D22178ABB | google-site-verification=huLrbonR7DtlBXbneBPMzSfnJI70TSGBAicIrueZJ88 | globalsign-domain-verification=E9CBF4FA61A4D37FA8FB8C8D5E02BAEA | _globalsign-domain-verification=WnTid785giN2uWqrM3QspWUHAX928zdxJMdCiRrHz8 | flexera-domain-verification-vjjanofspqxreqoq | globalsign-domain-verification=E2F3D2DCFD2EC0E4A20E952965F8C2D3 | globalsign-domain-verification=5a2fe3ed0f49a5453aed50e86de56e12 | w5gf2cvc65vhyb7sq1tczmlkcm3r9kd5 | globalsign-domain-verification=310EE73C0346D225D9D3E7B37CF889FD | 3EFE26987CC8A7C139B87FA8C92C4809039328BB34491586D79BD0EA4E2D9DA8 | globalsign-domain-verification=9BC22755327A4771582387181B826D85 | mvv7trwm8b8dcks3lcn3t38rtd0sj8cf | v=spf1 -all | globalsign-domain-verification=E762B5EA669B4D79CFBBF28E5D6B0BF9 | globalsign-domain-verification=dbf17cfc367fad9421b0d2d8542c8630 | miro-verification=36e8ce35eafc1b2c9957baa0ae820dd941b3cc5c | _yow5g7hxia3i0c3dk3f8tsh6bz6s1br | globalsign-domain-verification=6B87D540DB9DF67FD5015487F6A11EBD | globalsign-domain-verification=5e845ec8b51ca371caa22d7fd17babfe | _hk5xi0o5y2dhiba61gn11l6alds2971 | apple-domain-verification=Y12BNIiWUHhYWNC2 | globalsign-domain-verification=9EAC8E8211672B736374B1FE28AAD92B |
| TXT | _dmarc.bancodechile.cl | v=DMARC1;p=reject;pct=100;fo=1;ri=3600; rua=mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com |
| CAA | bancodechile.cl | — |
| DS | bancodechile.cl | — |