Digital exposure report
bcp.com.bo
Good shape, with a few gaps worth closing this quarter.
Scanned: 2026-11-21 09:50 UTC
Partial coverage: the score is based on 93% 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 bcp.com.bo
- 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 bcp.com.bo
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- bcp.com.bo
- Website request
- GET https://bcp.com.bo/
- Scan time
- 2026-11-21 09:50:10 UTC
- Grading method
- Version 2How grading works
- Unverified or excluded checks
- HTTP → HTTPS redirect · Unverified
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/18 | Traffic to the site is encrypted and the certificate is valid. |
| Browser protections | 27/30 | The site instructs browsers to block common attacks. |
| DNS infrastructure | 1/15 | The domain's infrastructure lacks basic protections. |
Fix priorities
- 1.MediumDNS server redundancy · Hardening gap+2
- 2.MediumDNSSEC — signed DNS records · Hardening gap+8
- 3.LowCAA — who may issue certificates · Hardening gap+5
- 4.LowCSP — protection from script injection · Hardening gap+3
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.
- HTTP → HTTPS redirect
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. 3 of the 10 allowed DNS lookups.
v=spf1 mx:bcp.com.bo include:spf.protection.outlook.com include:spf-004a9b01.pphosted.com -all
$ dig +short TXT bcp.com.bo
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@hispasec.com,mailto:snznaru6s5@rua.app.digitalcorplatam.com; ruf=mailto:dmarc@hispasec.com,mailto:snznaru6s5@ruf.app.digitalcorplatam.com; pct=100;
$ dig +short TXT _dmarc.bcp.com.bo
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: selector1, s1, s2. Confirm signing with dkim=pass in a sent message's Authentication-Results.
selector1._domainkey: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAs3uahReeeRQEc6hHYT7duTriNZcd… s1._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4Zsxk6z0KBGBJbJnk+8l1b8Kufmjaox9… s2._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuPUAhAzZIld09tTD3PMmFjp/j3bmrA7Y…
$ dig +short TXT selector1._domainkey.bcp.com.bo
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
2 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
10 mxb-004a9b01.gslb.pphosted.com 10 mxa-004a9b01.gslb.pphosted.com
$ dig +short MX bcp.com.bo
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://bcp.com.bo/ returned HTTP 200 (final URL: https://bcp.com.bo/). Client-side certificate validation passed.
HTTP 200 Final URL: https://bcp.com.bo/
$ curl -sIL https://bcp.com.bo/
HTTP → HTTPS redirect
Unverified · Severity: OK · Not scoredCouldn't confirm whether plain HTTP redirects: port 80 didn't respond in time or the connection failed. Not scored.
Couldn't confirm whether plain HTTP redirects: port 80 didn't respond in time or the connection failed. Not scored.
Port 80 not responding (timeout)
$ curl -sI http://bcp.com.bo/ | grep -iE "^(HTTP|location)"
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 2026-12-10 (19 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-05-26 Valid until: 2026-12-10 Names: bcp.com.bo, www.bcp.com.bo Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect bcp.com.bo:443 -servername bcp.com.bo 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. ≥ 180 days recommended.
Strict-Transport-Security: max-age=31536000; includeSubDomains
$ curl -sIL https://bcp.com.bo/ | grep -i "Strict-Transport-Security"
CSP — protection from script injection
Needs attention · Severity: Low · Hardening gap · 5/8A script policy exists, but it's permissive and offers only partial protection.
script-src includes: no script-src/default-src — weakens XSS protection.
Content-Security-Policy: object-src 'none'; frame-ancestors 'self'; style-src 'self' 'unsafe-inline' script-src 'self' 'unsafe-inline' https://static.hotjar.com https://www.googletagmanager.com http://www.google-analytics.com https://connect.facebook.net https://lynn-latam-production-br-ch-reg-common.azurewebsites.net https://googleads.g.doubleclick.net https://www.clarity.ms www.google.com https://www.gstatic.com https://www.googleapis.com https://cdn.jsdelivr.net https://td.doubleclick.net/; https://lynn-latam-production-br-ch-reg-common.azurewebsites.net;
$ curl -sIL https://bcp.com.bo/ | 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 frame-ancestors 'self'
X-Frame-Options: SAMEORIGIN CSP frame-ancestors: 'self'
$ curl -sIL https://bcp.com.bo/ | 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://bcp.com.bo/ | grep -i "X-Content-Type-Options"
Referrer-Policy
Passed · Severity: OK · 3/3Internal URLs don't leak to external sites.
Referrer-Policy: no-referrer
Referrer-Policy: no-referrer
$ curl -sIL https://bcp.com.bo/ | grep -i "Referrer-Policy"
Permissions-Policy
Passed · Severity: OK · 2/2The site restricts access to sensitive browser features.
Permissions-Policy: fullscreen=()
Permissions-Policy: fullscreen=()
$ curl -sIL https://bcp.com.bo/ | 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: (missing)
$ curl -sIL https://bcp.com.bo/ | 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 bcp.com.bo: NODATA
$ dig +short DS bcp.com.bo
- 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 bcp.com.bo SOA delv bcp.com.bo
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 bcp.com.bo
- Identify which certificate authority issued your current certificate (see the certificate check).
- Publish CAA for that authority only, and add iodef to receive alerts.
bcp.com.bo. CAA 0 issue "letsencrypt.org" bcp.com.bo. CAA 0 iodef "mailto:security@bcp.com.bo"
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
Needs attention · Severity: Medium · Hardening gap · 1/3The domain depends on a single DNS server — a single point of failure.
1 NS records. RFC 2182 recommends at least 2 servers on separate networks.
server29.bcp.com.bo
$ dig +short NS bcp.com.bo
- Add a second NS server at your DNS provider, or use a managed provider with anycast.
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain.
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.01 observed gaps · 1 unverified
- NIS2 / vendor due diligence2 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 | bcp.com.bo | 170.245.35.119 | 45.232.46.119 | 45.232.46.204 |
| AAAA | bcp.com.bo | — |
| MX | bcp.com.bo | 10 mxb-004a9b01.gslb.pphosted.com | 10 mxa-004a9b01.gslb.pphosted.com |
| NS | bcp.com.bo | server29.bcp.com.bo |
| TXT | bcp.com.bo | google-site-verification=lH_-IZI6_Od8NVQ252yjIvdyHTw7_rEXzNTuro6leGQ | _d5cv9zrwp3hso1xqp0difnsx5fbwccb | dtm-domain-verification=mDqd6sY9aLhb4oTn-eO6T0I0AgjVpTxtjOuhWJ776HI | _hsjcrsw0g6092f8gp0xho3cwdnberii | MS=ms79679013 | google-gws-recovery-domain-verification=74319288 | _pyixry286y4a26d0ucgb52xar8ddzjr | v=spf1 mx:bcp.com.bo include:spf.protection.outlook.com include:spf-004a9b01.pphosted.com -all | _atm00d73ndwepo5axu12hxwdg9dhfy7 | _wjs2y6wcsu1hs5lv532pkgfjidpg7pz | MS=ms27511994 | atlassian-domain-verification=w5f/S31tiwajby0aAciSs/etOAp1M9ZokAaUicOaD/JnyMbl89DCvtF2qLYvmXiO |
| TXT | _dmarc.bcp.com.bo | v=DMARC1; p=reject; rua=mailto:dmarc@hispasec.com,mailto:snznaru6s5@rua.app.digitalcorplatam.com; ruf=mailto:dmarc@hispasec.com,mailto:snznaru6s5@ruf.app.digitalcorplatam.com; pct=100; |
| CAA | bcp.com.bo | — |
| DS | bcp.com.bo | — |