Open
Cached
·
just now
95/100
SECURITY SCORE
Certificate Information
Subject
CN=beta.axisgroup.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
January 04, 2026
Valid Until
April 04, 2026
70 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
5B:DE:18:C4:25:9A:A9:B8:DD:36:11:D0:F4:AD:BC:49:CD:A0:28:30:60:57:8D:A1:00:BC:E8:FB:28:36:2E:80
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; includeSubDomains; preload
Content-Security-Policy
Good
default-src; script-src; font-src; +4 more
default-src 'self' 'unsafe-inline' https: *; script-src 'self' 'unsafe-inline' https: blob: *; font-src 'self' data: https:; img-src 'self' data: https:; style-src 'self' 'unsafe-inline' *; frame-ancestors 'none'; upgrade-insecure-requests;
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
geolocation=(self)
Recommendations
- • Strengthen CSP by removing 'unsafe-eval'
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