Open
Cached
·
just now
89/100
SECURITY SCORE
Certificate Information
Subject
CN=firstmanhattan.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
November 07, 2025
Valid Until
February 05, 2026
33 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
95:5A:72:2D:1A:EC:AC:FD:C2:0A:81:A6:3E:B3:6A:B3:C8:4E:89:41:BE:15:B2:BD:42:F0:E5:E0:28:98:97:DC
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=63072000; includeSubDomains; preload
Content-Security-Policy
Basic
default-src; frame-src; script-src; +2 more
default-src 'self' 'unsafe-inline' *.firstmanhattan.com *.cookieyes.com cdn-cookieyes.com *.vimeocdn.com *.google.com *.typekit.net acsbapp.com *.acsbapp.com *.marketo.com *.marketo.net *.mktoresp.com *.mktoutil.com *.google-analytics.com *.hotjar.com *.hotjar.io; frame-src 'self' data: *.firstmanhattan.com *.castos.com *.clickcertain.com *.vimeo.com youtube.com www.youtube.com *.hotjar.com *.marketo.com snazzymaps.com www.google.com; script-src 'self' 'unsafe-eval' 'unsafe-inline' cdn-cookieyes.com *.clickcertain.com *.remarketstats.com go.firstmanhattan.com www.googletagmanager.com www.google-analytics.com www.google.com www.gstatic.com *.castos.com munchkin.marketo.net code.jquery.com *.hotjar.com *.marketo.com acsbapp.com *.acsbapp.com; font-src 'self' data: *.typekit.net acsbapp.com *.acsbapp.com; img-src 'self' cdn-cookieyes.com *.vimeocdn.com *.google.com *.typekit.net acsbapp.com *.acsbapp.com *.marketo.com *.marketo.net *.mktoresp.com *.mktoutil.com *.google-analytics.com *.hotjar.com *.hotjar.io data:;
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Missing
Not configured
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • 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