Open
Cached
·
just now
88/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
BootstrapCDN
Cloudflare
Active incidents
Cloudflare CDN
Cloudflare CDNJS
DigiCert
Google Analytics
Google API JS Client
Google DoubleClick
Google Fonts
Google Hosted Libraries
Google reCAPTCHA
Google Search
Google Static File Front End
Google Tag Manager
Hotjar
ipify
jQuery
Microsoft Azure
Vimeo
Google Cloud
Certificate Information
Subject
C=US, ST=Pennsylvania, L=Philadelphia, O=PFM Financial Advisors, LLC, CN=*.pfm.com
Issuer
C=US, O=DigiCert Inc, CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid From
January 05, 2026
Valid Until
January 22, 2027
291 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
CE:1B:B4:06:DE:D2:1B:5E:7C:5A:CD:A0:72:0A:AE:4A:7B:5D:EF:64:3C:2D:43:CA:8F:23:BD:CB:0B:03:8B:B6
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
X-Frame-Options
Good
sameorigin
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
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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