Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Dropbox
Google Trust
Akamai
Active incidents
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.pairsoft.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
March 24, 2026
Valid Until
June 22, 2026
71 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
1C:86:E6:22:0B:87:8D:DE:EF:BD:7C:68:34:79:82:19:C9:64:83:B7:1F:40:E3:84:E2:CA:FE:3D:4F:CB:20:6B
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
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