Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
Umami Analytics
AWS API Gateway
AWS CloudFront
Let's Encrypt
Google Tag Manager
Google Sign-In
OpenAI
Active incidents
Squarespace
Webflow
Google DoubleClick
Google Analytics
ClearBit
Google Cloud Storage
Google Static File Front End
Calendly
Google Fonts
Twitter
G Workspace
Hotjar
Loom
LinkedIn
Stripe
unpkg
Google Search
Amazon S3
bunny.net
Active incidents
GitHub
AWS
Active incidents
Vercel
IP-API
PostHog
HubSpot
Intercom
Product Hunt
jsDelivr
Google Cloud
Certificate Information
Subject
CN=joinrightmatch.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
April 21, 2026
Valid Until
July 20, 2026
58 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
6D:7E:63:C1:23:68:77:0C:CF:7E:05:03:94:BD:CF:9D:76:17:9A:CE:5E:C3:A1:3C:30:8F:C8:F6:18:B4:06:5C
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
Present
max-age=63072000
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • 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
Configured
(Restricts certificate issuance)
Current Issuer
Authorized
(Matches CAA policy)
Authorized 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
- • Consider adding 'issuewild' records to control wildcard certificate issuance