Open
Cached
·
just now
93/100
SECURITY SCORE
Certificate Information
Subject
CN=production-api.androidacy.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
January 12, 2026
Valid Until
April 12, 2026
68 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
38:2F:8B:BD:36:20:39:E1:EA:FB:63:11:D2:78:C3:23:73:1F:FE:4C:22:7E:A8:95:98:61:87:60:E0:16:B0:6A
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
Basic
default-src; upgrade-insecure-requests; block-all-mixed-content; +1 more
default-src https: wss: data: blob: 'unsafe-inline' 'unsafe-eval'; upgrade-insecure-requests; block-all-mixed-content; frame-ancestors https://*.androidacy.com
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
encrypted-media=*, geolocation=*, attribution-reporting=*, browsing-topics=*, local-fonts=*
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