SSL Certificate Analysis for brand.bbvaexperience.com - Security Grade & TLS Configuration

Open Cached · just now

82/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 1

DigiCert

Certificate Information

Subject

C=ES, ST=Bizkaia, L=BILBAO, O=BANCO BILBAO VIZCAYA ARGENTARIA SOCIEDAD ANONIMA, CN=bbva.com

Issuer

C=US, O=DigiCert Inc, CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1

Valid From

March 18, 2026

Valid Until

October 02, 2026 54 days

Public Key

RSA 2048 bit Adequate

Signature Algorithm

SHA256-RSA

SHA-256 Fingerprint

F8:B9:1C:91:4E:58:70:27:83:EC:1E:07:59:58:58:90:CA:A9:B9:7F:DC:39:BD:86:E7:2E:78:12:F1:5A:3B:88

Alternative Names

99 domains

Security Configuration

TLS Protocols

TLS 1.2 TLS 1.3

Forward Secrecy

Supported (Modern clients use PFS)

HTTP Security Headers

Status

Strict-Transport-Security

Present

max-age=31536000; includeSubdomains;

Content-Security-Policy

Weak

font-src; frame-ancestors Analyze

Content-Security-Policy-Report-Only

Missing

Not configured Analyze

X-Frame-Options

Missing

Not configured

X-Content-Type-Options

Good

nosniff

Referrer-Policy

Missing

Not configured

Permissions-Policy

Missing

Not configured

Recommendations

• Increase HSTS max-age to at least 1 year and add includeSubDomains
• Significantly strengthen CSP directives
• Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
• Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
• Consider adding Permissions-Policy to control browser features

CAA Records (Certificate Authority Authorization)

CAA Records

Not Configured (Any CA can issue certificates)

CAA Issues

• No CAA records configured - any CA can issue certificates

Recommendations

• Implement CAA records to restrict which CAs can issue certificates for your domain
• This adds an extra layer of security against unauthorized certificate issuance
• Example: Add CAA record 'example.com. CAA 0 issue "letsencrypt.org"'
• Consider adding 'iodef' record to receive security incident reports