Open
Cached
·
just now
88/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Google Tag Manager
Bugsnag
G2
Google Hosted Libraries
HubSpot Forms
Capterra
JotForm
Google DoubleClick
Google Analytics
Google Static File Front End
Google API JS Client
Transcend
Hotjar
LinkedIn
HubSpot Analytics
Google Search
BootstrapCDN
Storylane
Facebook
Amazon S3
OneTrust
Adobe Fonts (Typekit)
AddEvent
AddToAny
Cloudflare CDNJS
Salesforce Pardot
AWS Certificate Manager
Vimeo
HubSpot
YouTube
Font Awesome
Google Cloud
Certificate Information
Subject
CN=renweb.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
February 18, 2026
Valid Until
March 19, 2027
312 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
22:86:3E:9C:AC:70:8F:98:CA:B1:02:CB:54:2D:DB:0D:59:C1:96:B0:84:EB:38:27:BB:93:64:82:A7:ED:54:28
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=63072000; includeSubDomains;
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
origin
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 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