Cached · just now
93/100 SECURITY SCORE

Certificate Information

Subject
C=US, ST=California, L=Foster City, O=BrightEdge Technologies Inc., CN=*.brightedge.com
Issuer
C=US, O=DigiCert Inc, CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid From
November 06, 2025
Valid Until
December 07, 2026 290 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
3F:53:16:50:45:BD:03:96:92:80:52:BD:24:F0:32:A2:06:F0:17:91:F9:ED:14:67:D3:52:BD:C7:68:14:83:F3
Alternative Names

Security Configuration

TLS Protocols
TLS 1.2 TLS 1.3
Forward Secrecy
Supported (Modern clients use PFS)

HTTP Security Headers

Status
Strict-Transport-Security
Excellent
max-age=31536000, max-age=63072000, max-age=31536000; includeSubDomains; preload
Content-Security-Policy
Basic
frame-ancestors; ,; script-src; +11 more Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Present
SAMEORIGIN, SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
strict-origin-when-cross-origin, no-referrer
Permissions-Policy
Present
geolocation=(), microphone=(), camera=(); +1 more
Recommendations
  • Improve CSP by adding more specific directives and removing 'unsafe-inline'

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

Subject Alternative Names

2 domains