Open
Cached
·
just now
89/100
SECURITY SCORE
Certificate Information
Subject
CN=dev.blastiq.com
Issuer
C=US, O=DigiCert Inc, OU=www.digicert.com, CN=GeoTrust TLS RSA CA G1
Valid From
December 20, 2025
Valid Until
June 20, 2026
146 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
2F:80:AF:21:DC:8D:BD:1E:AC:4E:4C:D4:C7:67:D8:10:0C:06:95:A2:78:E2:60:C8:44:F4:3D:F4:E4:4B:72:38
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
Content-Security-Policy
Good
frame-ancestors; frame-src; default-src; +6 more
frame-ancestors 'self'; frame-src 'self'; default-src 'none'; script-src 'self'; connect-src 'self' *.blastiq.com https://southeastasia-1.in.applicationinsights.azure.com/v2/track https://js.monitor.azure.com api.raygun.io; img-src 'self'; style-src 'self' fonts.googleapis.com 'unsafe-inline'; base-uri 'self'; font-src 'self' fonts.gstatic.com;
X-Frame-Options
Excellent
deny
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Strengthen CSP by removing 'unsafe-eval'
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
- • 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