Open
Cached
·
just now
92/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Dropbox
Google Trust
Akamai
AWS
Amazon S3
Beamer
Braintree
Calendly
Cloudflare CDNJS
Cloudflare Web Analytics
Font Awesome
Freshdesk
Freshworks
Google Analytics
Google API JS Client
Google Fonts
Google Maps
Google reCAPTCHA
Google Search
Google Static File Front End
Google Sign-In
Google Tag Manager
Google Translate
Heap
jsDelivr
New Relic
Qualtrics
Sentry
unpkg
Wistia
Google Cloud
Certificate Information
Subject
CN=support.purmsec.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
April 27, 2026
Valid Until
July 26, 2026
82 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
AB:45:90:01:CF:82:F2:E7:FE:09:A5:76:39:16:CF:7B:17:FA:FB:49:7C:9B:93:2F:CD:A9:41:26:76:84:95:59
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=31536000; includeSubDomains; preload
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • 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
Configured
(Restricts certificate issuance)
Current Issuer
Authorized
(Matches CAA policy)
Authorized CAs
Wildcard CAs
Recommendations
- • Consider using critical flag (flags=128) for stricter CAA enforcement
- • You have authorized 4 CAs - consider limiting to only the CAs you actively use
- • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts