Open
Cached
·
just now
91/100
SECURITY SCORE
Certificate Information
Subject
CN=globalstar.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
January 13, 2026
Valid Until
April 13, 2026
66 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
6B:FA:A5:67:39:39:8F:60:0E:C6:11:69:E2:D7:F4:BF:CE:9C:BB:F8:DE:98:00:7E:67:7E:E9:A6:C3:D9:07:92
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
Present
max-age=2592000
Content-Security-Policy
Basic
frame-ancestors; object-src; script-src
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
camera=(), microphone=(), geolocation=(self), payment=(), usb=(), autoplay=(self "https://player.vimeo.com" "https://challenges.cloudflare.com"), fullscreen=(self "https://player.vimeo.com" "https://challenges.cloudflare.com"), picture-in-picture=(self "https://player.vimeo.com" "https://challenges.cloudflare.com")
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • 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