Open
Cached
·
just now
82/100
SECURITY SCORE
Certificate Information
Subject
CN=pocketplan.io
Issuer
C=US, ST=Arizona, L=Scottsdale, O=Starfield Technologies, Inc., OU=http://certs.starfieldtech.com/repository/, CN=Starfield Secure Certificate Authority - G2
Valid From
October 05, 2025
Valid Until
January 03, 2026
39 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
2E:DC:9F:08:34:C0:ED:E3:18:6B:4B:1A:9F:C1:35:80:B1:9C:A2:E5:C9:2A:E1:BE:5F:D9:F7:D3:4F:F9:1E:88
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
Missing
Not configured
Content-Security-Policy
Weak
upgrade-insecure-requests
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • Significantly strengthen CSP directives
- • 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
Configured
(Restricts certificate issuance)
Current Issuer
Not Authorized
(Potential misconfiguration)
Authorized CAs
pki.goog
; cansignhttpexchanges=yes
sectigo.com starfield.com godaddy.com
ssl.com
starfieldtech.com
comodoca.com
digicert.com
; cansignhttpexchanges=yes
letsencrypt.org
Wildcard CAs
comodoca.com
digicert.com
; cansignhttpexchanges=yes
letsencrypt.org
pki.goog
; cansignhttpexchanges=yes
ssl.com
CAA Issues
- • CRITICAL: Current certificate issuer 'C=US, ST=Arizona, L=Scottsdale, O=Starfield Technologies, Inc., OU=http://certs.starfieldtech.com/repository/, CN=Starfield Secure Certificate Authority - G2' is NOT authorized by CAA records. Authorized CAs: pki.goog; cansignhttpexchanges=yes, sectigo.com starfield.com godaddy.com, ssl.com, starfieldtech.com, comodoca.com, digicert.com; cansignhttpexchanges=yes, letsencrypt.org
Recommendations
- • Consider using critical flag (flags=128) for stricter CAA enforcement
- • You have authorized 7 CAs - consider limiting to only the CAs you actively use
- • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts