Open
Cached
·
just now
91/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Google Trust
AdRoll
AppNexus (Xandr)
BootstrapCDN
Brightcove
Crazy Egg
Criteo
Oracle Eloqua
Google Analytics
Google DoubleClick
Google Fonts
Google Search
Google Tag Manager
G Workspace
Liveramp
OneTrust
OpenX
Outbrain
PubMatic
Rubicon Project
SearchUnify
StackAdapt
Taboola
The Trade Desk
TripleLift
unpkg
Yahoo
YouTube
Zoom
Active incidents
Certificate Information
Subject
CN=knowledge.broadcom.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
August 19, 2026
Valid Until
November 17, 2026
89 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
74:41:A8:6A:C8:3D:42:7F:51:72:E6:3F:0C:A9:E3:7D:72:AE:51:03:F4:6C:E5:9F:71:6B:63:BA:FB:F9:5B:14
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
Good
max-age=31536000; includeSubDomains
X-Frame-Options
Present
SAMEORIGIN, SAMEORIGIN
X-Content-Type-Options
Present
nosniff, nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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