Open
Cached
·
just now
92/100
SECURITY SCORE
Certificate Information
Subject
CN=pixelframe.ai
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
October 31, 2025
Valid Until
January 29, 2026
63 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
51:AA:22:C5:10:1F:C0:26:C2:61:38:DB:5C:C0:73:4F:AE:1D:AD:27:D5:82:D8:9D:3A:D6:74:62:C8:81:71:01
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=31556926; includeSubDomains
Content-Security-Policy
Basic
default-src; script-src; font-src; +4 more
default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://unpkg.com https://code.jquery.com https://cdn.jsdelivr.net https://pixelframe.ai https://*.pixelframe.ai https://*.unpkg.com https://*.cloudflareinsights.com https://challenges.cloudflare.com https://www.gstatic.com https://*.googleapis.com https://apis.google.com https://accounts.google.com; font-src 'self' https://cdnjs.cloudflare.com data: https://fonts.gstatic.com; style-src 'self' 'unsafe-inline' https://cdnjs.cloudflare.com https://fonts.googleapis.com https://challenges.cloudflare.com https://accounts.google.com; img-src 'self' data: blob: https: http: https://pub-fa2dad2229b845ffbb1ac54b62fa087b.r2.dev; connect-src 'self' https: wss: https://*.pixelframe.ai https://pub-fa2dad2229b845ffbb1ac54b62fa087b.r2.dev https://*.googleapis.com https://identitytoolkit.googleapis.com https://securetoken.googleapis.com https://accounts.google.com; frame-src 'self' https: http: https://challenges.cloudflare.com https://accounts.google.com
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
browsing-topics=()
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • 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